How it works
From a conversation to working software.
A clear, governed process: Amanda does the building; you stay in control of what ships.
The process
- 01
Idea
Describe the problem, the people involved and what good looks like.
- 02
Plan
Amanda proposes a plan, lists the files and data involved, and shows a credit estimate.
- 03
Build
Amanda writes multi-file changes on a branch in an isolated build sandbox.
- 04
Preview
Open a working preview of the app before anything is merged.
- 05
Test
Type checks, tests and visual checks run; failures are fixed or reported.
- 06
Review
You see what changed in plain English and decide: keep, change or restore.
- 07
Deploy
Approved changes are prepared for staging and production through release gates.
- 08
Improve
Keep iterating. Every step is versioned, so it's safe to try things.
Who does what
Amanda does
- Plans the work and estimates credits
- Writes and changes code across files
- Proposes database migrations
- Runs builds, tests and visual checks
- Creates version checkpoints
- Explains every change
You approve
- Plans above your spending limits
- Merges into your main branch
- Production database migrations
- Connector write permissions
- Production deployment
- Restores and other destructive actions
Credits, versions, approvals and rollback
Credit estimates
You see an estimate before chargeable work. Unused reserved credits are released.
Versioning
Each change is a checkpoint you can compare and restore.
Approvals
Sensitive actions wait for a person. Nothing risky runs silently.
Rollback
Restore an earlier version when a change isn't right.