Netlify vs Dokploy: which to choose

Netlify vs Dokploy: which fits your team's hosting decision

Teams that come here usually have a renewal, a move to credit-based billing or a data residency rule that makes Netlify's hosted model harder to justify. Netlify fits teams that want managed builds, a CDN and functions without operating servers, while Dokploy fits teams that want their apps running on servers they control. The decision turns on four questions: who will operate the servers, where the data must physically live, whether Netlify-specific features such as Forms and Functions are in use, and how the licensing of Dokploy's paid features affects your team. Start with operations. Netlify runs the build pipeline, the CDN and the edge, so your team pays for those as a service and carries little infrastructure work. Dokploy shifts that work to you: someone must size the host, patch Docker and the proxy, watch disk and renew certificates, and restore from backups. Its documentation sets a floor of at least 2 GB of RAM and 30 GB of disk, and the supported operating systems are listed in its installation docs. Confirm that the named owner has time for that work before you commit. Next, check the features your sites depend on. Static sites served from an NGINX container are a straightforward move, but Netlify Forms, Functions and Blobs have no direct equivalent in Dokploy, so each one needs a replacement service you run. Count those dependencies first. Then review licensing: Dokploy's core is Apache 2.0, but its proprietary directories, which include SSO, SCIM, audit logs and custom roles, fall under a source-available license that permits production use only under a commercial agreement. If you need those controls, ask Dokploy for the written terms before you rely on them.

Which platform fits which scenario

This table matches common team situations to the platform that fits better and the condition that decides it. Read each row against your own constraints, such as who operates servers, where data must stay, and which enterprise controls an auditor will ask about. The main takeaway is that Netlify removes more operating work for static and edge-delivered sites, while Dokploy fits teams that need server-side apps inside their own network.

Scenario	Better fit	Condition that makes it so
Static marketing site, no server staff	Netlify	Netlify's managed CDN, builds and forms remove patching and proxy work. Choose Dokploy only if the site must stay in your own network or you already run servers.
Static site that must stay on your own servers	Dokploy	Its Static build type serves the built files from an NGINX container on a server you control. Confirm who will renew TLS, patch the host and restore backups.
Server-rendered Next.js app with data in the company network	Dokploy	Nixpacks, Railpack or Dockerfile builds run the app next to the database on your own hosts. Next.js features are fully supported when deployed as a Node.js server or container, per the Next.js deployment docs.
Next.js app that depends on Netlify-specific features	Netlify	Platform adapter support varies by host, and the Next.js docs say Netlify is still working on a verified adapter. Test your exact feature set before moving.
Team needs SSO, SCIM or audit logs	Dokploy (Enterprise terms)	These features sit in the proprietary directories under the Dokploy Source Available License, so they need a commercial agreement. Ask for written terms covering production use.
Preview deployment for every pull request	Netlify or Dokploy	Netlify previews are managed. Dokploy previews need wildcard DNS and a server with enough capacity. Confirm the GitHub integration and cleanup behavior for your repository.
Multi-server or high-availability production	Netlify for static, neither for stateful clusters without planning	Dokploy clusters use Docker Swarm and a registry, and its docs recommend vertical scaling first. Plan horizontal scaling, registry and failover with an engineer before committing.
Data residency or air-gapped requirement	Dokploy	Only a self-hosted deployment keeps builds, databases and logs inside your own infrastructure. Confirm that the Dokploy core license terms allow your intended internal use.

Where your data and traffic live under each option

Netlify runs builds, functions and the CDN on its managed multi-tenant platform, while Dokploy runs on servers you provision in your own cloud account or data center. The cards below separate where data sits, who operates it, how sign-in works and what evidence you must assemble yourself.

Where build and request data sits

Netlify processes builds, bandwidth and function requests on its own managed infrastructure, so the regions and sub-processors involved are set by the vendor. With Dokploy, source code, build layers, container images and application data stay on the hosts you choose, which may be a single VPS in one region or several servers across providers. Confirm with Netlify which processing regions apply to your account and contract, and confirm with your own team which regions your Dokploy servers occupy.

