Deploy and go-live checklist
Order matters: the system stays private until the last step.
Product domain
aetherin.appis the Aetherin tools portal; individual products use their own subdomains.streamproof.aetherin.appis attached to the Streamproof Vercel project. The apex remains assigned tokimi-gateway.- Adding a domain does not make Streamproof public: Vercel Authentication remains enabled.
1. GitHub (private first)
- Create a free organization in the browser: https://github.com/organizations/plan (GitHub does not allow creating organizations through its API).
- Create a private repo
streamproofin it, then:
git remote add origin git@github.com:<org>/streamproof.git and git push -u origin main.
- CI (
.github/workflows/ci.yml) runs typecheck and tests on every push.
2. Vercel
vercel login, thenvercel link(new projectstreamproof). Choose the team you want it under.- Add a Redis store from the Vercel Marketplace (Upstash, free tier). It injects
KV_REST_API_URLandKV_REST_API_TOKEN. In production the API refuses to start without it, so spend can never be silently lost. - Set environment variables (Production, Sensitive):
UPSTREAM_BASE_URL,UPSTREAM_API_KEYCLIENTS_JSON: only SHA-256 hashes of client keysPRICES_JSON: enabled models with prices per million tokensADMIN_TOKEN: at least 24 random characters (guards/api/usage)- In the Git integration, connect the repo so every push to
maindeploys.
3. Keep it private until launch
- Turn on Deployment Protection (Vercel Authentication) for all deployments. Nothing is reachable without a Vercel login.
- Keep the GitHub repo private.
- Test with your own client key via the protection bypass header or a protection-bypass token.
4. Verify
POST /v1/chat/completionswith a client key returns a reply, andGET /api/usage(BearerADMIN_TOKEN) shows spend rising.- Exceeding the budget returns 402, exceeding RPM returns 429, a wrong key returns 401.
- Redeploy: spend must survive (it lives in Redis, not in the function).
5. Open to the public
- Rotate
ADMIN_TOKENand every client key used in testing. - Disable Deployment Protection for production only after explicit approval. The custom domain is already attached and is also protected.
- Replace the
mailto:links with your payment or booking link. - Confirm the pricing and the comparison table against each vendor's current docs.
Key hashing
node -e "console.log(require('crypto').createHash('sha256').update('sk-acme-...').digest('hex'))"