BluestaqThe Architecture of Trust.

BLUESTAQ /ARQ™

One governed record store. Rights enforced on every record.

  • Today · Rights enforced
  • 3 countries
  • 5 domains

BLUESTAQ /ARQ™ is the governed record layer: connect the sources you already run in place, govern access down to the record, and put the data in the hands of the people and apps that need it. Nothing to replace.

SOURCES INEverything you already run, in place.Sensors, radars, aircraftDatabases and IT systemsPartner and allied feedsCommercial data from /MARKETVIA /ARQ INTEROP · OPEN STANDARDSNO MIGRATION · NO RIP-AND-REPLACEData stays at the source.Connection is configuration, not a project.BLUESTAQ/ARQ™ONE GOVERNED RECORD STORETrack 4471SECRETObservation 9032UNCLASSReport 118TS // SCIRIGHTS ENFORCED ON EVERY RECORDRECORD-LEVEL ACCESSAUDIT ON EVERY NODEWho may see which record, everywhere it moves.APPS OUTThe tools your people already use.Dashboards and analyticsC2, GIS and SIEMApps you build on /LAUNCHPartners, rights-slicedRIGHTS CHECKED ON EVERY READONE CREDENTIAL · EVERY PATTERNNothing to rip out.The exit door stays unlocked, including from us./ARQ FabricINSTANCES LINKEDFederate, sync and replicate between instances:many instances, one governed fabric./ARQ AIMODEL-AGNOSTIC, ON GOVERNED DATAThe Librarian answers in plain language withonly what you are cleared to see./ARQ InteropOPEN STANDARDS, TWO-WAYREST · Kafka · OpenAPI · JDBC/ODBC · SDKs · MCPSources in, apps out, one credential.RUNS WHERE THE DATA HAS TO REACH/ARQ CloudCONNECTED/ARQ EnclaveCLASSIFIED, AIR-GAPPED/ARQ EdgeINTERMITTENT/ARQ MobileDISCONNECTEDSOURCES INEverything you already run, in place.Sensors, radars, aircraftDatabases and IT systemsPartner and allied feedsCommercial data from /MARKETVIA /ARQ INTEROP · OPEN STANDARDSBLUESTAQ/ARQ™ONE GOVERNED RECORD STORETrack 4471SECRETObservation 9032UNCLASSReport 118TS // SCIRIGHTS ENFORCED ON EVERY RECORDAPPS OUTThe tools your people already use.Dashboards and analyticsC2, GIS and SIEMApps you build on /LAUNCHPartners, rights-slicedRIGHTS CHECKED ON EVERY READ/ARQ FabricINSTANCES LINKEDFederate, sync and replicate: many instances, one fabric./ARQ AIMODEL-AGNOSTIC, ON GOVERNED DATAThe Librarian: plain language, only what you may see./ARQ InteropOPEN STANDARDS, TWO-WAYREST · Kafka · OpenAPI · JDBC/ODBC · SDKs · MCPRUNS WHERE THE DATA HAS TO REACH/ARQ Cloud/ARQ Enclave/ARQ Edge/ARQ Mobile

THE RECORD LAYER IN YOUR DOMAIN

Defense and intelligence teams run /ARQ as the governed record layer under the systems they already operate. Sensors, vehicles and platforms at the tactical edge write into it; mission apps, C2 and analytics read from it through open standards, without re-engineering a single source. Every record carries its rights, so who may see what is enforced at the record level everywhere the data moves, and every access is logged on every node it touches. Sharing with an allied partner is a deliberate choice: distribution controls and security tagging release exactly the records you choose, and nothing else. When the link home is denied or degraded, edge nodes keep sharing with each other and resync when connectivity returns. The same product runs in the cloud, in the enclave, at the edge and on a phone, at the levels your authorizing official approves. AI assistants and agents reach the data through MCP under the same identity and permissions as a human user.

Talk it through

IN PRACTICE

What this means
for your team.