Who operates the platform

On Netlify, the vendor patches, scales and secures the multi-tenant platform, and you rely on its contractual commitments. With Dokploy, your team or your implementation partner owns the Docker host, the Traefik proxy, OS patching and the Dokploy upgrade cycle. Ask Netlify for its current security documentation and shared responsibility terms, and write down who on your side is responsible for each Dokploy layer before go-live.

Identity and SSO coverage

Dokploy's Apache 2.0 core covers the basic sign-in and user model, but OIDC and SAML single sign-on, SCIM provisioning, audit logs and custom roles sit in the proprietary directories under the Dokploy Source Available License. Netlify's team and SSO options are defined in its own plan terms. Map each identity requirement to the plan or license tier that delivers it, and confirm the SSO and SCIM setup with Dokploy in writing before you rely on it.

Compliance evidence you must assemble

Neither option removes your obligation to show controls. Netlify may provide its own attestation reports under its contract, which you should request and review. For a self-hosted Dokploy stack, you will need to collect evidence yourself, including access logs, backup records, patch history and change records. DeployOpen can prepare the systems, controls and evidence for an assessment, but it does not issue audit reports or certifications; an independent auditor or certification body does that.

Backup and data retention

Dokploy deploys Postgres, MySQL, MariaDB, MongoDB and Redis and offers automated backups to S3 destinations you configure, so retention and the storage location become your decisions. Managed platforms handle platform-level recovery differently, so compare what each one restores and for how long. Confirm the backup target, encryption, retention period and restore test schedule for your Dokploy databases, and ask Netlify for its documented retention for deploy history and any data you store.

Terms that govern your deployment

Dokploy's terms describe core as free and open source but forbid commercial resale or redistribution of Dokploy as a service without explicit consent. If you plan to offer hosting to other business units, customers or subsidiaries, this clause matters. Review Dokploy's terms and the commercial agreement required for production use of proprietary features, and review Netlify's terms for data processing addenda, subprocessors and any data transfer mechanisms that apply to your region.

What the Apache 2.0 core and proprietary features mean for you

Dokploy is open core, so the license depends on which directory a file sits in. The root LICENSE.MD applies Apache License 2.0 to code outside /proprietary directories, while code inside them falls under the Dokploy Source Available License 1.0. That second license allows production use only under a commercial agreement with Dokploy. In practice, the Apache 2.0 core can be read, modified and self-hosted under its terms, but the enterprise controls in the proprietary directories cannot be assumed to be free for production. The proprietary code covers SSO with OIDC and SAML, SCIM, audit logs, custom roles and license key handling, so any requirement that depends on those controls needs a written commercial position before go-live.

The terms of service add a second constraint. Dokploy describes its core as free and open source, but commercial resale or redistribution of Dokploy as a service is forbidden without explicit consent from the Dokploy team. If you plan to run Dokploy for other companies, customers or business units billed back internally, ask Dokploy in writing whether that use is covered. The Enterprise tier, which includes SSO/SAML, SCIM, audit logs and an SLA, is listed at contact-sales pricing, so the cost of those controls is a quote item, not a published figure. Ask for the license scope, the entitled number of servers and users, the support terms and whether the agreement covers self-hosted installations. Before you rely on any feature, have counsel read LICENSE.MD, LICENSE_PROPRIETARY.md and TERMS_AND_CONDITIONS.md from the current repository and compare them with the features your identity, audit and access requirements actually need. Map each control to the directory that implements it, record the license that governs it, and confirm the version you deploy matches the files you reviewed.

How cost differs by hosting model

Netlify moved all new accounts to credit-based pricing on September 4, 2025, according to its documentation on credit-based pricing plans. Production deploys, bandwidth, web requests and compute draw from one monthly credit balance, so your bill follows how often you ship and how much traffic and server-side work your sites generate. You pay Netlify for plan access and for consumed credits, and the spend recurs every billing period.

