Plans
Plans are about engine depth, output breadth, and continuation strength
Read the plans as different levels of structural power. The question is not whether you are a beginner or advanced. The question is how much output richness, continuation depth, and flexibility you want the engine to deliver before you start refining the repo yourself.
How to read plans
Think in terms of depth, not skill labels
A stronger plan should feel more valuable because it expands what arrives in the repo and how far the structured continuation path goes. It should not feel like a personality label or a watered-down ‘starter for beginners’ story.
Output breadth
Focused baseline with the main product shape kept easier to inspect.
Broader grouping across screens, flows, and product areas before you start local continuation.
The broadest guarded output surface when the product needs more structural reach from the start.
Continuation power
Clean base to keep moving yourself.
Stronger starting point so continuation begins with more structure already present.
Most capable continuation path for rebuild, extension, and refinement inside guardrails.
Why you pay more
You want a real repo baseline without maximum depth on day one.
You want the repo to land with more substance and better flow grouping.
You want the strongest guarded mix of depth, flexibility, and long-term continuation leverage.
Standard Engine
Focused repo depth for when you want a serious baseline without paying for maximum expansion on day one.
When you want a serious baseline, a cleaner continuation surface, and a sensible place to start before paying for broader output shape.
What gets stronger at this level
This plan is about clean starting depth. It keeps the repo understandable while still giving you a real build-ready baseline to continue.
- Core product structure without unnecessary spread into every possible flow.
- A cleaner starting repo that is easier to inspect, understand, and continue.
- Enough structure to become real work, not only a throwaway concept.
How to think about this plan
Choose Standard Engine when you want this specific level of repo depth and continuation leverage. The difference is not just more copy on a pricing card. The difference is how much useful structure shows up before you start continuing the codebase yourself.
Deep Engine
Broader output shape, stronger feature grouping, and more continuation depth before you even start local refinement.
When you want the repo to land closer to a fuller product structure so continuation starts from a stronger place.
What gets stronger at this level
This is where the repo usually arrives with more substance. The value is not speed alone. The value is that more of the structure is already there for you to continue from.
- Richer grouping across flows, screens, and product areas.
- Stronger continuation shape when the product needs more than a narrow baseline.
- More useful starting depth for real MVP and build-ready work.
How to think about this plan
Choose Deep Engine when you want this specific level of repo depth and continuation leverage. The difference is not just more copy on a pricing card. The difference is how much useful structure shows up before you start continuing the codebase yourself.
Deep Engine Plus
The strongest guarded engine path for users who want the most output depth, flexibility, and continuation power without slipping into unbounded generation.
When you want the strongest version of the Virex engine path because the product needs more depth, more control, and more room to keep growing.
What gets stronger at this level
This plan is about trust and leverage at the same time. You pay for more structural power, broader product surface, and stronger continuation flexibility inside guardrails.
- The broadest and deepest generated structure where the product benefits from it.
- A stronger starting point for ambitious products with heavier continuation needs.
- The most capable guarded path for rebuild, expansion, and refinement work.
How to think about this plan
Choose Deep Engine Plus when you want this specific level of repo depth and continuation leverage. The difference is not just more copy on a pricing card. The difference is how much useful structure shows up before you start continuing the codebase yourself.
Why the stronger plans exist
The point is not to make Standard Engine look weak. The point is to make it obvious why deeper plans cost more: they can land with broader product surface, stronger grouping, richer continuation shape, and more useful structural leverage for real product work.
How credits work
One shared Deep Engine allowance for everything you build or change
Each plan comes with a monthly Deep Engine allowance. Builds, structural edits, repairs, and deeper augmentation all draw from the same pool — never separate buckets. Cosmetic edits (colors, sizing, logo position, dark mode) run on the Standard Engine and never count against the allowance.
Full breakdown lives on the build page
The build guide walks through what counts, what is always free, and what happens around 85% / 95% / 100% of the monthly allowance.
Premium and Pro never run out of builds
If you exhaust the Deep Engine credit pool partway through the month, the engine quietly drops to the Standard Engine and keeps going. Builds stay unlimited, edits stay unlimited, you just get roughly 10× less depth per pass — no LLM-driven feature codegen, no deep edit reasoning. On the first of next month the credit pool refills and full depth returns automatically.
Starter has a build cap (15 / month)
Starter is permanently on the Standard Engine — no Deep Engine credits at all. The 15 builds/month limit is soft upsell pressure: the moment you want deeper output or more headroom, Premium gets you both. Cosmetic edits stay unlimited and free on every plan.
Ready to pick one?
Pick the plan and start building
Once the plan that fits your work is clear, the next step is the pricing page. Checkout is handled by Stripe and takes a minute.