01

Connect, not start over.

Your sensors, databases and partner feeds stay where they are. /ARQ Interop, the component of /ARQ that connects what you already run, joins them through open standards and APIs (REST, Kafka, OpenAPI, JDBC/ODBC, SDKs, MCP); integration is configuration, not a capital project. Commercial data bought on /MARKET lands in the same governed instance.

02

Access is part of the architecture.

/ARQ governs access down to the record: who may see which record, everywhere the data moves, with identity and authorization checked at every hop and every access logged. Rights and licence terms travel with the record, so a share to a partner, an enclave or the edge is a deliberate choice, never a copy that escapes its terms.

03

Keep the tools that do the work.

Deliver governed records to the dashboards, C2, GIS and operational systems you already use, to the apps your own teams build on /LAUNCH, and to the models and agents /ARQ AI puts to work. The data is held in open forms you can take with you: no lock-in, including to Bluestaq.

WHAT YOU GET

What the record layer gives your team.

What /ARQ does for your team, as it runs today.

Rights enforced on every record.

Access is governed down to the record, who may see which record everywhere the data moves, so security travels with the data instead of staying behind at the source.

Open standards, no lock-in.

REST, Kafka, OpenAPI, JDBC/ODBC, SDKs and MCP connect what you already run; data is held in forms you can take with you, including away from Bluestaq.

Move across domains at approved levels.

Distribution controls and security tagging make every cross-domain share a deliberate choice, released at the levels your authorizing official approves.

Nothing to rip out.

Sources connect in place through open standards without touching their internals; integration is configuration, not a capital project.

Model-agnostic AI on governed data.

/ARQ AI runs on your data, your models and your infrastructure, remote APIs or local GPUs, with the Librarian answering only from what you are cleared to see.

Sovereign by design.

Each organization or nation runs its own instance, holds its own keys, connects to partners when it chooses and disconnects when it must.

Provenance and audit, built in.

Every access is logged end to end on every node the data touches, a full record of who reached what and when; audit is a property of the platform, not an add-on.

79 schema families, 1,748 operations.

One published service catalog serves space, air, maritime, land and cyber as mission views of the same families, including the governance families that carry record-level access.

BLUESTAQ /ARQ™The Architecture of Trust./ARQ CloudCOMMERCIAL OR GOV CLOUDCONNECTED/ARQ EnclaveYOUR FACILITY, CLASSIFIEDCONNECTED/ARQ EdgeRUGGED LAPTOP OR CASEINTERMITTENT/ARQ MobilePHONE OR TABLETDISCONNECTEDSYNC WHEN BACKRights enforced everywhere. The same data, the same rules, whether the link is up or not.

Pinch to zoom, drag to pan.

Cloud, enclave, edge and mobile: the same product and the same rights at every tier; nodes keep sharing edge to edge when the link home is gone and resync when it returns.

CONTINUE EXPLORING

The next useful question.

Explore Bluestaq.

Bluestaq PlatformONE SECURE, OPEN PLATFORM

Products

/ARQPRODUCT OVERVIEW/MARKETPRODUCT OVERVIEW/TRUTHPRODUCT OVERVIEW/LAUNCHPRODUCT OVERVIEW

/ARQ FEATURES

/ARQ DeploymentsCLOUD TO MOBILE/ARQ AIAI ON GOVERNED DATA/ARQ InteropOPEN API AND CATALOG/ARQ FabricINSTANCES, LINKED

Reference

Trust & ownershipYOUR DATA, YOUR CONTROLSThe integration taxARTICLEYour second data estateWHITE PAPER · PDFDecisions have a supply chainWHITE PAPER · PDF

Company

Company & venturesWHO WE AREWhat we doCAPABILITY AND DELIVERYNewsPRESS AND UPDATESCareersJOIN THE TEAMTalk to BluestaqSTART A CONVERSATION

Ask a question or choose a page. Roadmap and early-access material carry their status labels.