Plan fee: The base plan is a recurring charge for the account, separate from any credits consumed.
Deploys: Every production deploy consumes credits, so frequent releases raise spend even when traffic is flat.
Bandwidth and requests: Traffic and web requests draw from the same balance, so a popular launch can exhaust credits.
Compute: Functions and other server-side work add to consumption, and heavy rendering increases the draw.
Pausing: When credits run out, projects on the account are paused, so ask exactly which features stop and how the team is notified.

Before comparing totals, ask Netlify for a usage estimate built from your last three months of deploys, bandwidth and function invocations, and confirm the credit rate for each category.

Cost components on each side, one-time and recurring

Netlify's bill is a plan fee plus credits that move with usage, while a self-hosted Dokploy install moves cost to servers, storage, DNS, backups and people. The cards below separate what you pay once from what recurs, and name the drivers and quote questions for each side.

Netlify plan fees and credits

Netlify bills new accounts in credits since September 4, 2025, and production deploys, bandwidth, web requests and compute all draw from one monthly balance. The recurring cost rises with traffic, build frequency and function use, not with the number of sites alone. Ask Netlify how each credit type is metered for your build volume and what happens when the balance runs out, since projects can pause.

Dokploy licence and paid tiers

Dokploy core is Apache 2.0, but SSO, SCIM, audit logs and custom roles sit under a source-available license that requires a commercial agreement for production use. Hobby and Startup tiers are listed on the pricing page, while Enterprise is quoted by contact. Check whether your team needs any proprietary feature before assuming the core is enough, and get the tier and server count in writing.

Servers, RAM and disk

Dokploy needs at least 2 GB of RAM and 30 GB of disk, and its docs recommend scaling vertically before adding nodes. Each server, managed or self-hosted, is a recurring line item, and multi-server setups add Swarm workers and a Docker registry to run. Size for build peaks and database growth, not just the idle minimum, and price the same capacity on your current cloud provider.

Backups to S3 storage

Dokploy offers automated database backups to S3 destinations you configure, so the bucket, its storage class, egress and retention become your recurring costs. Netlify's backup and recovery is largely outside your bill, so this is a new line to budget. Confirm retention periods, restore testing time and whether the bucket sits in your own account or region.

DNS, TLS and reverse proxy

Netlify includes a CDN and certificate handling in its platform fee. On Dokploy, Traefik on ports 80 and 443 handles routing and HTTPS, and you pay for DNS hosting, any CDN you add, and the time to keep certificates renewing. Costs here are small and recurring, but a CDN for global static delivery is a separate decision to price.

Staff time for patching and upgrades

Self-hosting moves OS patching, Docker and Dokploy upgrades, certificate checks and monitoring to your team. This is the largest recurring cost that is hard to see on an invoice, and it grows with the number of servers and sites. Estimate the hours per month internally, name an on-call owner, and compare that with the credits you would otherwise spend.

One-time migration and support retainers

Moving sites costs a one-time effort for rebuilding build settings, redirects, environment variables and preview wiring, plus any testing you commission. An ongoing support or upgrade retainer from DeployOpen is optional and fixed-scope, so it is priced from the written scope, not from a list price. Ask for deliverables, what the retainer covers and how changes are billed.

What moving a Netlify site to Dokploy involves

The sequence takes a Netlify site from an inventory of builds, redirects and forms to a Dokploy-hosted site on servers you control, with DNS, TLS, backups and a rollback path in place before Netlify is switched off.

