Documentation
Learn how ForGrit turns app ideas into reviewed, previewed, built, and launched software.
How a build works
ForGrit runs your idea through five clear steps — you review and approve each one before moving on:
ForGrit uses a controlled build pipeline. Once you review and approve the plan, design, and estimate, those approved decisions guide the build so the output is traceable and repeatable.
Technical noteApproved decisions can be locked so builds are repeatable from reviewed inputs — different from raw chat output, where results may change unpredictably.
Review and approve
Before code is generated, you review and approve what ForGrit will build. You see the plan in plain language, the representative preview, and the estimate before credits are used.
Technical noteApproval creates a design/build record (a “design lock”) that guides generation — the approved architecture, layouts, component hierarchy, and technology choices.
Cost approval
You always see the estimate before a paid step. Credits are used only after you approve. If ForGrit fails a paid generation step, credits for that failed step return to your balance.
Technical noteThe approved estimate becomes the budget lock for that generation run.