DeployVera PaaS · Netlify alternative

Netlify alternative: when to pick DeployVera, when to stay

Netlify is a mature platform for frontend projects. DeployVera runs Docker or static apps from GitHub on a fixed monthly plan. This page explains when each fits and where the settings in your netlify.toml end up on DeployVera.

Last reviewed:

Netlify may fit better

  • You build a frontend-heavy project and want a preview deployment for every change; Netlify’s Free plan includes unlimited deploy previews.
  • You use platform features such as Functions, the global CDN, Blob storage or Netlify Database.
  • Your team workflow depends on Netlify’s previews and deploy contexts.

DeployVera may fit better

  • Your app is a Dockerfile-based API or web app that must run continuously.
  • You want the monthly price in TRY, shown with CPU, RAM, NVMe and application limits up front.
  • You want to publish a static site or SPA on a permanent free plan without a card.
  • You want managed PostgreSQL, MySQL, MongoDB or Redis (beta) next to the app.
  • You want to manage deployments from an AI agent such as Claude or Cursor.

What DeployVera does not offer

  • No per-pull-request preview deployments, serverless or edge functions, or global CDN.
  • Redirect and header rules in netlify.toml are not read.
  • No equivalent of platform services such as Netlify Forms or Identity.
  • Databases are beta; backups are platform-level with no self-service download.

Where do netlify.toml settings go on DeployVera?

The example is a typical Vite SPA netlify.toml. The table maps each section.

netlify.tomlOn DeployVeraNote
[build] commandBuild command in the panel, or a DockerfileBuild and start commands are set in the technical settings.
[build] publishStatic frontend / SPA publish directoryThe repository root is rejected as publish directory; use a subfolder such as dist.
[[redirects]]Built-in SPA fallback; Dockerfile for the restStatic mode falls back to index.html for unknown paths. For 301s and similar rules use a Dockerfile with Nginx.
[build.environment]Environment variables in the panelKeep secrets out of the repository; enter them in the panel.
[context.*]No direct equivalentAn application follows pushes to its one connected branch. For staging you can create a separate application (it uses its own application slot).

Steps to move from Netlify to DeployVera

The example is a Vite-built SPA. For a server app with a Dockerfile, choose the Dockerfile method in step 2.

  1. 1.Read your netlify.toml

    Note the build command, publish folder, redirects and environment variables.

    [build]
      command = "npm run build"
      publish = "dist"
    
    [build.environment]
      NODE_VERSION = "20"
    
    [[redirects]]
      from = "/*"
      to = "/index.html"
      status = 200
  2. 2.Connect the repository and pick a method

    Connect GitHub and choose the repository and branch. For a static site or SPA keep the automatic build method, enable Static frontend / SPA and set the publish directory to /dist; the port becomes 80 automatically. For a server app choose the Dockerfile method and make sure it listens on 0.0.0.0 and the port you set.

  3. 3.Enter build and start commands

    Move the command value from netlify.toml to the build command in the panel’s technical settings. If you need a version (for example NODE_VERSION), pick the runtime version in the same settings group.

  4. 4.Add environment variables in the panel

    Define the values you kept in the Netlify UI or under [build.environment] as environment variables in the DeployVera panel. For build-time variables that reach the browser (for example those starting with VITE_), set the value before the build.

  5. 5.Adapt redirects

    An SPA needs nothing extra: unknown paths fall back to index.html. If you need real 404s or 301s, use the Dockerfile method and copy your own Nginx configuration into the image. If you use Functions, move them into an always-running Node.js server.

  6. 6.Deploy, test, then switch the domain

    Watch the first deployment’s build logs and open the home page and sub-pages on the temporary address, including a refresh on a sub-page. When it works, add your domain, apply the DNS record the panel shows and check HTTPS. Keep the Netlify site up until DNS has switched.

Sources and notes

  • Netlify’s Free plan is $0 with 300 credits; Personal is $9 (1,000 credits) and Pro is $20 (3,000 credits). Production deploys, compute and bandwidth use credits. Check the official pricing page for the current state.
  • netlify.toml can define [build] command and publish, [[redirects]], [context] and environment variables; contexts and redirects are Netlify-specific.

Sources

Frequently asked questions about moving from Netlify

Can I move my static Netlify site to DeployVera?

Yes. With Static frontend / SPA the build output folder is served by Nginx. The repository root is not accepted as publish directory; choose a subfolder such as dist or public.

Do the redirects in netlify.toml work?

DeployVera does not read netlify.toml. For SPAs, unknown paths already fall back to index.html. For other redirect and header rules add an Nginx configuration through a Dockerfile or define them in application code.

Do Netlify Functions run on DeployVera?

No. There is no serverless or edge function support. You can turn your functions into an always-running HTTP app and publish it with a Dockerfile.

Is the free plan enough?

DeployVera’s permanent free plan includes 0.5 vCPU, 512 MB RAM, 2 GB storage and one application, with no card. It can be enough for a small static site or demo; limits are in the live catalog.

Can I pay in Turkish lira?

DeployVera lists plans in TRY. Netlify’s pricing page shows amounts in US dollars.

Try it on the free plan first.

Publish a parallel copy on DeployVera without shutting down your Netlify site, then switch the domain when it works.

Create a free account