Choose the right lane model and understand who owns what.
Host mode is the simpler first-release path: the integrator keeps its app shell, branding, bootstrap, and connectivity seams,
while the tenant backend stays on our care. Full mode is the second step, when the tenant wants to own the backend contract too.
xconect, xconecta, xconectb, and xconectc follow one platform contract.
The tenant lanes repeat the same gateway and embedding contract across stacks, while xconecta mirrors the canonical Node.js shape on a different tenant entity.
xconect
Node.js lane
The baseline tenant lane implemented in vanilla Node.js.
xconecta is the same lane shape with another tenant entity behind it. Use xconect when you want the canonical Node.js backend contract.
The integrator owns the visible shell and the tenant backend path.
You ownShell, launcher, tenant backend behavior, payment-session handling, and business orchestration.
Platform still ownsGateway trust rails, request authority, invoices, notifications, and shared runtime contracts.
Host mode
Minimal embedding touch. Tenant backend stays on our care.
The integrator keeps the app and the bootstrap seam while we operate the heavier backend path.
You ownApp shell, branding, authentication, minimal bootstrap, and connectivity into the shared host/runtime path.
We ownTenant backend, session/bootstrap authority, guard and payment flows, and the heavier runtime operations underneath.
Why host mode matters firstIt is the lowest-friction commercial path: minimal touch for embedding, with the tenant backend still on our care.
Technical pathBootstrap session and widget session stay separate.
1
Local app starts bootstrapThe integrator shell resolves local auth and calls POST /api/host-bootstrap when the host is cross-origin.
2
Tenant backend returns bootstrap stateIt signs a short-lived browser-safe bootstrap token and returns host config for the shared pages.
3
Shared host pages use that tokenThe browser calls host APIs with the bootstrap token; the tenant backend stays authoritative for subject resolution and host contract routes.
4
Widget session is minted separatelyThe tenant backend creates catalog and widget sessions; shared runtime packages handle widget renewal in place.
5
Gateway keeps trust authorityRequests, guards, payments, invoices, and notifications still resolve through gateway authority under the hosted tenant backend.
Bootstrap sessionShort-lived browser token for host routes and launcher/bootstrap renewal.
Widget sessionSeparate runtime session minted by the tenant backend and renewed by the shared host/runtime bridge.