Swfte Intelligence Platform
A customer-hosted, time-aware graph of the organisation with an evidence status on every fact, designed so that findings can become governed agents and workflows.
Best for: Organisations that want a controlled picture of people, groups and ownership to give AI agents context, and that can start from directory data. Not a warehouse, a lakehouse or a dashboard tool today.
Data sources and connectors: Built today: directory sources (Active Directory and LDAP, Microsoft Entra ID, Okta, Google Workspace). Cloud, code, Kubernetes, database, SaaS and document sources are designed for. The connector list beyond directory sources is open.[1][2]
AI-native analytics and agents: Built: a time-aware graph with an evidence status on every fact, and a local API that serves graph, as-of, coverage and evidence reads. Designed for: plain-language questions, trend detection, dashboards and wiring findings into agents.[1][2]
Data governance and access control: Built: token-scoped API with the tenant taken from the credential, row-level tenant isolation, a hash-chained audit log, and answers limited to what the person asking may see. Designed for: an action gateway with approvals.[1][2]
Deployment and data residency: Customer-hosted: a virtual machine with Docker, Kubernetes with Helm, or an air-gapped route. Connected, private and air-gapped modes. In air-gapped mode no outbound link is started.[1]
Pricing transparency: <pricing - founder to fill> <availability - founder to fill>[1]
APIs and extensibility: Built: a token-scoped local API for graph, people, groups, coverage and audit. Designed for: a context-package API and an MCP server.[1]
Built and designed, kept apart:
| Capability | State | Note |
|---|---|---|
| Directory sources: Active Directory / LDAP, Microsoft Entra ID, Okta, Google Workspace | Built | People, groups, reporting lines and accounts, read with a read-only account. Passwords and credentials are never read or stored. |
| Identity resolution into people and org structure | Built | Accounts across directories are resolved into people, with the resolution evidence kept on the link. |
| Time-aware graph store | Built | Insert-only history, as-of reads, evidence statuses on facts, tenant isolation and a hash-chained audit log. |
| Local API for graph, people, groups, coverage and audit | Built | Token-scoped, with the tenant always taken from the credential, never from the request. |
| Outbound link: enrolment, mutual TLS, signed commands, kill switch, outbox, signed updates | Built | Customer-killable, and absent entirely in air-gapped mode. |
| Packaging: container image, installer, Helm chart | Built | Virtual machine with Docker, Kubernetes via Helm, and an air-gapped route. |
| Pre-model sanitisation gateway | In progress | Designed to clean content before it reaches a model. |
| Cloud, code, CI/CD, Kubernetes and database collectors | Designed for | On the roadmap. This is what lets the graph answer who owns a service, not only who a person is. |
| SaaS, business-system and document sources | Designed for | On the roadmap. <connector list beyond directory sources - founder to fill> |
| Context-package API and MCP server | Designed for | On the roadmap. Designed so an agent can ask for the context it is allowed to have. |
| Action gateway with approvals | Designed for | On the roadmap. Designed so agents act only through typed, approved and audited capabilities. |
| Production control plane | Designed for | On the roadmap. |
| Cloud marketplace delivery | Designed for | On the roadmap. <marketplace listings - founder to fill> |
| Wiring into Cortex, Nexus, Studio and the Nexus harness | Designed for | On the roadmap. Each is designed to read organisational context from the graph. |
| Graph explorer, org and ownership maps, as-of timelines, coverage and evidence views | Designed for | The local API already serves the data these views read: the subgraph, as-of reads, coverage and evidence. The views themselves are design intent. |
Watch-outs:
- Today it reads directory sources only. Cloud, code, SaaS and document sources are on the roadmap.
- Plain-language questions, dashboards and trend detection are design intent, and named dashboards and chart types are not published.
- Not a data warehouse, lakehouse or business intelligence replacement.
- Pricing and availability are not published. <pricing - founder to fill> <availability - founder to fill>
- A pre-model sanitisation gateway is in progress. Do not assume content is cleaned before it reaches a model.
- Compliance wording: this is built for compliance-by-design, not “compliant”. Swfte does not hold a SOC 2 report, an ISO 27001 certificate or a HIPAA BAA today. A SOC 2 Type I audit is in preparation; the trust page lists what is in place and what is in progress.
Sources: Swfte Intelligence Platform page, Swfte intelligence deployment page (read 2026-10-06).