No surprises — see cost before generating.
TrainedApps uses a credit-based system with full transparency. You see the estimated cost before every generation, and you only pay for what you use.
How credits work
A simple four-step process from prompt to credit deduction.
Describe your change
Write a prompt describing the feature or modification you want.
See the estimate
Before generation begins, TrainedApps shows you the estimated credit cost based on the scope of the change.
Confirm or adjust
If the cost is too high, simplify your request. If it looks right, confirm and generation begins.
Credits are deducted
Credits are deducted only after the generation completes successfully. Failed generations do not cost credits.
What increases cost
Credit usage scales with the complexity of what you are generating. Here are the factors.
Number of pages and components
More pages and UI components means more code to generate, which uses more credits.
Backend complexity
Apps with complex business logic, multiple API routes, and data relationships cost more than simple CRUD apps.
Authentication and roles
Adding auth with role-based access increases the generation scope and credit usage.
Third-party integrations
Connecting to external APIs (payments, email, storage) adds integration code and increases cost.
Database complexity
More tables, relationships, and migration files increase the generation workload.
Follow-up prompt scope
Small tweaks cost less than major feature additions. The estimator accounts for scope automatically.
Estimator examples
How many credits does a typical app cost? Here are two reference points.
Small MVP
15-25Landing page, sign-up form, basic dashboard, one data model
- 3-5 pages
- Basic auth
- 1-2 data models
- Simple admin panel
SaaS Application
60-100Multi-page app with auth, roles, payments, admin, and 5+ data models
- 10-15 pages
- Full auth with roles
- 5-8 data models
- Payment integration
- Admin dashboard
- Email notifications
These are approximate ranges. The actual cost depends on prompt specificity and app complexity. You always see the estimate before confirming.
Optimization tips
How to get the most value from your credits.
- Start with the core feature set. Add extras in follow-up prompts.
- Be specific in your prompts to avoid unnecessary re-generations.
- Use the code editor for small tweaks instead of new prompts.
- Combine related changes into a single prompt to reduce overhead.
- Review the estimate and simplify if the cost is higher than expected.
Plan guidance
Choosing the right plan based on your expected usage.
Free
10 credits
Trying the platform for the first time. Build a small prototype to see how it works.
Starter
100 credits/month
Solo builders working on one or two projects. Enough for an MVP and several rounds of iteration.
Pro
500 credits/month
Teams and agencies building multiple apps. Enough for several full-stack projects per month.
Enterprise
Custom
Large organizations with high-volume needs. Custom credit allocation, SLA, and dedicated support.
Transparent pricing, no surprises
Start with free credits, see estimates before every generation, and upgrade only when you need to.