Pay by the hour.
Keep the monthly ceiling.

You add credit, and each running application draws from it every hour at its plan's rate. The smallest application tier costs $0.0119 an hour. Nothing is charged on a monthly cycle, there is no invoice date, and no card is stored.

Because that is the figure worth comparing, and because it is a ceiling. Hourly charges stop once something has paid its monthly price, which takes 28 days of continuous running — so the remaining days of a longer month are free, and no month costs more than the number on this page. Run something for part of a month and you pay for the hours it ran, nothing else.

Your apps are stopped, and your organization is put into read-only mode until you top up. New inference requests are declined too. Nothing is deleted — your configuration, domains, environment variables and deploy history are all still there. Adding credit lifts the suspension, and you choose which applications to start again.

No. Every application runs in a real container on a real server, and we would rather charge eight dollars for that than ship a free tier we quietly throttle. Need something up for an afternoon? Four hours of the smallest plan costs about five cents.

No. Invite the whole team; it costs nothing. You pay for compute, not for who can log in.

No. Transfer is unmetered on every plan — nothing to exhaust, nothing to overage, so the number you see is the number you pay. If that ever changes we will say so beforehand, not afterwards on an invoice.

Yes, in either direction, from its settings. The new CPU and memory limits apply the next time the application deploys, and billing moves to the new hourly rate from that point.

PayPal, in one-off top-ups. Nothing to cancel and no recurring authorisation — when you stop topping up, you stop paying. That is the entire cancellation flow.

One deployable thing: a web app, an API, a worker. A frontend and a backend is two apps on two plans — better you hear that here than at checkout.

It depends on the model, and the catalogue says which. Most bill by the input and output tokens they use, at a rate published before you call. Image and video models are not sold by the token at all — the providers price those per image, per second or per megapixel — and a handful of embedding models charge a different token rate for text, pictures and audio. Those are charged what the request cost to serve plus our markup, and the amount appears on your usage page like every other call. Everything draws from the same prepaid balance as your applications and databases, and the catalogue changes independently of this static page, so it is the place to check before you call.

Yes. A database is a container on a server exactly like an application, so it runs on its own plan and bills by the hour the same way. The smallest of each — a 1 GB app and a 1 GB database — is $8 and $15.23 a month, drawn from the same balance.

Nothing stops it. The storage figure on a database tier is the disk it is sold with, not a quota the server enforces — we would rather tell you that than let you find out by assuming there is a safety net. We watch disk per server and will ask you to move up a tier before it becomes a problem for you or anyone else on that machine.

We do. Backups are on or off per database and stored by Maxlayer in our own storage, so there is nothing for you to configure. While a database's backups are on, it costs an extra 30% of its plan. Two limits worth knowing: Redis cannot be backed up at all, and restoring is manual — a backup is a dump file, and restoring it means running it yourself.

Because running storage is part of running the service. A bucket per customer was a configuration you had to make and a credential you had to guard, and a backup that silently stopped arriving only surfaced when you needed it. Here the toggle is the whole setup, and the surcharge is on the same prepaid balance as the database itself. One consequence we state plainly: if you leave, your dump files leave with us — export them first, because restore is manual and there is no self-serve download.

Yes, but not by default. A database starts private to your own applications; publishing it on a port takes an explicit, confirmed action by an admin. We keep it off by default because a database on the public internet is a materially different risk, and we do not firewall the port for you — restricting who can reach it is yours to do on the server.