Globiquity.ai™ develops and licenses one orchestration platform that carries a shipment or a relocation through its full lifecycle: intake, pricing, capacity assignment, movement tracking, proof of delivery, invoicing, settlement, and claims. STRATUM-X™ is the execution engine. QUANTUM-X™ is the relocation front office. Both run today on a single multi-tenant platform with one record model, one identity model, and one API surface, rather than as two products integrated after the fact.
STRATUM-X™ execution
Running in production todayQUANTUM-X™ relocation front office
Running in production todayFinancial and back-office integrations
In active developmentSecurity and compliance roadmap
In active developmentQuoting and related authorized workflows
Dispatch and operational coordination
Financial workflows and reconciliation
Tenant configuration with least-privilege permissions
Household goods and relocation programs (QUANTUM-X™)
Commercial freight customers submit shipping requests directly. Defense household goods and relocation requests enter through the relocation front office. Enterprise workforce relocation requests enter the same way, in commercial terminology. These are distinct intakes with distinct compliance contexts.
Every one of those intakes converges on a single execution core: one place where work is priced, capacity is assigned, and movement is tracked. There is no second quoting system, no parallel dispatch, and no duplicated operational record.
Because there is one core, there is one operational picture. Status, documents, cost, and communication for a defense relocation and for a commercial freight shipment are produced by the same machinery and are visible in the same shape.
Three request streams, each with its own compliance context, captured as structured records.
The convergence point. Work is priced and capacity is assigned in one place for every intake stream.
Movement is tracked, milestones are recorded as they happen, and documents attach to the record.
Proof of delivery, invoicing, payment, and a closed record retained with its evidence.
Transaction and telemetry capabilities running in production today, exposed through the same REST API that drives the interface.
A persistent, record-scoped conversation on every shipment and move. Every party talks in one place, and every message stays with the record as part of its audit trail.
Shipment GQ-20418 · conversation
Driver assigned. Pickup confirmed for 10:30.
Loaded and on the road. ETA 14:10.
Delivered and signed for. Proof of delivery received, thanks.
Positional updates from the field, visible only to authorized users in the shipment's organization by role and assignment, and shared with connected systems over the event stream, so status is observed rather than requested.
Each milestone is written to the record as an event at the moment it occurs and propagates immediately to reporting and to subscribed systems. Status is a query, not a phone call.
Routes are planned and optimized on the platform against distance, capacity, and service constraints, producing an estimated arrival that recalculates as conditions change.
Shipment and move requests are submitted, captured, and turned into live records on the platform, with no rekeying between request and execution.
Customers pay against a shipment or a move directly on the platform, with payment tied to the record rather than reconciled after the fact.
Documents and photographs are uploaded from the field and from the office, attached to the record, and retained as part of it.
Generally available today, running on the same multi-tenant platform, record model, and API surface as STRATUM-X™.
Household goods inventory is captured with mandatory photo evidence, independently verified before pricing, and verified again at pickup and drop-off. Each version is preserved rather than overwritten, which is what makes chain of custody provable after the fact rather than asserted.
The same product serves defense household goods programs and commercial workforce relocation. Terminology, workflow vocabulary, and permissions render in the language of the organization using it, and the underlying record is identical, which is why both feed the same execution engine.
Requests are submitted, reviewed, returned with notes if incomplete, and validated before anything enters execution.
Before a relocation is committed, the platform produces a cost projection and policy assessment so the organization can evaluate whether and how to proceed.
Goods are surveyed before pricing, so the price reflects what is actually being moved.
A dedicated mobile experience for the person relocating: submit, track, communicate, upload evidence, and see status without calling anyone.
Damage claims are filed against the delivered move, with the evidence already attached to the record from capture through delivery.
Aggregate reporting on volume, on-time performance, spend, and satisfaction across a relocation program.
A single status register for the platform. Every capability named anywhere on this page appears in exactly one of the two groups below, with no capability counted twice and none left unplaced.
Accepting tenders and awards from external systems and turning them into live records without rekeying. Partially implemented. No external interface is operating today.
Payment, payroll, card and accounting connections, each with its own status.
The full roadmap listed in the security and compliance program. Planned, not in force.
Suggests a cost estimate and a quote price for a shipment or a move, in STRATUM-X™ and QUANTUM-X™.
Evidence for each production capability (demonstration, test or release record) is available under NDA.
The platform owns the logistics work; your existing systems keep owning your company, money and people data.
| The platform is authoritative for | Your existing systems stay authoritative for |
|---|---|
| Shipment and move records, quotes, dispatch and assignments | Customer and vendor master data in your ERP |
| Tracking events and lifecycle milestones | General ledger and accounting (for example QuickBooks) |
| Documents, inventory and claims attached to a record | Payroll and employment (for example DEEL) |
| Payment status for platform invoices | Bank and treasury accounts (for example Wise, Syncada) |
| Area | Globiquity.ai™ (licensor) | Authorized integrator | Customer |
|---|---|---|---|
| Platform hosting and updates | Responsible | ||
| Monitoring and incident response (platform) | Responsible | ||
| Connector build and support | Responsible | ||
| Configuration and onboarding | Responsible | ||
| Users, roles and data entered | Responsible |
One platform. STRATUM-X™ and QUANTUM-X™ are two layers of the same system, sharing one execution core, one identity model, and one operational record, running together on one multi-tenant platform. They are deployed together rather than integrated after the fact.
No. The choice belongs to the customer organization. The platform is designed to operate alongside existing systems of record, connecting through documented APIs and exchanging data with upstream systems rather than requiring a migration. Where an organization is willing to run its program entirely on the platform, that is what we recommend, because the capability set on the platform is broader than what an integration boundary can carry across.
A documented REST API with a published OpenAPI specification, plus webhooks and streaming connections for event-driven status updates. Anything the interface can do, an integrating system can do. The technical documentation package is listed in resources.
Resources and contact
The consolidated status register lists every capability on this page in exactly one of two groups, running in production today or in active development.
In production and in development
The platform is multi-tenant. Each customer organization's records are scoped to that organization in the application, and access is further limited by role. Defense and commercial work are held as separate organizations on shared infrastructure; a dedicated environment for defense data is not in place today.
Baseline application controls, such as central sign-in with account lockout, optional multi-factor authentication, role-based access and encrypted database connections, are in place today and listed on this page. The compliance controls and certifications in the security roadmap are planned and not in force today. Globiquity.ai™ is building the program deliberately rather than claiming positions it has not earned. Current security posture and documentation are available under appropriate agreement.
Yes. Both run on one record model, with terminology and workflow vocabulary rendering in the language of the organization using it, which is why both feed the same execution engine.
Online customer payment is live on the platform today through Stripe, with multi-currency and international treasury movement through Wise. Integration with U.S. Bank Syncada, the established freight payment network for defense household goods invoicing, is in development.
A capability discussion, a review of the systems that need to connect, and a scoped integration plan built against those systems. Scope is set with you before any commitment is made.
The technology white paper and the technical documentation package, including the API reference and OpenAPI specification, are available from the resources section. Request anything not listed there and it will be provided under appropriate agreement.
Resources and contact
