Skip to main content

​
Hosting limits

Publishing (hosting / LIVE URL) is available on every plan, gated by monthly Cloud credits (Free 10/mo; Pro, Business and Enterprise a fifth of the monthly credits, 20/mo at 100; reset on the 1st UTC). Free’s app pauses when Cloud credits hit zero (no Free top-ups). Pro, Business and Enterprise fall through to their monthly credits and top-ups once Cloud credits run out. Free can also use a database and app storage in Preview and on LIVE apps (storage capped at 1 GB on Free). The database pauses when idle, so tables stay across short sandbox sleep; abandoned Free Preview infra may be cleaned up after ~14 days if there is no LIVE deployment. Published apps and attached databases spend from Cloud credits first, not the Build credits used for chat. Usage UI labels this spend Database, Hosting and File storage (filterable together as Cloud credits).

​
Included

This spend covers published compute, database usage, bandwidth (what visitors download from your app) and stored files. A background meter samples LIVE apps about every 5 minutes; database compute is billed per hour, shortly after each hour ends, and bandwidth about every 30 minutes. Pro, Business and Enterprise pay half the Free rate for hosting, databases, bandwidth and file storage, and nothing for the preview sandbox. Chat and AI features cost the same on every plan.

​
App size

Mythex picks the machine for each published service when it deploys, based on what the app needs — you don’t set anything. A plain web app or API gets the default; an app that needs more (heavy processing, large in-memory data) gets more memory. Ask in chat if you want a specific size.
  • Default: 1 CPU, 512 MB, 1 machine.
  • Extra machines start only when traffic is heavy and go back to sleep when it drops.
  • Cost follows size: a bigger machine, or more of them running, spends more credits per hour. A sleeping app spends nothing on compute.
  • If you ask for more than your plan allows, the publish uses the most it allows and the deploy log says so.

​
If your app runs out of memory

If a published app uses all its memory, it crashes. We email you when that happens — whether it restarted on its own, or kept crashing and stopped. Ask the agent to give it more memory and publish again; if it’s already at your plan’s maximum, upgrade (Free) or ask the agent to make the app use less.

​
Database size

A published app’s database grows and shrinks with its load: it starts at the smallest size (0.25 compute units), grows up to 2 while busy, and sleeps after 5 idle minutes. You’re charged for what it actually used — its size multiplied by the time it was awake — so a quiet app’s database costs very little. Stored data is charged by size.

​
Empty Cloud credits

When that month’s Cloud credits hit zero:
  • Chat / build is unaffected — Build credits are separate and never pay for Cloud
  • Free LIVE apps pause — their servers stop; your database, files, and the published URL are kept, until Cloud credits reset on the 1st or you upgrade
  • Pro, Business and Enterprise LIVE apps keep running, now drawing on the monthly credits and top-ups
  • Preview + terminal stay available
Before that happens you get an “Action needed” email when your Cloud credits are almost empty and a published app with a server is still running — at most once a day. It lists each app that will go offline and notes that its database is kept. Free is shown how to upgrade; paid plans are shown how to turn on auto-reload (or, if auto-reload is already on, to check the card). Static sites don’t use credits while they sit there, so they don’t trigger it. If a Free published app pauses because Cloud credits ran out, we email you; when they reset and it goes live again, we email you that it’s back. Free users who used yesterday’s Build credits also get a morning email when today’s 10 are ready.

​
Monthly limit per app

Each project can have its own monthly limit on what its published app spends — database, hosting and file storage — set in Settings → Usage. We email the owner at 80% of the limit and when it’s reached. At the limit the published app pauses the same way as empty Cloud credits (servers stop; database, files and URL kept), and comes back on the 1st of the next month, or as soon as you raise or remove the limit. Building with the agent and the workspace don’t count toward it. See Usage.

​
Practical advice

  • Prefer scale-to-zero friendly apps — published apps and their databases sleep when idle and wake on the next visit
  • Cache static assets
  • Top up or upgrade before a marketing launch if you expect traffic