booting
Point Cicatrixa at a GitHub repo — or several. The AI works out how to build it, wires a subdomain, verifies the deploy actually works, and stays on call: every push redeploys, every crash gets diagnosed and repaired, before you ever hear about it.
Deploy your first repo → Log in▼ HOW IT REFUSES TO GUESS
The objection, answered
Sure. Nobody does, because the work isn't the build — it's everything around it. Cicatrixa is the ops engineer that does the part you'd rather not: the Dockerfile nobody wrote, the port that only your app knows, the crash that happens while you're asleep.
Nobody's watching at 3am. A crashed container just stays crashed until a human notices — usually from a user's complaint, not a dashboard.
Docker is homework. A correct Dockerfile per stack, the right port, the right start command — engineers rewrite this by hand for every new repo. Cicatrixa reads the code and writes it.
Two repos, two headaches. A frontend and its API need to find each other — normally your job to wire, your CORS bugs to chase. We bridge them on the same domain automatically.
A fix means a whole redeploy cycle. SSH in, patch, rebuild, restart, hope. We collapse that to one chat message that ends in a real commit on your repo.
No verified deploy, no traffic. Ever.
— THE ONE RULE THE ROUTER CANNOT BREAK
The healing loop
The same bar you'd hold a careful engineer to — proof before promotion, every single deploy.
GitHub App in one click, or a token in thirty seconds. Pick one repo or several — frontend, backend, workers.
The AI reads the repository like a chart: framework, entry point, port. No Dockerfile? It writes one.
Containers build on a sealed internal network — no host ports, ever — and a subdomain wires itself.
Nothing takes traffic unproven. The deploy is smoke-tested and the AI signs off on the result in writing. Build or boot fails? It diagnoses the log and retries — up to three times — before you'd ever notice.
Every push redeploys in seconds. Crashed containers restart themselves; chronic failures rebuild from source. The previous version keeps serving until the new one proves healthy.
Talk to it. "Check the API for errors" — it investigates the real logs and code, proposes an exact patch, and — only once you approve — commits, pushes to your GitHub, and redeploys.
The product, live
This is the control plane your team sees — an actual run, stage by stage, from a bare repo to a verified, self-healing service.
Get running
Sign up, connect GitHub, and pick a repo — or a whole project's worth. There's nothing to install; the build happens on our side, not yours.
Email and a password. No credit card, no waitlist — you're in the dashboard in under a minute.
The GitHub App's own repo picker grants access to exactly what you choose. A token works too.
Pick a repo (or several for one project) and watch the log — live at your-project.cicatrixa.com in minutes.
Where we sit
| roll your own VPS | typical PaaS | cicatrixa | |
|---|---|---|---|
| Detects the right Dockerfile | ✗ you write it | ± buildpacks only | ✓ AI reads the code |
| Wires multiple repos together | ✗ your CORS bugs | ✗ | ✓ same-origin bridge |
| Retries a failed build | ✗ | ✗ fails, you fix | ✓ AI diagnoses & retries |
| Watches for crashes after deploy | ✗ | ± restarts only | ✓ restart → rebuild |
| Redeploys automatically on push | ✗ | ✓ | ✓ |
| Chat a fix straight into a real commit | ✗ | ✗ | ✓ reviewed, then pushed |
What a chat turns into
This is an actual exchange: ask for an error check, get back a proposed patch with a diff — approve it, and it's built, verified, pushed to your GitHub, and live.
Pricing
One plan, everything included. Cheaper than the cheapest dyno you've ever rented — except this one notices when your app dies, and fixes it.
Invite-only while we scale the fleet — request access and we'll wave you in.
Questions, answered straight
We read your repo through the exact scope you grant (GitHub App repo picker, or a token you control). Builds happen on the server hosting your app — nothing is used to train models, and nothing is sent anywhere else.
The AI reads your stack — Node, Python, Go, static — and writes one. If the AI is unavailable, deterministic heuristics per-language cover the same ground.
The AI reads the failure, diagnoses the cause, and retries with a corrected plan — up to three attempts. If it truly can't, the previous working version keeps serving; nothing goes dark.
No. Every fix shows up as a diff you review. Only when you click Apply does it clone, patch, verify the build, commit as Cicatrixa Agent, and push.
Per-account quotas — service count, RAM, storage — enforced before every deploy, and every container is hard-capped regardless. One tenant can't starve another.
None. Zero. Every app runs on a sealed internal network and routes purely by subdomain — port conflicts aren't a category of bug you can have here.
Start now
Sign up, connect GitHub, and deploy something real in the next five minutes. $2.99 a month once you love it — just an invite to start.
Deploy your first repo →Contact
Questions, pilots, or something broke that shouldn't have — one address reaches the founders directly.