The clone manifest: what a self-hosted Hub is.
The provisioning runbook, the afternoon-install recipe, is itself product: installer plus presets plus a consulting conversation. It's being written against the manifest above.
Your own Supabase
Database, auth, row-level security, edge functions.
Vercel
The app, deployed from your fork.
A worker host
Any small always-on Linux box: daemons, dispatcher, executor, the broker.
Nango
Token lifecycle. Self-hosted is free to 1,000 connections.
Airbyte
On its own box or cloud, 4 to 8 GB minimum.
A secrets vault
Often forgotten. Cloud KMS by default, or your own.
Your own AI keys
Bring your own. Your model bill never touches us.
A backup destination
Your bucket, verified nightly. A backup that hasn't restored is not a backup.
Alerting pointed at your human
Also often forgotten, and the reason things break quietly.
Four rungs from hosted to yours.
Design law from day one: a tenant's presence stays liftable. Config exportable, data behind one boundary, connections under their own accounts.
- 01
We host and operate.
- 02
We host, your admins run it.
- 03
You own every account, credential and billing relationship.
- 04
You self-host the AGPL core and keep licensing the skills layer, or not.
Moving a hosted Hub into your own infrastructure.
- 01
Define
Freeze the portability contract: the supported release, exported records, excluded operational data, dependencies, support owner, downtime window and rollback point.
- 02
Provision
Build the destination boundary: database, storage, identity, worker runtime, observability and backups, from versioned configuration.
- 03
Reissue
Providers issue new client-controlled credentials into authorised destination homes. No secret value is exported from our custody.
- 04
Move
Import the library, skills, approved configuration, task and run history and required derived records, with checksums and tenant identifiers intact.
- 05
Prove
Replay acceptance and negative tests: identity isolation, source freshness, skill outputs, gate invalidation, broker refusal, audit evidence, backup restore.
- 06
Cut over
Run in parallel, resolve drift, move traffic deliberately, keep a time-boxed rollback path before the old custody is retired.
Status: planned, not built. No portability tooling exists. This is a designed sequence, not a self-service export.
More docs
Architecture
The topology: four zones wired around one record, where agents run, and the four ways a worker is started.
Security
Row-level security as the whole authorisation story, the credential broker, the ten-check gate chain, and what has actually been made to fire.
The stack
Next.js, TypeScript, Supabase, Nango, Airbyte, n8n and Vercel: what each does, what's being rebuilt, and what a stranger needs to run it.
Data plane
How client data reaches Hub: Airbyte into a fenced landing zone, thin transforms, a freshness stamp on every number.
Automations & skills
The split: one repo per organisation, a birth certificate for every automation, skills whose home is git.
Status
The capability matrix, five labels, no hedging. What you could use this afternoon versus what needs a switch or a sitting.
Self-hosting
The clone manifest and the transfer sequence: what you stand up, what moves, what never leaves our custody.