A: Hello big number hehe,

CPU MINTUES ARE THE FUEL FOR YOUR APP’S ENGINE

WHAT A CPU MINUTE REALLY IS
Picture one CPU minute as sixty seconds of pure processing time on a single core. Every query to the database, every API handshake, every rendering of a web page or call to an AI model keeps the engine spinning for a slice of that minute. NoCode-X bundles one thousand of these minutes into each core every month, along with storage, bandwidth, and a developer seat. Full breakdown lives at https://docs.nocode-x.com/licenses-&-billing/

TYPICAL CONSUMPTION SNAPSHOTS
A static page request with no backend logic sips less than 0.01 CPU minutes, so a brochure-style site can serve roughly a hundred thousand views on a single core before dipping into the reserve.
A simple REST API endpoint that validates input, hits the database, and returns JSON burns around 0.02 to 0.05 CPU minutes per call, translating to twenty to fifty thousand hits per core each month depending on payload size.
An AI-assisted form fill that makes a quick OpenAI completion call and post-processes the result lands close to 0.1 CPU minutes—ten thousand such interactions per core before you need more fuel.
A heavier workflow like ingesting a five-minute video, transcribing it with Whisper, summarizing with Perplexity, and writing the result back into storage can climb to 3–5 CPU minutes. On that curve a single core comfortably handles two hundred of these rich jobs monthly, or more if you parallelize across additional cores.

CHOOSING YOUR TIER
Match the math to your roadmap. Prototyping a lean SaaS with a few hundred daily users? One core in Tier 1 keeps you cruising. Scaling to thousands of API calls plus regular AI enrichments? Tier 2’s extra cores double or triple the runway. Running media-heavy automations or high-volume public traffic? Tier 3 and beyond stack cores linearly, so every upgrade is a simple multiplier of the numbers above. Because cores scale in lockstep with storage and bandwidth, you grow capacity without juggling separate limits.

SEEING IT IN REAL TIME
Open your workspace, tap Usage, and watch live graphs of CPU, storage, bandwidth, and AI credit drawdown. If the needle creeps toward red sooner than expected, spin up another core with a click and keep the experience silky.

THUS
Think of cores as perpetual horsepower and CPU minutes as the gasoline you burn while creating value—light for static pages, moderate for business logic, heavier for AI and media crunching. Start with the tier that feels comfortable, monitor the gauge, and add cylinders when ambition outpaces capacity. Your next feature is waiting to be unleashed; fuel it wisely and watch your app roar.

greetings
Wim