Sovereign Intelligence Platform
Transparent documentation of what's implemented, what requires configuration, and what's on the roadmap.
Enterprise software vendors often claim "integrations with 500+ systems" when they really mean "we have an API." We believe in honesty about what works out of the box versus what requires your team's effort.
The Sovereign Adapter Architecture: Rather than maintaining hundreds of brittle vendor-specific connectors, Datacendia provides 5 universal adapters that work with standard protocols. We provide the socket; you bring the plug that fits your specific systems.
| Status | Meaning |
|---|---|
| ✅ Implemented | Works out of the box with standard configuration |
| ⚙️ Client-Configured | Adapter ready; requires your credentials/endpoint configuration |
| 🔧 BYO-Connector | You provide the connector; we provide the integration framework |
| 📋 Roadmap | Planned for future release |
| ❌ Not Planned | Not supported due to licensing, compliance, or technical constraints |
These adapters work with any system that supports the respective protocol:
| Adapter | Protocol | Use Cases | Status |
|---|---|---|---|
| Database Adapter | SQL (PostgreSQL, MySQL, SQL Server, Oracle) | ERP systems, data warehouses, custom databases | ✅ Implemented |
| Webhook Ingest Adapter | HTTP/HTTPS webhooks | SaaS applications, event-driven integrations | ✅ Implemented |
| File Watcher Adapter | File system monitoring | Legacy systems, batch exports, air-gapped transfers | ✅ Implemented |
| FHIR Adapter | HL7 FHIR R4 | Healthcare EHR systems (Epic, Cerner via FHIR) | ✅ Implemented |
| FIX Protocol Adapter | FIX 4.4/5.0 | Financial trading systems, market data | ✅ Implemented |
| MQTT Adapter | MQTT 3.1.1/5.0 | IoT sensors, industrial systems | ✅ Implemented |
| Database | Status | Notes |
|---|---|---|
| PostgreSQL | ✅ Implemented | Native driver included |
| MySQL / MariaDB | ✅ Implemented | Native driver included |
| Microsoft SQL Server | ⚙️ Client-Configured | Driver available; requires your connection string |
| Oracle Database | ⚙️ Client-Configured | Requires Oracle Instant Client (licensing on you) |
| MongoDB | ✅ Implemented | Native driver included |
| IBM DB2 | 🔧 BYO-Connector | Requires IBM client libraries |
| Snowflake | ⚙️ Client-Configured | Via SQL adapter with your credentials |
| Databricks | ⚙️ Client-Configured | Via SQL adapter with your credentials |
| System | Status | Integration Method |
|---|---|---|
| SAP (S/4HANA, ECC) | 🔧 BYO-Connector | Via RFC/BAPI or OData—you provide SAP connector |
| Salesforce | ⚙️ Client-Configured | REST API with your OAuth credentials |
| Microsoft 365 / SharePoint | ⚙️ Client-Configured | Graph API with your Azure AD registration |
| Workday | ⚙️ Client-Configured | REST API with your tenant credentials |
| ServiceNow | ⚙️ Client-Configured | REST API with your instance credentials |
| Jira / Confluence | ⚙️ Client-Configured | REST API with your Atlassian credentials |
⚠️ Important: Premium financial data feeds (Bloomberg, Refinitiv, FactSet) require expensive licensing agreements between you and the data provider. We cannot bundle these—their redistribution terms prohibit it. We provide the integration framework; you bring the license.
| Provider | Status | Notes |
|---|---|---|
| Bloomberg Terminal | 🔧 BYO-Connector | Requires Bloomberg B-PIPE license ($24k+/user/year) |
| Refinitiv/Reuters | 🔧 BYO-Connector | Requires Refinitiv Elektron license |
| Public Market Data (Yahoo, Alpha Vantage) | ⚙️ Client-Configured | Via REST adapter with your API keys |
| SWIFT | ❌ Not Planned | Requires SWIFT CSP certification—out of scope |
⚠️ Important: Healthcare integrations require a Business Associate Agreement (BAA) between you and your EHR vendor. Datacendia provides the FHIR adapter; you bring the BAA and credentials.
| System | Status | Notes |
|---|---|---|
| Epic (via FHIR) | ⚙️ Client-Configured | FHIR R4 adapter ready; requires your Epic credentials + BAA |
| Cerner (via FHIR) | ⚙️ Client-Configured | FHIR R4 adapter ready; requires your Cerner credentials + BAA |
| Epic (proprietary APIs) | ❌ Not Planned | Non-standard APIs require Epic certification |
| System | Status | Notes |
|---|---|---|
| Local File-based Keys | ✅ Implemented | Default for development and air-gapped environments |
| HashiCorp Vault | ✅ Implemented | Transit secrets engine for signing/encryption |
| AWS KMS | ⚙️ Client-Configured | Adapter ready; requires your AWS credentials and key ARN |
| Azure Key Vault | ⚙️ Client-Configured | Adapter ready; requires your Azure AD credentials |
| Hardware HSM (PKCS#11) | 📋 Roadmap | Planned for enterprise deployments |
| Provider | Status | Notes |
|---|---|---|
| Keycloak (OIDC) | ✅ Implemented | Full SSO integration |
| Azure AD / Entra ID | ⚙️ Client-Configured | Via OIDC with your tenant configuration |
| Okta | ⚙️ Client-Configured | Via OIDC with your Okta credentials |
| SAML 2.0 | ⚙️ Client-Configured | Supported via Keycloak federation |
Some vendors claim integrations that are technically impossible or legally problematic. We're explicit about what we don't support:
What we actually provide: 6 universal adapters (Database, Webhook, File Watcher, FHIR, FIX, MQTT) + a framework for client-configured connections. If your system speaks SQL, REST, or a standard protocol, we can connect. If it requires expensive licenses or vendor certifications, that's on you to provide.
Our principle: "We provide the socket; you bring the plug."
Request a technical briefing to discuss your specific systems and integration requirements.
Request Briefing →