1. Home
  2. Integrations

Architecture & Integrations

The platform interoperates with existing government and enterprise systems of record. It ingests and publishes data across documented, versioned interfaces. In an integrated deployment, it runs alongside the systems you keep, without a data migration or a cutover event; in a primary deployment, authorized integrators handle migration and onboarding.

Platform data pathDocumented · Versioned
Intake channels

Freight requests, defense relocation requests, enterprise relocation requests, assignee mobile

API surface

Documented REST API with an OpenAPI specification provided to customers and integrators, webhooks, streaming connections, OAuth2 client credentials

Platform services

Pricing and capacity assignment, movement tracking, documents and evidence, invoicing and payment, reporting

Integration targets

Government and enterprise systems of record, payment and treasury rails, accounting systems, identity providers

Current statusIntegrations & controls

Wise, Stripe

Running in production today

U.S. Bank Syncada, Brex, QuickBooks, DEEL

In active development

Compliance controls and certifications

Roadmap, not in force today
01 · Architecture and integration

API-first architecture, built to interoperate with the systems you already run

API-first

Every capability is exposed through a documented REST API, with an OpenAPI specification provided to customers and integrators. Anything the interface can do, an integrating system can do.

Open integration posture

The platform operates alongside systems of record, ingesting and publishing data rather than demanding migration.

Event-driven updates

Webhooks and streaming connections push status changes to connected systems as they happen, rather than requiring polling.

Clear data ownership

Every record has exactly one owning service, and other services hold references to it. There is no ambiguity about which system holds the authoritative version, which is what keeps a multi-system integration from drifting out of sync.

Standards-based service authentication

Machine to machine connections use OAuth2 client credentials with narrowly scoped, short-lived, cryptographically verified tokens.

Tenant-scoped access

Every request is scoped to its organization from a verified credential, enforced at the data layer, never from a client-supplied value.

Federated identity

Support for enterprise single sign-on, with an architecture prepared for federal public key infrastructure credentials.

02 · International finance

Payment and accounting systems connect through the same open API surface

Settlement and reconciliation are wired through the documented API and event stream, so an existing finance stack integrates without rekeying and without replacement.

Settlement and reconciliation
Documented API and event stream
Existing finance stack
Running in production today2
W

Wise

Treasury connection for balance visibility and payroll transfers.

Direction
Platform to Wise for payroll recipients and transfers; Wise to platform for balances
Scope
Balance visibility and USD payroll transfers, approved and funded in Wise
Limitations
Payments in USD
Maintained by
Globiquity.ai™
S

Stripe

Online customer payment collection.

Direction
Platform to Stripe for payments; Stripe to platform for payment status
Scope
Card payments on shipments
Limitations
Payments in USD
Maintained by
Globiquity.ai™
In active development4
US

U.S. Bank Syncada

Freight invoice and payment processing on U.S. Bank's freight payment network.

Syncada is the established third party payment system for defense household goods programs.
Maintained by
Globiquity.ai™
D

DEEL

Global payroll and Employer of Record services for international workforce, covering compliant employment across the countries where the platform is deployed.

Maintained by
Globiquity.ai™
B

Brex

Corporate credit card capability, extending the card program beyond what the current treasury rail supports.

Maintained by
Globiquity.ai™
QB

QuickBooks

Accounting synchronization, so invoices and payments reconcile into the customer's books without rekeying.

Maintained by
Globiquity.ai™
03 · Security program

Security and compliance program

Household goods relocation data carries personally identifiable information and, for defense programs, controlled unclassified information. Globiquity.ai™ is building its security and compliance program around that reality. Below, the controls in place today are listed separately from the program's roadmap.

Globiquity.ai™ will provide its current security posture and documentation package under appropriate agreement.
The platform is being built so those controls apply from the data layer up rather than being added at the perimeter later.
In place todayAs of October 2026
  • Central sign-in with secure password hashing and automatic lockout after repeated failed attempts
  • Multi-factor authentication (authenticator app) available to every user
  • Short-lived sessions, revoked when a password changes or a user is disabled
  • Role-based access control across the products
  • Records scoped to each customer organization in the application
  • Live shipment location visible only to authorized users, by role and assignment
  • Encrypted database connections
  • Rate limiting and strict input validation on sign-in and core application APIs
  • Audit log of sign-in events and of changes to relocation records
  • Automated security scanning on every code change
Security roadmapAll items planned
  1. Mutual Transport Layer Security (mTLS)
  2. Department of War approved External Certificate Authority (ECA) certificates
  3. Protection of Controlled Unclassified Information (CUI) and Personally Identifiable Information (PII)
  4. National Institute of Standards and Technology (NIST) Special Publication 800-171 requirements
  5. Cybersecurity Maturity Model Certification (CMMC) Level 2 requirements
  6. Programmatic retention and purge of Personally Identifiable Information (PII)
  7. Federal Risk and Authorization Management Program (FedRAMP) certification
04 · Questions

Frequently asked questions

01Is this one platform or two products?

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.

02Do we have to replace our existing systems to use it?

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.

03How does the platform connect to our systems?

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

04What is running in production today, and what is planned?

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

05How is defense data kept separate from commercial data?

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.

06What is your current security and compliance status?

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.

07Can the same platform run defense household goods and commercial workforce relocation?

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.

08How do we settle payments?

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.

09What does it take to get started?

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.

10How do we get the technical documentation?

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