Day one is the day nobody budgets for#
The feature work is not what makes a new project slow. It is everything before it. Pick a stack, wire an ORM, write the first migration, stand up auth, generate a secret, get CORS right, point the frontend at the backend, add a database, then do it all again for the environment your teammate is on. Two days gone and you have not written a line of product code.
A blueprint removes that day. Not by generating a starter repo you still have to host, but by provisioning the running system.
What the blueprint does instead of you#
Open the Elysia + TanStack Dashboard blueprint and press deploy. Rock8Cloud does the following before you have opened an editor:
- Clones the monorepo into your own GitHub account, one repo for both services
- Creates two services from it, an Elysia API on Bun and a TanStack Start web app
- Provisions a managed PostgreSQL database and passes it to the API
- Generates the auth secret, so no shared plaintext and nothing to invent
- Gives each service the other’s public URL, so CORS and callbacks are correct on the first try
- Runs the migrations as the API boots
- Seeds a demo account, so there is something to log in as
The result is not a template on your laptop. It is a signed-in dashboard on a real URL, with a database behind it and a repository you own.
Yours after minute one#
A blueprint is a starting point, not a cage. What it creates are ordinary Rock8Cloud services running ordinary open tech from your own repository. Change the schema and push. Swap the UI library. Add a worker, or a Dragonfly cache, or a second API. Delete the demo user once you have your own.
The wiring you did not have to do is not hidden from you either. The database URL, the auth secret and the cross-service URLs are all normal environment variables on normal services, there to read and there to change.
Start free#
Deploy the blueprint, then make it yours. 60 days free, no credit card required.