# Sapilon

> Sapilon is an AI-first software system that governs AI to modernize legacy systems and graduate AI prototypes into production-ready, AWS-native software.

Full content for ingestion: https://sapilon.com/llms-full.txt

## Core
- [What Sapilon is](https://sapilon.com/product): software factory & modernization engine, not a vibe-coding toy
- [How it works](https://sapilon.com/how-it-works): four gated stages — Design, Build, Rehearsal, Live
- [Modernization](https://sapilon.com/product/modernization): 50–95% of a legacy app rebuilt in the bootstrap phase, ~10× faster than a traditional rewrite
- [Pricing](https://sapilon.com/pricing): Prepaid wallet, pay-as-you-go. No subscription, no seats.
- [Governance](https://sapilon.com/product/governance): //!AUTO · //!SAFE · //!DEV ownership zones, auditable and reversible
- [Experts ecosystem](https://sapilon.com/product/experts): verified human specialists review AI-escalated decisions; all-inclusive published rates
- [Feature Packs](https://sapilon.com/packs): packaged, versioned feature slices extracted from real Sapilon apps
- [Trust & ownership](https://sapilon.com/trust): Plain Git, open libraries, native AWS. No lock-in.
- [FAQ](https://sapilon.com/faq): the most-asked questions, answered plainly
- [Glossary](https://sapilon.com/glossary): Sapilon's vocabulary defined — zones, stages, points, wallet

## Docs
Task and reference documentation. Raw Markdown for any page is at the same URL with a .md suffix.
### Getting started
- [What Sapilon is](https://sapilon.com/docs/getting-started/what-is-sapilon): Sapilon turns a legacy system or an AI-built prototype into production-ready, AWS-native software you own outright, using a governed AI agent whose permissions are written into the code itself.
- [Your first project](https://sapilon.com/docs/getting-started/your-first-project): Create a project from the projects list, give it your existing code or a written description as input, and open it — each project is an isolated workspace with its own repository, wallet draw, and stage.
- [The four stages](https://sapilon.com/docs/getting-started/the-four-stages): Every project moves through Design (shape, mocked data), Build (real backend on the Build Server), Rehearsal (dress rehearsal on the Rehearsal Server), and Live (production) — and each transition is a gate that checks readiness rather than a deploy button.
- [Your first Ask](https://sapilon.com/docs/getting-started/your-first-ask): Ask for one outcome at a time, say what it is for and what must not change, and read the diff before you accept it — a good brief is the difference between one turn and five.

### Your project
- [Existing System](https://sapilon.com/docs/project/existing-system): Answer one question about where your current system lives, and the product gives you a short, ranked list of what to bring — with a plain explanation of what the agent has to guess if you skip each one. Telling us something does not exist is a real answer.
- [Tasks](https://sapilon.com/docs/project/tasks): A task is one piece of work queued for the project — written by you or split out by the agent from a larger request — and it is the record of what is planned rather than the mechanism that does the work.
- [Feature briefs](https://sapilon.com/docs/project/feature-briefs): A feature brief is the agent’s written proposal for a change large enough that building it straight away would be a guess: what it understood, what it plans to do, and what it needs you to decide.
- [Project history](https://sapilon.com/docs/project/project-history): Every project keeps a record of the agent sessions, releases and review runs behind it, so what changed, when, and at what cost is answerable after the fact rather than reconstructed.

### Ownership zones
- [Ownership zones explained](https://sapilon.com/docs/ownership-zones/zones-explained): Every part of your codebase carries one of three markers — //!AUTO (the agent owns it), //!SAFE (the agent proposes, you approve), //!DEV (humans only) — written in the source itself, so AI permissions are code you can read and change.
- [Editing generated code](https://sapilon.com/docs/ownership-zones/editing-generated-code): Edit anything you like — your changes are checkpointed as their own version before the next agent turn — but code you intend to keep hand-writing belongs in //!DEV or //!SAFE, or a later turn may rewrite it.
- [When the agent stops](https://sapilon.com/docs/ownership-zones/when-the-agent-stops): A stopped turn is usually governance working as designed: the agent needs an answer, needs your approval on a //!SAFE diff, hit a failing check, or reached an action that requires a verified expert's verdict.

### Stages & gates
- [Design](https://sapilon.com/docs/stages/design): Design settles what the app is: screens, flows, data model and architecture, running against mocked data with nothing deployed, so changing your mind is nearly free.
- [Build](https://sapilon.com/docs/stages/build): Build replaces mocked data with a real backend, database and integrations on the Build Server, so the app works end-to-end before anyone pays for production infrastructure.
- [Rehearsal](https://sapilon.com/docs/stages/rehearsal): Rehearsal runs the finished app on the Rehearsal Server, where you drill the data migration, walk the real journeys, and check security and running cost while it is still safe to be wrong.
- [Live](https://sapilon.com/docs/stages/live): Live is production: the new system takes over, the old one is retired, and the same governed workflow keeps shipping changes with versioning, monitoring and backups behind them.
- [Promoting between stages](https://sapilon.com/docs/stages/promoting-between-stages): Promotion runs a readiness gate — tests, health, architecture and stage-specific checks — that can pass, pass with warnings, or block; it is a check on the project, not a deploy button.
- [The servers](https://sapilon.com/docs/stages/servers): A project runs on up to four servers — Design, Build, Rehearsal and Live — each created when the project reaches the stage it serves. The Design Server is free and serves your mocked preview; the other three are real infrastructure, monitored and backed up, and drawing from the wallet while they exist.

### Billing
- [Wallet and top-ups](https://sapilon.com/docs/billing/wallet-and-top-ups): Sapilon runs on one prepaid wallet that AI points, AWS hosting and expert time all draw from; there is no subscription and no seats, and the balance cannot go negative.
- [Points](https://sapilon.com/docs/billing/points): A point is Sapilon's fixed-price unit of AI usage with one published rate, so an interaction costs a predictable whole number instead of a token bill you can only understand afterwards.
- [What a turn costs](https://sapilon.com/docs/billing/what-a-turn-costs): Every agent turn reports what it cost in points and why, so cost is something you read after each turn rather than discover at the end of the month.
- [Expert work pricing](https://sapilon.com/docs/billing/expert-work-pricing): Expert work is priced by job size — Small (under 30 minutes) and Medium (about an hour) at fixed prices, Large billed hourly against an estimate and a cap you approve before anything starts.

## Compare
- [Sapilon vs Lovable](https://sapilon.com/compare/sapilon-vs-lovable): From prototype to production
- [Sapilon vs Replit](https://sapilon.com/compare/sapilon-vs-replit): When you outgrow the sandbox
- [Sapilon vs Bolt](https://sapilon.com/compare/sapilon-vs-bolt): Fast draft vs. software that lasts
- [Sapilon vs Base44](https://sapilon.com/compare/sapilon-vs-base44): MVP output vs. production-grade
- [Sapilon vs Cursor](https://sapilon.com/compare/sapilon-vs-cursor): The editor and the factory
- [Sapilon vs v0](https://sapilon.com/compare/sapilon-vs-v0): UI generation vs. full lifecycle

## Blog
- [Design, Build, Rehearsal, Live: why the fastest AI software ships in stages](https://sapilon.com/blog/design-build-rehearsal-live)
- [How much does a custom internal tool cost?](https://sapilon.com/blog/how-much-does-a-custom-internal-tool-cost)
- [AI-safe code: ownership zones explained](https://sapilon.com/blog/ai-safe-ownership-zones-explained)
- [AI-first doesn't mean AI-only: why Sapilon has human experts](https://sapilon.com/blog/ai-first-doesnt-mean-ai-only)
- [Your old system already wrote the spec: how Sapilon thinks about artifacts](https://sapilon.com/blog/your-old-system-already-wrote-the-spec)
- [Is this the end of low-code and no-code?](https://sapilon.com/blog/is-this-the-end-of-low-code-no-code)
- [Why prompts are not enough for creating a production app](https://sapilon.com/blog/why-prompts-are-not-enough)
- [AI agents now write software. Who's flying the plane?](https://sapilon.com/blog/ai-agents-who-is-flying-the-plane)

## About
- [Company](https://sapilon.com/about)
- [Contact](https://sapilon.com/contact)

## Legal
- [Terms of Service](https://sapilon.com/terms): customers own the generated software; plain Git, no lock-in
- [Privacy Policy](https://sapilon.com/privacy): no selling of data, no training AI models on customer content
- [Data Processing Agreement](https://sapilon.com/dpa): GDPR processor terms, EU data residency, sub-processors (AWS, Anthropic, Stripe, Google)
- [Marketplace Terms](https://sapilon.com/marketplace-terms): Sapilon as intermediary; experts are independent and responsible for their professional work

## Status
Sapilon is in private early access, preparing for general availability.