Inventory sites, redirects and dependencies
List every Netlify site, its build command, publish directory, environment variables, custom domains, redirect and header rules from _redirects and netlify.toml, and every feature in use such as Forms, Functions, Blobs, identity or split testing. The owner of each site confirms the list. Done when each site has a row in a written inventory with its features marked as static, server-rendered, or dependent on a Netlify-only service.
Provision a server that meets Dokploy's requirements
Confirm the chosen operating system is on Dokploy's installation list and that the server has at least 2 GB of RAM and 30 GB of disk, as stated in the installation docs. The infrastructure team opens ports 80, 443 and 3000, plans access to the web interface, and decides whether this is a single server or a cluster. Done when the server passes the install checks and the Dokploy dashboard loads over the intended private or public path.
Choose build types for each site
Assign each site a build type. Static sites that produce plain HTML, CSS and JavaScript use the Static build type, which serves output from an NGINX container. Server-rendered apps use Nixpacks (the default), a Dockerfile, or a buildpack type. Confirm framework support in the build type docs and record the choice per site. Done when each site has a documented build type and a test build has succeeded on the Dokploy server.
Rebuild, translate rules and test
Recreate each redirect and header rule at the proxy in front of the site, since Netlify's file formats are not read by Dokploy. Test every redirect, 404 page, header and environment variable on a staging domain. Compare responses with the Netlify production site for a sample of URLs. Done when a test log shows the same status codes and redirect targets for the agreed URL list and the owner signs off.
Replace Forms and Functions with owned services
Netlify Forms, Functions and Blobs have no direct equivalent inside Dokploy, so each dependency needs an owned replacement such as an application endpoint, a database in Dokploy, or an external service the organization already runs. Export existing form submissions before cutover. Done when every Netlify-only feature has a named replacement, a tested endpoint, and a stored export of historical data.
Set up backups, rollback and monitoring
Configure automated database backups to an S3 destination in Dokploy's settings and confirm a restore works on a test copy. Coolify's guide for teams leaving managed platforms notes that a rollback can redeploy a retained application image but does not restore databases or persistent files, so plan those separately. Done when a restore test completes, a rollback to the previous image is rehearsed, and uptime alerts reach the on-call owner.
Move DNS and TLS, then decommission Netlify
Lower DNS time-to-live ahead of the change, point each domain to the Dokploy server, and confirm certificates are issued for every hostname. Keep Netlify live for a verified overlap period agreed by the owners, then stop builds, remove domains and export final archives before cancelling the account. Done when all domains resolve to the new server with valid certificates, traffic and error rates look normal, and a final Netlify export is stored.

Questions buyers ask before switching from Netlify to Dokploy

How much work does moving from Netlify to Dokploy take?

The effort depends mostly on how many sites you run, how each one is built, and how much Netlify-specific behavior they rely on. A plain static site built from a Git repository is usually the simplest case, because Dokploy's Static build type serves the output from an NGINX container. Server-rendered apps need a Nixpacks, Railpack or buildpack configuration and a check that the runtime, environment variables and build commands match what Netlify ran. The main drivers are the number of sites, the number of redirect and header rules to port, any Netlify Functions or Forms in use, and the count of databases or external services attached to each project. Ask for a written scope that lists each site and its dependencies before anyone commits to a timeline.

Can our internal team migrate to Dokploy without outside help?

Yes, a team with Linux server and Docker experience can run Dokploy themselves, and the core is Apache 2.0 licensed. The questions to answer honestly are whether someone will own the server after go-live, who handles patching and backups, and whether the team has time to rebuild each site's pipeline. Dokploy's installation docs list at least 2 GB of RAM and 30 GB of disk, and its tested operating systems include Ubuntu, Debian, Fedora and CentOS, so the platform itself is modest to start. Where an internal team lacks capacity or wants a second pair of eyes on hardening and runbooks, DeployOpen can plan and implement the work under a fixed-scope agreement.

What access and ownership does a Netlify to Dokploy move require from us?

Expect to provide several things before work starts. You need access to the Git repositories, the Netlify project settings including environment variables, the DNS zone that points to your sites, and a server or cloud account where Dokploy will run. You also need a named owner for runbooks, who will approve DNS changes, decide cutover windows and accept responsibility for restores. Dokploy's remote server documentation covers how additional servers are attached, and its database docs cover automated backups to S3 destinations, which the owner should configure and test. Record who holds each credential, because a rollback depends on it.

