vsNetlifyA gigabyte is 20 credits there, a production deploy is 15. Deplo has one number a month, and it is the server.
All three are on their own price list, converted at the price of a credit pack.
The Pro plan carries 3,000 credits, which is 150 GB of traffic, and the next 1,500 cost $10. A terabyte is 20,000 credits: $126 a month on their biggest Pro tier, before a single deploy. Here nobody counts the gigabytes.
A production deploy costs credits whether the change was a feature or a typo. Here a deploy costs the CPU time of a machine you already pay for, twenty times a day if you like.
Netlify runs functions for the length of a request: a background one stops at fifteen minutes, and none of them keeps a disk. Its database is Postgres and nothing else. Here a worker, a queue and any database are apps with a volume each.
The Pro plan carries 3,000 credits, which is 150 GB of traffic, and the next 1,500 cost $10. A terabyte is 20,000 credits: $126 a month on their biggest Pro tier, before a single deploy. Here nobody counts the gigabytes.
A production deploy costs credits whether the change was a feature or a typo. Here a deploy costs the CPU time of a machine you already pay for, twenty times a day if you like.
Netlify runs functions for the length of a request: a background one stops at fifteen minutes, and none of them keeps a disk. Its database is Postgres and nothing else. Here a worker, a queue and any database are apps with a volume each.
Three answers, two numbers. Theirs comes from their published rates, credits converted into dollars; ours is a plan you can buy today.
$137/ month
Nothing stays awake here. A function runs for the length of a request, a background one stops at fifteen minutes, and a worker lives somewhere else, with a bill of its own. Their Postgres is the only database on offer.
$16.71/ month
CubePath gp.starter
8 GB of memory
Netlify Pro numbers are their published list, read on 8 October 2026. Credits are converted at $10 for 1,500, the price of a Pro pack: a gigabyte is 20 credits, about $0.13, and the 3,000 credits in the plan are counted as the first 150 GB. Production deploys, 15 credits each, are not counted. Pro tiers up to 20,000 credits for $126 make heavy traffic a little cheaper. www.netlify.com
Click around a real Deplo on a real server for a few minutes. No email, no password, nothing to migrate yet.
Try the demoDeploys, backups, logs, metrics and TLS, already on. Nothing to buy on top, nothing to hunt down.
Ask, and it's done. Connect Claude, Cursor or any assistant that supports MCP, and it can deploy, read the logs and roll back when you ask in plain words. It works with a key you create and can revoke at any time, and it can never do more than you can. Nothing connects until you create a key, and one switch turns it off for the whole team.
Your whole release process becomes a push. Connect GitHub, GitLab, Bitbucket or Gitea once. Every push to your main branch goes live, every pull request on GitHub gets its own preview link that disappears when it closes, and a bad release goes back to the version that worked.
Your team works on the same apps without stepping on each other. Give each person exactly the access they need, like "can deploy, can't delete", and hand a freelancer or a client one project and nothing else. The activity timeline shows who did what and when, right in the dashboard.
Your app online without touching a setting. Connect the repo and you get a live link, and HTTPS the moment you add your domain. Deplo recognises your framework and builds it for you, and Postgres or Redis sits next to your app in two clicks. Same stack you ran on the cloud. Only the bill changed.
What stays the same, what changes, and what it costs.
For a small site, yes: the $20 plan covers up to 150 GB if nothing else spends the credits, and the free one covers a side project. Every production deploy takes 15 of them, and the gap opens with traffic, where every gigabyte is 20 credits, and with anything that has to stay awake.
Yes. The Static build method serves the files your build produces, with a switch for single-page apps so unknown paths land on index.html. Free SSL on your own domain and, from GitHub, a preview for every pull request come with it.
Your framework's own server runs in the container, so its API routes keep working. What does not come across are the platform products: Netlify Blobs, Edge Functions and the database that ships with the account.
The global CDN, the free tier, and somebody else's on-call. The page is served from the region your server is in, unless you put a CDN in front of it yourself.
Answer three questions and pick a host, or install Deplo on a server you already have. It's free, and leaving is as easy as arriving. What you do with the money you save is your business.
Netlify
