Skip to main content
AIWA uses credits when it performs AI-powered work on your projects. Different actions require different amounts of work, so they have different credit costs. Use this page as a quick reference when planning your AIWA usage. Credits are used for AI-powered work. Publishing and hosting your applications do not consume credits.

​
Credit Cost Table

A full application build is typically around 50 credits. Because applications vary in complexity, treat this as an estimate rather than a guaranteed fixed cost.

​
Full App Build: ~50 Credits

A full app build is the initial creation of a new application from your idea. For example:
Build a CRM for a real estate agency. Agents should be able to manage leads, properties, viewings and follow-ups. Include authentication, a dashboard and customer profiles.
AIWA may perform several operations to turn that request into a working application:
A complete build typically costs approximately 50 credits. Why does it say “~50”? Because not every application requires exactly the same amount of work. A simple application and a more substantial full-stack product may require different generation work. For this reason, ~50 credits should be treated as a typical estimate.

​
Edit / Iteration: 10 Credits

Once your first version exists, you can continue working with AIWA to improve it. A standard edit or iteration costs 10 credits. For example:
  • Add a testimonials section to the homepage.
  • Create a customer profile page.
  • Improve the dashboard layout.
  • Add another step to the onboarding flow.
  • Make the application more responsive on mobile.
This is how most ongoing product development happens inside AIWA:

​
Auto-Debug Fix: 10 Credits

When AIWA performs a dedicated debugging operation to diagnose and fix a problem, the action costs 10 credits. For example:
My signup form submits but the user isn’t being created. Find the problem and fix it.
AIWA can investigate the issue and attempt to correct it.
AIWA also performs checks and self-healing during the normal generation process. Corrections that are part of completing the generation you’ve already requested aren’t necessarily separate debugging actions.

​
Plan Turn: 6 Credits

A Plan turn costs 6 credits. Plan Mode is useful when you want AIWA to reason through a substantial change before modifying your application. For example:
Plan how we should add a marketplace to this application with sellers, buyers, listings, payments and commissions. Don’t build anything yet.
You can review the proposed direction before moving into implementation.

​
Generate an Image: 4 Credits

Generating a new image costs 4 credits. This can include AI-generated visual assets used within your application. For example:
This applies to generating a new image, not simply displaying or using an existing image.

​
Transcription: 2 Credits

AI-powered transcription costs 2 credits. Transcription allows AIWA to convert supported spoken input into text that can be used as part of your building workflow.

​
Idea Shuffle: 2 Credits

Using AIWA’s idea shuffle functionality costs 2 credits. Idea Shuffle is a lightweight AI action designed to help you discover or explore something new to build. Because it requires substantially less work than building an application, it uses fewer credits.

​
Publishing: 0 Credits

Publishing does not consume credits.
You aren’t charged AI credits simply for putting your project online.
Publishing availability and features such as custom domains can still depend on your AIWA plan. “0 credits” means the publishing action itself isn’t metered against your credit balance.

​
Hosting: 0 Credits

AIWA also doesn’t continuously deduct credits simply because a published application remains online. For example:
This is an important distinction between AI usage and application hosting.

​
Example: Building Your First App

Suppose you start with:
Build a booking application for a fitness studio.
Your approximate usage might begin with:
You then decide:
Add membership plans to the homepage.
Then:
Plan how recurring subscriptions should work before implementing them.
Then you publish:
This gives you a much better way to estimate your usage than simply counting how many prompts you’ve sent.

​
Example: Improving an Existing Product

Imagine you already have a live SaaS application. You ask AIWA to:
You can therefore use your credit balance across one product or several different projects.

​
Your Plan Doesn’t Limit You to a Fixed Number of Apps

When AIWA says a plan provides enough credits for approximately a certain number of full applications, that’s an estimate based on typical full-build usage. For example:
It does not mean AIWA gives you a fixed number of “app slots.” You could instead spend the same credits making many iterations to one important application.

​
Estimated vs Fixed Costs

Pay attention to the distinction on this page. Approximate
  • Full app build: ~50 credits
The ~ means the amount can vary. Standard action costs Actions such as:
  • Edit: 10 credits
  • Debug: 10 credits
  • Plan: 6 credits
  • Image: 4 credits
  • Transcription: 2 credits
have their defined action costs under the current credit model.

​
Check Before You Build

AIWA shows your available credit balance inside your account Aiwa Credits Balance Preview If you’re planning a substantial build, checking your available balance can help you understand how much building capacity you currently have.

​
Quick Reference

If you only remember one part of this page, make it this:
These costs reflect AIWA’s current credit system and may evolve as AIWA’s capabilities and building process improve.

​
Next: Monthly Credits vs Top-Up Credits

Next we’ll explain the difference between the credits included with your plan each month and additional credits you can purchase separately.

Monthly Credits vs Top-Up Credits

Understand how monthly and top-up credits behave differently.