Ample vs Netlify: which should host an app with a backend? · Ample Computer
Ample vs Netlify: which should host an app with a backend?
Ample and Netlify compared on backends, languages, databases, storage and agent access, with sourced limits and steps to move a Netlify project.
Checked November 5, 2026
the short version
Netlify is the better choice for static sites and front ends whose dynamic work fits short JavaScript or Go functions. Ample is the better choice for an app with a real backend: a Python, Ruby, PHP, Java or Node server, a worker or a WebSocket service, with Postgres, MySQL, Redis or MongoDB that a coding agent can deploy alone.
Who this is for
Netlify is built around a global CDN and serverless functions; it says itself that it has no long-lived server. Ample runs the server. If your app is mostly static, Netlify is hard to beat; if the backend matters, read on.
Ample and Netlify side by side
| Round by round | Ample | Netlify |
|---|---|---|
| Free plan | Yes. Free is $0 for up to 2 apps, with no card. | $0 with 300 credits a month as a hard limit, including functions, Netlify Database and Blobs. |
| Paid plans | Pro is $20 a month for up to 10 apps and Scale $99 a month for up to 50. Every plan includes compute, databases, S3 storage, a CDN and scheduled jobs. | Personal $9 a month (1,000 credits), Pro from $20 a month (3,000 credits), with unlimited members. |
| Spending limit | A hard spending cap on every plan, on by default: apps pause and are never billed past it. | When credits run out, every project on the team pauses until the next cycle unless auto recharge is turned on. |
| How apps run | Each app runs as a normal long-running process in its own microVM with its own kernel. | Serverless functions and Deno-based edge functions; no long-lived server. |
| Long-running servers and workers | Yes. Web services and background workers (--kind worker) run as ordinary processes, with WebSockets, streaming responses and requests of 10 minutes or more. |
No. Synchronous functions stop at 60 seconds and background functions at 15 minutes. |
| Languages | Node, Python, Go, Ruby, PHP, Java, .NET, Elixir, Rust and static sites, detected from the repository. | TypeScript, JavaScript and Go functions. |
| Docker images | Not needed: Ample Computer builds from source and runs your start command; a Dockerfile's own steps are not run. | No. |
| Databases | Managed Postgres (with pgvector), MySQL, Redis and MongoDB, each in its own microVM, created automatically when the code needs one. | Netlify Database, managed Postgres that sleeps after 5 minutes idle; 3 databases on Free. |
| Object storage | S3-compatible buckets, optionally published through Ample's CDN. | Netlify Blobs (its own SDK; no S3 API documented). |
| Persistent disk | Persistent volumes attached to the app. | None. |
| Custom domains and TLS | Custom domains with automatic TLS. | Custom domains with automatic Let's Encrypt certificates on all plans. |
| Regions | The USA and Europe, placed automatically; the USA is the default. | Global CDN; functions run in one selectable region. |
| Scheduled jobs | Scheduled jobs: a command or HTTP request on a cron schedule (any time zone) or interval, with retries and run history (ample job create). |
Scheduled functions with a 30-second limit. |
| Agent access | CLI, remote MCP server (OAuth), A2A endpoint and agent skills. Deploys are synchronous and return JSON with an exit code: 0 live, 1 failed, 2 needs input. | Remote MCP server, a ChatGPT app, a Claude connector, agent skills and llms.txt. |
| Agent signup without a person | Yes. ample auth signup creates an account with no browser, card or CAPTCHA; a person claims it by email within 48 hours. |
Partly. netlify deploy --allow-anonymous publishes a static site without an account, to be claimed within an hour; functions need an account. |
Choose Ample when
- ✓ The backend is written in Python, Ruby, PHP, Java, .NET or Elixir, or is a Node server rather than functions.
- ✓ Requests or jobs run longer than function limits, or the app keeps WebSocket or SSE connections open.
- ✓ You need MySQL, Redis, MongoDB, a persistent disk or S3-compatible buckets.
Choose Netlify when
- ✓ The project is a static site or a front end with light serverless functions.
- ✓ You use Netlify Forms, Identity, deploy previews or per-preview database branches.
- ✓ You want your pages served from a global edge network.
Move a Netlify project to Ample
Translate netlify.toml. Note the build command and publish directory, redirects in
_redirectsornetlify.toml, and any scheduled functions.Wrap functions in a server. Netlify Functions become routes in a small server (for example Hono or Express); background functions become a worker, and scheduled functions become Ample jobs (
ample job create).Plan and deploy. A static site deploys as a static service; an app with a server gets a web service and any database it needs.
$ ample plan --write && ample upMove data. Dump Netlify Database with
pg_dumpand restore it; copy Blobs into an Ample bucket and switch to an S3 client.Point your domain. Add the domain to the app, update DNS to the target Ample prints, and keep the old app running until the new one answers on the domain.
$ ample domain add <app-name> www.example.com
Frequently asked questions
Can Ample host a static site like Netlify?+
Yes. A folder with an index.html or a Vite build deploys as a static service with HTTPS. Netlify's global CDN will usually be faster for visitors far from Ample's servers.
Can I keep Netlify for the front end and use Ample for the API?+
Yes. Deploy the API to Ample, set its URL in the front end's environment, and keep the site on Netlify.
Sources · every claim about them, checked
- Ample agent instructions (AGENTS.md) (checked 2026-10-14)
- Netlify pricing (checked 2026-10-14)
- Netlify credit-based plans (checked 2026-10-14)
- Netlify paused projects (checked 2026-10-14)
- Netlify vs Render (Netlify knowledge base) (checked 2026-10-14)
- Netlify functions configuration (checked 2026-10-14)
- Netlify functions languages (checked 2026-10-14)
- Netlify Database (checked 2026-10-14)
- Netlify Database billing (checked 2026-10-14)
- Netlify Blobs (checked 2026-10-14)
- Netlify HTTPS (checked 2026-10-14)
- Netlify function regions (checked 2026-10-14)
- Netlify MCP server (checked 2026-10-14)
- Netlify deploy from AI tools (checked 2026-10-14)