Third-party interoperability
Sovereign-capable is not the same as isolationist. System9 is designed to run with nothing, and to be an excellent citizen of everything a customer already owns. The position is "and," not "or": a customer does not have to move to the platform to get value from it. The platform can govern, catalog, secure, and reason over an estate that stays exactly where it is, which makes it deployable inside an existing hyperscaler commitment rather than a bet against one. This page consolidates the integration surfaces that are otherwise described across the Data, Security, and Agent topics.
In one paragraph
Federate the customer's identity provider, govern their data in place, keep their keys in their own KMS, use hosted or local models per policy, feed their existing BI and SIEM tools, and let their own agents drive the platform, all over standard protocols, in both directions, under one governance model.
The integration surfaces
| Surface | What connects |
|---|---|
| Identity federation | OIDC, SAML 2.0, LDAP provider aggregates; SAML metadata/response handling with signature verification and a replay store; SCIM provisioning; LDAP bind; CAC/PIV smartcard auth; assurance-level bindings; and just-in-time provisioning: described by standard, not by vendor. |
| Cloud storage & SaaS content | Object stores (S3, Azure, GCS) as first-class table storage; OAuth-scoped SaaS connections (OneDrive, SharePoint, Google Drive, Dropbox); and foreign catalogs/databases registered as federated sources. |
| Secrets & keys | Secrets through local/AWS/Azure/GCP backends; key management bridged to AWS KMS, Azure Key Vault, GCP KMS, and HashiCorp Vault transit, with a bring-your-own-key registry, or entirely in-platform on TPM/PKCS#11/YubiKey. |
| Models | A provider abstraction for hosted or self-hosted runtimes, with a secure provider that redacts before egress: gated by the three AI tiers (none, local-only, or local plus third-party). |
| BI, analytics & metadata | Artifact generation and adapters for Power BI, Tableau, Looker, Sigma, Superset, and Grafana; OpenMetadata-compatible endpoints; catalog export in summary JSON, JSON, DDL, CSV, Parquet and OpenLineage; outbound OpenLineage publishing to DataHub, Marquez, Atlan, Collibra or Purview, off until enabled by a signed capability; and open table/sharing protocols (Iceberg REST, Delta Sharing as server and client). |
| Security ecosystem | Connectors for Splunk, CrowdStrike, Microsoft Sentinel, STIX/TAXII, syslog, webhook, MQTT, and Modbus; an OCSF event schema on the platform's own events; and Sigma rules evaluated as continuous streaming queries. |
| AI & agent ecosystem | A Model Context Protocol server exposing measured agent tools; outbound MCP connectors with tool-to-skill projection; and agent-to-agent interop with signed agent cards, a JWKS endpoint, and clearance-and-trust-filtered discovery. |
| Standard query access | PostgreSQL wire, Redis protocol, Gremlin, GraphQL, and the SQL/KQL/PromQL surfaces. |
Sovereign and integrated, over one governance plane
Every surface above enters the same governed substrate. An external identity lands in the same directory as agents and devices; data governed in place is cataloged and classified without moving; and an external agent gets a scoped, audited, refusable seat, under the platform's governance, not around it.
*Figure: an excellent citizen of what the customer already owns. Identity, storage, keys, BI/SIEM tools, and other agents all enter through one governance plane (identity, classification, policy, audit), so the platform governs an estate in place rather than requiring a migration first.
Table equivalent
| Motion | What it enables | The claim to make |
|---|---|---|
| Coexistence | Keep your warehouse, IdP, SIEM, KMS, and BI tools; add governance, agent accountability, and edge reach on top | "Govern in place": shorter sale, survives a hyperscaler contract |
| Assess-then-land | An assessment producing runnable infrastructure-as-code about an estate not yet run | Revenue before deployment |
| Partner-deliverable | Standard protocols in both directions let an integrator or ISV put it under their own offering | The governance layer is the product; the ecosystem is the reach |
Why it is different
- The customer's data does not have to move. "Govern in place" catalogs, classifies, lineages, and enforces policy on data that stays where it is, a shorter sale than "migrate first."
- The sovereignty dial is per-customer. One customer keeps keys in their own cloud KMS; the next keeps them in a hardware module in a facility with no internet, same platform, same policy path.
- Reachable by other people's agents, under our governance. A partner or customer assistant can be given a scoped, audited, refusable seat via MCP or agent-to-agent interop without the platform owning the assistant.
Across the deployment matrix
- Single-cell & multi-cell, the integration surfaces are the same; federation and foreign sources compose across cells.
- Sovereign / air-gapped, every surface has an in-platform alternative (local identity, in-platform keys, local models), so integration is an option, never a dependency.
- Cloud-enabled: the cloud connectors (storage, secrets, messaging) are available, each behind an egress guard.
Related
- Identity & Access: one directory for federated humans, agents, and devices.
- Signing & Cryptography: key custody, BYOK, and hardware options.
- The AI system (core + edge), the tiers that gate hosted vs. local models.
- Open sharing. Delta Sharing and the Iceberg REST catalog.
- Tools & MCP, the Model Context Protocol surface in both directions.