16 — Infrastructure and Deployment Architecture
Status: Approved launch decision; production evidence required
July 30 ownership
| Concern | Owner / runtime |
|---|---|
| Browser identity | Clerk production |
| Account and tenant resolution | Gateway on Cloudflare |
| Workbench | Next.js on Vercel at app.integratewise.ai |
| Provider OAuth | Nango credential wall |
| Canonical truth | Neon, written through Pipeline |
| Bounded edge state | D1 and KV |
| Files and immutable evidence | R2 |
| Retrieval indexes | Vectorize / AI Search |
| Public OAuth-protected MCP | Gateway + MCP Connector |
| Approval and execution | Governance → Hermes |
This is a hosting correction for the server-rendered Workbench, not a backend
migration.
Runtime path
Browser
→ app.integratewise.ai
→ Clerk
→ gateway.integratewise.ai
→ account / tenant resolution
→ Integration Manager and platform APIs
→ Nango / Pipeline / Projection Engine / Governance / Hermes
→ Neon + bounded Cloudflare state
Environment progression
local → preview → integration-test → development → staging
→ customer-zero → marketplace-certification → production
Every environment has independent secrets, callback URLs, audit, tenant data,
deployment version, migration state, rollback target, monitoring, and test-data
policy.
The three governing operating environments are:
| Environment | Rule |
|---|---|
| Development | Synthetic/test data and isolated Development Neon, D1/KV/R2/queues/search only. |
| Customer Zero | Dedicated production-shaped internal tenant resources; never a general test tenant. |
| Customer Production | Tenant-isolated production resources, with dedicated cells for contractual, residency, scale or regulatory requirements. |
Shared stateless Cloudflare Platform Workers are the default compute topology.
Workers for Platforms is reserved for customer-supplied or agent-generated code
that must be deployed in isolated Workers; ordinary multi-tenant Platform
services do not require one Worker per tenant.
Shared configuration
One controlled environment registry supplies service bindings and validated
configuration to Cloudflare, Vercel, GitHub Actions, connector OAuth apps, MCP,
Customer Zero, and production. Secrets are never copied into shared repository
files, Workbench bundles, or documentation.
Stop-ship infrastructure defects
- two selectable browser identity authorities;
- unresolved account or tenant membership;
- provider tokens outside Nango;
- UI or Twin direct canonical writes;
- D1 described or used as business truth;
- public MCP tool-count drift;
- unhealthy required endpoints;
- unreviewed migrations or no rollback target;
- cross-environment credential reuse;
- demo fallback masking live failure.
Vercel note
The repository's Vercel CLI was observed at 54.18.6, behind 58.1.0. Upgrade
with pnpm add -g vercel@latest before deployment verification.