Can I move a Netlify site to Ploy?

Static sites and Vite apps move by connecting the repository and adding a ploy.yaml with the build command and output directory. Netlify Functions become a worker next to the frontend, and scheduled functions become cron triggers in ploy.yaml.

Does Ploy have something like Netlify Blobs?

Yes. File storage gives every project an S3-style object store with put, get, list, and delete, and state gives you a durable key-value store with atomic JSON updates. Both are declared in ploy.yaml and appear on env in your worker.

What about background jobs?

Ploy includes queues with automatic retries and durable workflows whose steps are persisted as they complete. On Netlify, long-running work means Background Functions on a paid plan or an external job system.

Ploy vs Netlify

Netlify made git-based deploys and deploy previews the default for frontends. Ploy keeps that workflow and adds the backend: serverless workers with SQLite databases, queues, cron, durable workflows, sandboxes, auth, and model access, all open source and self-hostable.

Open sourceSelf-hostableFull backendNo lock-in

Deploy for free

Read the docs

Compare platforms

Side by side

Compare Ploy and Netlify feature by feature

Ploy

Open source · Batteries included

From $0

Self-host free forever

Netlify

Proprietary & hosted

From $0

Free plan with limits

Deployment & infrastructure

Self-hosting option

Deploy on your own infrastructure

Run the full platform yourself

Open source

Full access to source code

AGPLv3

Preview deployments

A URL for every branch

Deploy Previews

Git sources

Where your code can live

GitHub, or Ploy Git with no GitHub account

GitHub, GitLab, Bitbucket, Azure DevOps

Serverless compute

Where backend code runs

Isolate-based workers, scale to zero

Netlify Functions and Edge Functions

Long-running work

Jobs that outlive a request

Queues and durable workflows

Background Functions (Pro)

Pricing

Free self-hosting

Host unlimited projects for free

Forever free

Free managed tier

What the free plan includes

3 repositories, unlimited previews

Free plan with monthly limits

Paid plan

First paid tier

Pro at $10/month per organization

Pro, billed per member

Build minutes

Free tier build time

Unlimited when self-hosted

300 min/month (Free)

Bandwidth

Free tier data transfer

Unlimited when self-hosted

100 GB/month (Free)

Developer experience

Frameworks

First-class framework support

Next.js, Vite, TanStack Start, static sites, workers

Most frontend frameworks

Custom domains

Use your own domain names

Pro plan

Environment variables

Manage secrets and configuration

Monorepos

Several projects from one repository

Every ploy.yaml is a project

Local development

Run the platform's services on your machine

ploy dev emulates databases, queues, cron, and workflows

netlify dev

Config as code

Declare the project in the repository

ploy.yaml

netlify.toml

Built-in platform services

Databases

SQL storage attached to your project

SQLite per project, migrations from git

Netlify DB (beta, Postgres)

Queues

Background jobs and async messaging

Included, retries built in

Bring your own

Cron and timers

Run code on a schedule

Included, down to the second

Scheduled Functions

Durable workflows

Multi-step jobs that survive failures

Included, per-step retries

Bring your own

State and file storage

Key-value state, cache, and object storage

Included

Netlify Blobs

Sandboxes

Isolated environments for untrusted code

Included

AI gateway

Model access without provider keys

Included, OpenAI-compatible

AI Gateway

Authentication

User sign-up, sign-in, and sessions

Included, stored in your database

Via extensions

Why choose Ploy?

The backend is included: Databases, queues, cron, workflows, storage, and auth are declared in ploy.yaml, not bolted on afterwards.

Same workflow, more room: Git push, previews per branch, rollbacks, and environment variables work the way you expect.

Open source and self-hostable: Run the whole platform on your own infrastructure under AGPLv3 with no usage limits.

Built for agents too: Durable workflows, sandboxes, and an AI gateway are there when an app grows beyond request/response.

Choose Ploy if

Your app needs a database, background jobs, or scheduled work and you do not want to run them elsewhere.
You want one platform for the frontend and the backend, including workers that scale to zero.
You need to self-host, or want the option to later without changing your code.
You are shipping AI features or agents and want sandboxes and model access built in.

Choose Netlify if

You are deploying a static site or Jamstack frontend and the backend lives somewhere else.
Your team relies on Netlify-specific features such as its forms, split testing, or extensions.
You deploy from GitLab, Bitbucket, or Azure DevOps and do not want to add a remote.

Frequently asked questions

Can I move a Netlify site to Ploy?: Static sites and Vite apps move by connecting the repository and adding a ploy.yaml with the build command and output directory. Netlify Functions become a worker next to the frontend, and scheduled functions become cron triggers in ploy.yaml.
Does Ploy have something like Netlify Blobs?: Yes. File storage gives every project an S3-style object store with put, get, list, and delete, and state gives you a durable key-value store with atomic JSON updates. Both are declared in ploy.yaml and appear on env in your worker.
What about background jobs?: Ploy includes queues with automatic retries and durable workflows whose steps are persisted as they complete. On Netlify, long-running work means Background Functions on a paid plan or an external job system.

Deploy for free All comparisons

No credit card required • Self-host option available • Open source under AGPLv3