Create your SPINE
A name and your email. We host it, set it up, and you sign in as its owner.
What that means
Name your SPINE
One answer names everything else — and it's what your team will see.
Where should SPINE run?
Enhanced AI Hosted
We run the Worker on our infrastructure. Nothing to connect — pick your storage next.
Your own cloud
SPINE runs in your account. You connect the platform and hold the keys.
Cloudflare
Provisioned for you into your Cloudflare account — two tokens, about five minutes.
Vercel
A verified, ready-to-deploy build you ship yourself — full guide provided.
Storage & sign-in
Your data and your team's accounts live in the same database — this choice sets both.
Light Project
Enhanced AI provisioned — instant, shared infrastructure, isolated at the database level.
Dedicated Project
Through Enhanced Partnership — $20/mo for your first project, $15/mo for each additional.
Your own DB connection
Your own Supabase project — you hold the credentials outright.
Where should this SPINE’s code live?
Apps you install commit their own source under apps/<name>/. This
chooses who owns the repository they commit to.
We provision one
A private repository in our GitHub organisation, connected automatically. Nothing to set up, and you can move it to your own account whenever you like.
Your GitHub
We create the repository in your own account or organisation, so it is yours from the first commit. Needs a token you generate — one click below.
A repo you already have
Push into a repository that already exists. Name it and give a token that can write to it.
No repository
Apps still work; their source just has nowhere to go. You can connect one later at Settings → Repository.
AI model optional — everything else works without it
SPINE’s own tools — drafting app manifests, explaining capability gaps, the dashboard chat — need a model to call. Apps you build can use it too.
Color optional
Each of these is the real thing your dashboard will look like — the swatches are the instance's own tokens, so what you pick here is what gets built.
Your email
Two things at once: we email you the credentials, and we make you the owner of this SPINE — which is how you sign in with Google instead of keeping an admin token.
Last thing — then we build it
No accounts to create, no tokens to paste. We host it; your data stays isolated at the database level.
What shared actually means
Request provisioning
A person reviews these — nothing runs until we set it up and reply.
Connect Vercel
SPINE deploys to your Vercel account from a verified prebuilt bundle — your token is used once, right from this page, and never stored.
Show technical detail
Connect Cloudflare
Your SPINE runs in your own Cloudflare account. We use this key once and never save it.
- Create a key in CloudflareEverything is filled in for you. Click Continue to summary, then Create Token, and copy it.
- Check it
Rather do it by hand? Step-by-step
- Open dash.cloudflare.com → API Tokens and click Create Token.
- At the top, under Custom token, click Get started. Not the template list underneath. Edit Cloudflare Workers is the closest one and it is still missing the permission that registers a first workers.dev subdomain — fine if this account has deployed a Worker before, a dead end if it has not.
- Name it
spine. - Under Permissions, add two rows — the three dropdowns are group · resource · level:
Account·Workers Scripts·EditAccount·Account Settings·Edit - Under Account Resources, choose the account you want SPINE to live in.
- Only if you plan to host a React or Vue frontend here: add a third row,
Account·Workers Builds Configuration·Edit. Cloudflare has no documented way to pre-select this one, which is why the button above fills in two permissions and not three. Skip it if you are not sure — a token without it provisions a SPINE perfectly, and adding it later is editing the token, not remaking it. - Leave Client IP Filtering and TTL alone → Continue to summary → Create Token.
- Copy the token and paste it above.
workers.dev URL. Three calls, once. Your running SPINE never uses this token — it is safe to revoke the moment the wizard finishes.Connect Supabase
Your data and your team’s accounts live in your own Supabase database. We use this key to set it up.
- Create a key in SupabaseClick Generate new token, name it
spine, and copy it. It is shown once. - Check it
Rather do it by hand? Step-by-step
- Open supabase.com → Account → Access Tokens and click Generate new token.
- Name it
spine. There are no permissions to choose — a Supabase PAT carries your whole account, which is exactly why this one is used once and never stored. Revoke it when the wizard finishes. - Copy the
sbp_…value — shown once — and paste it above.
If you are on the free plan you may have two active projects. At the limit, either pause one in Supabase or choose Use an existing one in step 2 — the schema is additive and skips anything already present.
Make it yours
Only the database is required. Everything else can be added later in Settings.
Powers SPINE’s built-in AI helpers. One FluxPrompt key covers every major model. Skip it if you like.
- Get a keyThen Settings → Generate Api Key → Show, and copy it.
-
We check it straight away.
What this unlocks, and the steps
- Register at app.fluxprompt.ai/register — the free tier is enough to get a key.
- Open app.fluxprompt.ai/settings and click Generate Api Key.
- Click Show, copy the key, and paste it above. We check it against FluxPrompt’s live model catalogue immediately and tell you how many models it reaches.
Fully optional. Every other part of SPINE — the gateway, apps, auth, the dashboard — works with no model at all. Only the LLM-backed tools (drafting app manifests, explaining capability gaps, the dashboard chat) need one, and they will tell you so rather than failing quietly.
Use a direct provider key instead
A new repo on your GitHub
We create it in your account and copy SPINE in. You hold the code outright.
A repo you already have
Join an existing repository. Nothing in it is touched — apps only add their own
folders under apps/.
Enhanced AI keeps it
We hold the repository and give you access. No token to create.
apps/.- Create a GitHub keyThe one permission needed is ticked. Set Expiration to 90 days or No expiration — your apps use it every time they save code.
-
We check it straight away.
Prefer a fine-grained token? Step-by-step
- github.com → Settings → Developer settings → Fine-grained tokens.
- Resource owner: your own account. Repository access: All repositories (the repo does not exist yet, so it cannot be selected).
- Permissions →
Contents: Read and writeandAdministration: Read and write— Administration is what creates the repo.
Why is this key kept?
Everyone signs in with their own email — no shared keys to pass around.
What can each role do?
Manager adds and removes people, but does not change how it works.
Member uses the apps, nothing more.
Everyone gets an email with a one-time link to sign in for the first time.
More sign-in options
GitHub sign-in, for developers
Appearance — theme and accent colour
Building your SPINE
Show technical detail
Yours
spine.report_problem) upstream to Enhanced AI, so the
framework learns what building on it costs. No credentials, arguments, or user data are ever
included, and you can turn it off by removing the SPINE_REPORT_UPSTREAM variable.