- ×4
cheaper to build
- ×9
faster to launch
- ×100
more reliable in production
How it works
From a bare server to your own code in production. Everything below runs on hardware that is yours.
Stand up the server
Deploy it with the Fractera installer robot. You get an operating system, a starter template, the control panel, storage and authorization — installed and wired together.
Develop where you already work
Sync with GitHub, then clone onto your own machine and run Claude Code or Codex. The data keeps coming from your server; the code runs in your own IDE.
Push, and it deploys itself
Finish on the local machine and push the project to GitHub. That immediately starts a new deployment on your own server — and the visitor sees the new project.
How to start
Everything below is already installed — you are switching it on, not building it. The left column is the path; the right one is what saves you from walking it twice.
Six steps from a bare server
- Open the control panel — everything about this server is configured there. Control panel
- Pick the languages your application will ship in. Languages
- Use the settings to describe your project: name, description, logo, SEO. App settings
- Connect GitHub and push the server's code into your repository. GitHub
- Clone that repository onto your own machine, develop there, and push back.
- Press Deploy in the panel — the server takes your commit and rebuilds itself. Deployments
Recommended before you start
Neither blocks anything. Both save rework.
- An OpenAI key. Without it the Quiz asks no questions, and with no cases the coding agent refuses to build. The site still works — only vector search and the knowledge graph stay empty. Entered once; the cost goes straight to your model provider. OpenAI key
- Your own domain. On a numeric address there is no certificate and no installable app — a browser grants those only over a secure connection. Moving later changes every page address, so it is cheaper before they are indexed. Domain
Quiz — seven questions instead of a blank page
A project's most expensive mistake is made before the first line of code: the wrong thing gets built. Not through poor building, but because «where do I start» is hard to answer alone. Quiz turns it into a conversation: you answer, the model asks further, and out of it grows the list of scenarios the project is then built from.
The seed
Seven short questions: what the product is, who it is for, what a person should walk away with. Answer in your own words — dictation works. Everything after this grows from here, so a couple of sentences yields a markedly better result than a couple of words.
The conversation
Then one question at a time, in your language. There is an auto-quiz: the model asks five new questions and answers them itself, deepening the description — but anything it invented on your behalf is marked «Assumption», and you correct it. A guess passed off as fact would surface later, inside the finished scenarios.
The scenarios
The conversation is synthesised into numbered cases: who arrives, what they do, what must be true at the end. You read and confirm each one separately. An unread case is still the model's guess.
And this is a product rule, not advice: while a single case is unconfirmed the panel keeps its alarm lit and the coding agent refuses to build. Building on an unread guess costs more than not building at all.
What this project is, technically
Three things worth knowing before you build on it: what the skeleton is, where the code is actually written, and what happens when the project outgrows its first hundred pages.
This is not a finished site but the Fractera architecture: one skeleton carries a landing page, a large SaaS and multi-level automation alike. Growth needs no rewrite — the data, authorization and panel layers are already separate, and each is built for load you do not have yet.
Code is not written here. A developer clones the repository to their own machine and works with Claude Code, which reads the instructions and skills that live inside the project: they state the rules, and machine checks refuse to let them be broken. The server only receives the result and rebuilds.
The skeleton is built for a project that will outgrow a million lines: every entity owns its folder, the shared layer does not grow with their number, and routes and permissions are declared where they are enforced. Stability here is not a promise but a consequence — a new page adds nothing to a central spine.
A fully independent space
On a typical project these are three outside services — their pricing, their terms, and their permission for your project to keep running. Here all three live on your own server.
you do not pay
Vercelhostingyou do not pay
Neondatabaseyou do not pay
Clerkauthorization
You pay nobody
You depend on nobody. The project is yours, end to end.