Documentation

Not necessarily. Examples and prompts are starting points. ForGrit may generate a new version with its own design DNA. Once you approve a plan, preview, and estimate, those approved decisions guide the build.

No. Examples show one generated result from a prompt. Starting from an example creates a new build based on the same idea, with its own design, structure, and estimate.

No. Examples are prompt starters and generated previews. Starting from an example creates a new app with its own design DNA. Marketplace listings are real software assets that can be bought, sold, and transferred through a reviewed ownership workflow.

Yes. Built apps are stored in a private GitLab repo linked to your project, with version history and review access.

If ForGrit fails a paid generation step, credits for that failed step return to your balance. If a step needs your action, such as adding connection keys or fixing third-party setup, ForGrit shows what needs attention before launch.

Yes. Generated app code belongs to you, subject to ForGrit terms and third-party licenses. You can inspect, download, and continue development from the private GitLab repo.

No. Credits do not expire as long as your account remains active.

Yes. Your projects and generated repositories are private by default. We do not publish them, list them in the marketplace, or use private project code for model training unless you explicitly choose to share, list, sell, or transfer an app.