What happens to Netlify Forms and Functions after switching to Dokploy?

Dokploy does not provide a built-in equivalent of Netlify Forms or Netlify Functions, so you need to decide where each one goes. Forms usually move to a self-hosted form handler or to an endpoint in your own application that stores submissions in a database you control. Functions move to server routes in the application itself, to a separate service deployed in Dokploy, or to a Docker container. Export existing form submissions before cutover, since they live in Netlify. Test every form end to end, including spam filtering, notifications and file uploads, because these are the parts most often missed. Confirm each replacement's data handling against your own privacy and retention requirements.

How do deploy previews in Dokploy compare with Netlify deploy previews?

Dokploy's preview deployments create a running environment for a branch or pull request, which is the same basic idea as Netlify's deploy previews, but the setup and limits differ. You will need to configure the Git provider integration, a domain pattern for previews, and a cleanup policy so old environments do not accumulate on your server. Netlify previews are generated and hosted by Netlify, so their resource use is part of your Netlify plan, while Dokploy previews consume the CPU, memory and disk of the server running them. Check the preview documentation for the exact behavior in your chosen Git provider and confirm how previews interact with database seeds and secrets.

Does single sign-on in Dokploy require a paid tier?

Yes, based on the license split in the repository, SSO features are not in the Apache 2.0 core. Dokploy's proprietary directories include SSO with OIDC and SAML, SCIM, audit logs and custom roles, and these are source-available under the Dokploy Source Available License rather than open source. The company's pricing page places SSO/SAML and SCIM under its Enterprise tier, which is priced on contact. If your identity provider policy requires SSO for administrators, confirm the current license terms and tier with Dokploy before you plan the rollout, and check whether your intended use of the source-available code is permitted under the commercial agreement.

What changes if our Netlify credits run out, and how does Dokploy handle cost?

On Netlify, new accounts draw production deploys, bandwidth, web requests and compute from one monthly credit balance, and a team that exhausts it can see its projects paused. Dokploy has no credit balance, so the cost shifts to the servers you run, your Dokploy plan if you use one, and the time your team spends operating the platform. Compare the fixed cost of the server and any Dokploy fee against your current credit spend and your traffic pattern. Ask for a written breakdown of which costs recur monthly and which are one-time, such as the migration itself. Dokploy's Hobby tier is listed at $4.50 per month per server, and Startup starts at $15 per month for up to 3 servers, according to its pricing page.

Questions to answer before choosing either option

Start with who will operate the platform. Netlify is a managed service, so its builds, CDN, previews and uptime belong to the vendor. Dokploy is self-hosted: your team installs it on a server, keeps Docker and Traefik patched, sizes the machines and owns backups for any databases it runs. Dokploy's documentation lists a minimum of 2 GB of RAM and 30 GB of disk, but the realistic sizing depends on your build load and traffic, which you should test in your own environment. Ask whether you have an on-call rotation that can take that work, and whether a fixed-scope engagement or a retainer would cover what your staff cannot.

Next, check whether data residency rules limit a managed CDN. If your policy requires that site content, logs or form data stay in named regions or in your own facilities, a self-hosted Dokploy server gives you control over where those bytes sit, but it also means you must provide the edge caching, DDoS protection and TLS termination that Netlify provides. Confirm with your compliance lead which data actually flows through a static site, and how many servers and users you need, because Dokploy's Hobby plan covers one server and one user while its Startup plan covers up to three servers and basic role-based access, and each tier's terms should be checked on the Dokploy pricing page.

Finally, decide whether you need proprietary features and how much Netlify functionality you use. Single sign-on through OIDC or SAML, SCIM, audit logs and custom roles sit in the proprietary part of Dokploy's repository and fall under the Dokploy Source Available License rather than Apache 2.0, so a regulated team should read the Dokploy license file and the proprietary license before assuming the free core is enough. List the Netlify features your sites depend on, such as forms, functions, redirects, branch previews and Blobs, and map each one to a replacement before you compare costs.

Netlify vs Dokploy