Pick Agent Lab
A site plus an always-on backend: an API, a LINE bot, webhooks or an MCP server.
Agent Lab vs Netlify · Compare and migrate
Netlify is for static sites and serverless functions, with no always-on services; Agent Lab hosts both static pages and always-on backends, in Taiwan. Facts about Netlify come from its own pages, checked on 2026-10-18, with a source on every row.
> move this app from Netlify to Agent Lab
sites_build_planstart command found · listens on $PORT
sites_createshop-api → shop--acme.hosting.agentlab.run
databases_connect_appDATABASE_URL written, password hidden
Preview is up. Import the data with pg_restore, test it, then point your domain here; Netlify keeps running until you do.
Which one fits
Two reasons to pick Agent Lab, and two to stay on Netlify.
A site plus an always-on backend: an API, a LINE bot, webhooks or an MCP server.
Static pages, backends, PostgreSQL and scheduled jobs in one workspace, hosted in Taiwan.
Purely static or Jamstack sites that need a global CDN and branch deploy previews.
Backends that fit in short functions, with nothing that needs to stay on.
Side by side
Netlify's side is from its official pricing and docs pages on 2026-10-18; prices change, so follow the source link before you decide.
Scroll the table sideways.
| Agent Lab Deploy | Netlify | |
|---|---|---|
| Free tier | Free US$0: 1 size-S app (sleeps after 15 idle minutes), 1 S database, 3 static sites; pauses at a limit, never charges Details | 300 credits a month, with a hard limit Source |
| Cheapest always-on service | Pro US$29 a month before tax; its usage credit runs one size-S app all month Details | No always-on services, only functions (60 s synchronous, 15 min background); Personal US$9 a month Source |
| PostgreSQL | Managed PostgreSQL 16–18, MySQL 8.4 and 9.7, one dedicated instance per database; Free includes one S Details | Netlify Database (built on Neon), billed in credits Source |
| Nearest region to Taiwan | Google Cloud, Taiwan Details | Functions in Tokyo or Singapore on Pro and above; Ohio by default Source |
| Deploy from an AI tool (MCP) | Remote MCP with browser OAuth sign-in, no API key, the same permissions as the console Details | Official remote MCP Source |
| Roll back | Every version has a preview URL; roll back to an earlier version in the list, with no rebuild Details | Yes, publish an earlier deploy in one click Source |
Migrate
Netlify keeps serving until you change DNS.
Save the environment variables and secrets from Netlify, and note the start command, scheduled jobs and domains.
Upload, push from GitHub, or ask your AI tool through Agent Lab MCP. You get a preview URL.
Create PostgreSQL and connect it to the app, then pg_dump from the old database and pg_restore into the new one.
Test the preview, lower the DNS TTL, then point the domain at Agent Lab. Roll back in one step if something is off.
From Netlify
# List a Netlify site's environment variables
netlify env:list
# Netlify Database: export the data
pg_dump "$NETLIFY_DATABASE_URL" --no-owner --format=custom -f backup.dump
# Import into Agent Lab PostgreSQL (connection string in the console;
# add your IP to the database's allowlist first)
pg_restore --no-owner --no-acl -d "$AGENTLAB_DATABASE_URL" backup.dumpStatic site Upload the built folder (index.html at the top), or upload the source and let the platform build it.Netlify Functions They don't become a service by themselves; turn them into one server (Express or Hono).Scheduled Functions Becomes an Agent Lab scheduled job. A job calls a URL of your app on a clock, so the script becomes an HTTP endpoint.netlify.toml Not read. The platform detects the build command, or set it in build settings.Read https://app.agentlab.cresclab.com/agent/deploy.md. This project runs on Netlify today; move it to Agent Lab. First list what it uses on Netlify (services, database, scheduled jobs, environment variables, domains) and what each becomes on Agent Lab, deploy it to a preview URL, tell me where to enter secrets, and wait for my OK before anything goes live or DNS changes.FAQ