Integrations

Two small seams. No platform-core changes.

Embed one web component on the front end and implement a five-method adapter on the back end. That's the whole integration surface — your app stays yours, and your auth stays authoritative, because every write still passes the governance gate — permission, policy, approval, audit.

Start integration See the integration paths

The two-seam model

Your app is the body. Cambiary is the brain.

The platform holds zero application-specific code — it never needs to know what your system is. Everything connects through two generic seams, and neither requires a change to the platform core.

Frontend — HostContext

Drop the <agentic-panel> web component into Angular, React, Vue, Razor/MVC, or plain HTML. Pass a references-only context that describes where the user is — no PII blobs, no document bodies. Theme via CSS variables; the host token is passed through config, never localStorage.

Backend — HostAdapter

Implement five methods — validateToken, getContext, getPermissions, executeTool, pushNotification — in-process in TypeScript or out-of-process over HTTP in any language. Your adapter is the authority; the platform issues no identities of its own.

Integrate any app · 6 steps

The same checklist for every stack.

None of these six steps touch the platform core.

Pick a host-app id

Embed the panel

Implement 5 adapter methods

Define tools + risk levels

Register the host app

Author workflow templates

Featured paths

Worked examples for the stacks teams ask about.

Each is a documented approach with worked code — not a pre-built production connector.

The easy case

ABP.io / ASP.NET Zero

If your product is built on ASP.NET Zero, the adapter is a thin translation layer over the auth, permissions, application services, and notifications ABP already ships.

Read the approach →

Hosted commerce

Shopify

A hosted app using OAuth2, where the adapter holds the Admin API token. One adapter serves both storefront shoppers and back-office merchants — persona is just the user's role and permissions.

Read the approach →

Self-hosted commerce

nopCommerce

Self-hosted commerce with JWT auth and C# services. Swapping it for Shopify is an adapter-internal detail, invisible to the platform core.

Read the approach →

Any stack

Build your own adapter

Support desks, internal tools, and multi-system single-tenant orchestration. Implement five methods in-process in TypeScript or out-of-process over HTTP in any language — C#, PHP, Python.

Read the approach →

Compatibility matrix

What integration looks like, by stack.

Adapter effort is qualitative — it reflects how much your existing stack already does for you, not a benchmarked figure.

Stack	Embed	Auth	Adapter effort	Notes
ASP.NET Zero / ABP.io	Angular or MVC	jwt (AbpSession)	Lowest	Thin layer over existing ABP auth, IPermissionChecker, application services, notifications. Reference adapter that exists today.
nopCommerce	Razor/MVC or SPA	jwt	Low	Endpoints over existing C# services; one adapter serves customers and merchants.
Shopify (hosted app)	Storefront / embedded app	oauth2	Low	Small external service holds the Admin API token; platform contract identical to nopCommerce.
Zendesk-style ticketing	Any web surface	jwt / apiKey	Low	Out-of-process, single persona — the simplest shape and a good starter template.
Custom app (C#, PHP, Python, Node)	Angular / React / Vue / HTML	jwt / apiKey / oauth2	Implement 5 endpoints	Any language; no Node required in-process.
Multi-app single tenant	Multiple host surfaces	Per-app	One adapter per app	One tenant registration set; cross-system orchestration on a shared governance + audit layer.

Build status — real vs scaffolding

Honest about what ships today.

These are documented integration approaches with worked code examples. We do not ship pre-built production connectors to Shopify, nopCommerce, or ABP — ask us what a live integration looks like for your stack.

Real today

HostContext contract (Zod + JSON-Schema parity) and the HostAdapter interface
The <agentic-panel> embed web component, run/resume, and live Socket.IO card updates
The host-adapter SDK and HostRegistration model
The single GovernanceGateway invariant — permission ∩ policy ∩ approval ∩ audit on every action
Idempotency handling and append-only audit (references / ids only)
The ASP.NET Zero reference adapter and its seeded candidate-screening workflow

Still scaffolding

Real write dispatch from the gateway to a registered adapter (today /internal/tools/execute returns a stub; the governance, idempotency, and audit pipeline around it is real)
A first-class Tool / Skill / Connector registry — workflow templates are hand-seeded today
MCP exposure (apps ship as MCP servers) — an interface stub alongside the REST adapter
Full multi-tenant SaaS isolation — single-tenant MVP today; tenantId threads through context, runs, audit, and registration

Questions

Integration, answered straight.

Are these pre-built connectors?

No. Cambiary ships a documented integration approach with worked code examples for each stack — not install-and-go production connectors. The contracts, adapter SDK, governance, idempotency, and audit are built; the gateway-to-registered-adapter write dispatch is still maturing. Ask us what a live integration looks like for your stack.

Do we have to change the platform core to add our app?

No. Adding an application means embedding a panel, sending a HostContext, implementing five adapter methods, and registering the app. None of those steps touch platform core — your app plugs into two fixed seams.

Which languages can implement the adapter?

Any. In-process adapters are a TypeScript class; out-of-process adapters expose four HTTP endpoints and can be written in C#, PHP, Python, or anything that speaks HTTP. No Node is required in-process.

Does the platform become a second identity system?

No. The platform issues no identities. It passes your host token to your adapter's validateToken, which is the real authority. Your existing auth and permission systems stay authoritative.

Start with the integration guide.

The adapter SDK and worked examples are in the docs. We'll walk your team through the two seams, the governance gate, and a path close to your stack.

Start integration Read the docs