Openatthemodellayer,theintegrationlayerandtheruntime
An enterprise commits to a platform it can exit. That makes openness a commercial requirement rather than a philosophical position — and it is what CONNECT means in practice.
Wheretheplatformconnects
Models
Commercial APIs, open-weight models, private fine-tunes, domain models and first-party models, selected by policy per workload.
Integrations
ERP, CRM, GIS, SCADA, IoT, databases, warehouses and enterprise SaaS through declared, brokered operations.
MCP
Model Context Protocol servers registered, version-pinned, scoped per mandate and monitored as privileged integrations.
Infrastructure
Conformant Kubernetes as the deployment substrate, so the platform runs where you already run things.
Developers
APIs, ontology schemas, the agent runtime and architecture references.
Identity providers
OIDC federation, so human identity stays where it already is.
Partnercategories
Separated because they are genuinely different relationships with different obligations.
Technology partners
Companies whose products integrate with the platform, or whose products the platform integrates with under governance.
Infrastructure partners
Capacity, connectivity and facility relationships that support the deployment postures we commit to.
Research partners
Academic and public research collaborations feeding Labs. These are research relationships and are not described as commercial ones.
Delivery partners
Consultancies and systems integrators who deliver the platform in regulated environments.
Strategic partners
Longer-term arrangements spanning product, infrastructure or market access.
On logos
We do not display partner or customer logos without a real, current relationship and explicit permission — and we do not present research or ecosystem adjacency as a commercial relationship. If a logo is not here, that is usually why.
Marketplace
There is no marketplace today. A marketplace becomes worth building when there are enough governed integrations and enough customers to make discovery a real problem, and describing one before that point would be describing a roadmap slide as a product.
What exists now is the mechanism a marketplace would eventually sit on: declared operations, registered MCP servers with pinned versions, and per-mandate scoping. That is the part that has to be right first.
Questions
- How do we become a delivery partner?
- Through a conversation about the environments you already deliver in and the engineering capability you hold. Delivery partnership carries obligations around governance and evidence that project work does not, so it is a substantive discussion rather than a form.
- Can our product be integrated?
- If it has an API or an MCP server, usually yes. The work is declaring the operations and scoping them, which is deliberately a design step rather than a credential exchange.
- Do you resell infrastructure?
- No. Infrastructure relationships exist to support the deployment postures the platform commits to, not as a separate line of business.
Bring us one operational problem.
You do not need a finished brief. Bring the problem — we will work out the next step together.
Or book a call with the team