Ship your code.Know your bill upfront.

  1. 01Connect your repository
  2. 02Start your build
  3. 03Go live

Connect your repository. Deploy your Docker apps. Focus on your product while we manage the servers.

Connect Claude, Cursor or VS Code and ship with one sentence.

$0 · Free forever · One application, 512 MB RAM. No card required.

With DeployVera, I commit and push; it takes care of the rest.
Meltem Tekeli AkdağIoT Software Development Team Lead
Meet Veyra

Tell Claude or Cursor,and it ships.

DeployVera's MCP server lets the AI agent that writes your code see your projects, deploy them, follow the build and explain what went wrong. No trip to the terminal or the panel.

  • Browser sign-inYou sign in in the browser and choose which of read, deploy and env to grant, and for how long. Personal tokens are available for CI.
  • Approval for risky actionsRollbacks, deleting env vars, creating a project and attaching or removing a domain always need your approval in the browser, confirmed with password and 2FA. You can require approval for every deploy too.
  • The agent never sees valuesThe agent can add and update env vars, but their values are never shown back to it. Database listings and logs carry no credentials either.

Works with Claude (web, desktop, Claude Code), Cursor, VS Code, Codex and any MCP client.

An example sessionMCP
  1. You:

    ship the latest change

  2. Agent:

    deploy get_build wait_seconds=120

    Build finished. Live at shop-api.deployvera.com

  3. You:

    ship the login fix too

  4. Agent:

    deploy get_build wait_seconds=120

    Build failed.

    explain_build_failure

    Cause: package-lock.json is out of sync with package.json.

    Fix: run npm install and commit the updated lockfile.

  5. You:

    roll back the live version

  6. Agent:

    rollback

    Approval needed. Confirm in your browser: deployvera.com/approve

Push. Deploy. Done.

Less server work.More product.

  1. 01

    Connect your repository

    Connect your Git provider and select the repository and branch to deploy.

  2. 02

    Start your build

    Build with Dockerfile or Nixpacks and follow the logs in your panel.

  3. 03

    Go live

    Open your app at its HTTPS address; keep internal services on a private network.

  4. 04

    Monitor and iterate

    Track resources, choose a commit or return to a successful image.

A real project.Running in production.

Connect your repository. Deploy your Docker apps. Focus on your product while we manage the servers.

Open the live project
deployvera / examplemain

~ git push origin main

  1. Connect your repository01
  2. Start your build02
  3. Go live03
yusufcelalcelik.com
Veyra

Meet Veyra.

DeployVera’s project assistant. Coming soon to your panel.

Veyra knows your projects: she explains in plain language what is live, why a build failed and what the security scan found. She only reads. She never changes anything on your behalf and never sees your env values. Even her name comes from here: Deploy + Vera.

Launch your first application

Defined resources.You are in control.

01

Databases without using app slots

Run PostgreSQL, MySQL, MongoDB and Redis (beta) within your service resource pool. Open Adminer or Mongo Express from the panel; enable temporary external access for MongoDB Compass. Manage and export your data.

02

Smart builds and SPA routing

Nixpacks detects Node.js, PHP, Python, Go and Ruby. Choose Node.js, PHP and Python versions in the panel. Enable SPA mode for React/Vite/Vue so Nginx routes nested URLs to index.html.

03

Choose a commit, roll back, monitor

Deploy one of the last 50 commits or a custom SHA. Quickly return to a retained successful Docker image. Track CPU, RAM and Swap with Beszel and historical averages over 1 / 20 / 120 / 480 minutes, depending on the period.

Runs a database + worker → guide

Start with one site.Grow with your product.

Manage your site, API and database in one workspace. Apps get HTTPS addresses; database connections stay on the internal network.

Example application architecture

FrontendHTTPS
APIHTTPS
PostgreSQL Internal

2 / 3 application slots Container Starter 1 vCPU · 1 GB RAM

Databases are in beta and use separate quotas.

DeployVera / productionmain

New commit available

Interactive interface example — not real project data

See the version.Keep control.

Notice when a new commit leaves the live version behind. Follow deployments and the published version in the same panel.

Start free

Engineers, in their own words.

Deploying a project used to take me hours: I would search for the right setting in cPanel, hardcode environment variables and deal with server-specific issues. With DeployVera, I commit and push; it takes care of the rest.

Meltem Tekeli AkdağIoT Software Development Team Lead

Choose what you need.Know what you pay.

Founder discount · 50% 50% founder discount on eligible direct paid orders · 9 spots · Permanent founder discount for the first 10 customers. Excludes the free plan.

Container Free

$0/ mo

Free with no time limit. No card or invoice.

  • 0.5 vCPU
  • 512 MB RAM
  • 2 GB NVMe
  • Up to 1 deployments
Start free

Container Starter

$7

$3.5/ mo

Billed monthly.

  • 1 vCPU
  • 1 GB RAM
  • 5 GB NVMe
  • Up to 3 deployments
Choose plan

Container Pro

$35

$17.5/ mo

Billed monthly.

  • 4 vCPU
  • 4 GB RAM
  • 20 GB NVMe
  • Up to 10 deployments
Choose plan

Want us to set it up with you? Quick setup $49, one-time. Setup packages

On shared infrastructure, CPU, RAM and disk limits are shared by applications within the plan.

Plan prices include tax. Your checkout and invoice show the tax breakdown and any applicable discount.

Exit, support and status: Trust and transparency · Live status page

Migration service

Coming from Vercel, Netlify or Heroku?We'll do the move.

With the Migration package we move up to 3 apps and 1 database (including Supabase or Heroku Postgres) to DeployVera. It is a one-time, optional service, and you can always migrate yourself for free.

  • Quick setup1 app, domain + SSL

    $49one-time · 2 business days

  • MigrationRecommendedUp to 3 apps + 1 database

    $149one-time · 5 business days

  • Agency starter10 client projects + workshop

    $390one-time · 10 business days

Common questions

How do I deploy my app with AI?

DeployVera runs a hosted MCP server (https://mcp.deployvera.com/mcp). Connect Claude, Claude Code, Cursor, VS Code, Codex or any MCP client; the agent lists your projects, deploys them, follows the build and explains a failed build. Rollbacks and deleting environment variables need your approval in the browser. Setup steps: /ai-integration.

Can I deploy my frontend and API separately?

Yes. Each separate application deployment uses an application slot. A separate frontend and API need at least 2 slots. Databases do not use those slots; their own quotas and service resource limits apply.

How do PostgreSQL, MySQL, MongoDB and Redis fit into a plan?

Managed PostgreSQL, MySQL, MongoDB and Redis databases are in beta; you add them from the service screen and they do not consume application deployment slots. Separate database quotas and service resource limits apply; databases are not unlimited. The platform runs scheduled backups, but there is no self-service backup download or restore and no high availability. Redis data is not guaranteed to persist to disk.

How do I deploy from GitHub?

Select your repository and branch, then set the build method, application port and required environment variables. DeployVera builds the image and starts the application. Follow its status, build output and application logs in the panel.

Can I increase resources later?

Self-service upgrades are not available yet. If you need more resources, open a support ticket; no change or charge is applied without your approval.

Ship your code.We will take care of the infrastructure.

Start free