Cloud that respects developers — human and AI.
Full Linux containers, managed services, a dedicated
private network — from remote / agent environments
to highly-available prod, nothing changes but scale.
Curated examples, starter kits, and production-ready open source. Each recipe covers the full lifecycle from local dev through staging to production, with guides on seeding, migrations, backups, and scaling.
Vertical and horizontal autoscaling with granular steps. Lowest price per resource amongst popular PaaS platforms. Up to $65 free credit, no CC needed. No feature tiers, no fees for seats, minute-based pricing.
infrastructure
core with routing
and balancing
with system containers
Up to 50 containers for runtime services. HA / non-HA modes for managed services.
Standard tools. Full access. No magic. SSH, YAML, cron, apt-get, hostname:port — everything works the way you already know. Managed and scalable, but never abstracted beyond recognition.
Container efficiency.
VM-level access.
Other platforms give you a process.
Zerops gives you a machine.
Application containers run a process in a minimal filesystem — fast and efficient, but no SSH, no runtime package management, and multiple processes means fighting the single-process model. Full VMs give you everything but add kernel overhead, slow startup, and operational burden. System containers share the host kernel — container-fast startup, container-level density — but run a full Linux userspace. The access of a dedicated server. The efficiency of containers.
Same services. Same networking.
Same pipeline. Different scale.
Your dev environment is lying to you.
SQLite locally, Postgres in production. No cache in dev, Redis in prod. Docker Compose approximations that don't fail the way real services do. Code works here, breaks there — not because the logic is wrong, but because the infrastructure is different. AI coding agents make this worse: they write against whatever they can access. Give an agent SQLite, it produces queries that break on Postgres.
Each Zerops project is a complete environment — managed services, private networking, deploy pipeline, observability. Dev, staging, production, and preview environments run identical infrastructure. Resources are the only variable.
Databases, caches, queues, storage —
managed means managed.
Zerops handles backups, failover, and recovery.
Not just installation.
PostgreSQL, MariaDB, Valkey, KeyDB, Elasticsearch, Meilisearch, Typesense, Qdrant, ClickHouse, Kafka, NATS, S3-compatible object storage, and shared POSIX storage. All on the project's private network, all reachable by hostname. Zerops runs on its own bare-metal infrastructure — no cloud provider margin underneath.
One YAML. Zero-downtime deploys.
10-version rollback.
Push code. Zerops builds, deploys, and swaps containers
without dropping requests.
zerops.yaml defines build, deploy, and runtime. Push via GitHub, GitLab, zcli push, or GUI. Zerops spins up a temporary build container (up to 5 CPU, 8 GB RAM, 100 GB disk), runs your commands, deploys artifacts, and swaps containers with zero downtime. Build resources are included in your project core.
Push code via GitHub, GitLab, or zcli push
Build container created from build.base
build.prepareCommands modify the base image
build.buildCommands are executed, artifacts from build.deployFiles are saved
Container from run.base customized via run.prepareCommands
New containers go live. Once deploy.readinessCheck passes, old containers swap out — zero downtime
Private by default.
Independent once running.
Every project gets its own network, balancer, and firewall. Once deployed, it runs without us.
Each project gets a separate VXLAN network with dedicated L3 and L7 load balancers, firewall, and internal DNS. Services find each other by hostname — db:5432, cache:6379, api:3000. Standard hostname resolution, no proprietary SDKs, no service mesh. Connection strings don't change between environments. After deployment, your project operates independently from the Zerops control plane — a control plane issue does not affect running production.
infrastructure
core with routing
and balancing
with system containers
When something breaks,
you connect and look.
The platform does not stand between you
and your infrastructure.
with system containers
on Zerops
Every project includes its own logger and statistics services. Logs are collected via syslog-ng — not files you tail, but a structured pipeline you control. Forward to self-hosted ELK running on Zerops, to Better Stack, to any syslog-compatible target. When something goes wrong, you have the access you'd have on your own machine: VPN into the project network, SSH into the container, inspect process state, trace the problem.
Zerops is a spin-off of vshosting.eu, building on top of 20 years of experience with managed hosting. Development started in 2020 with official launch in 2024. Using bare metal and built every layer from ground up to create the ideal mix of flexibility, developer experience, and scalability.
What are we up to
The perfect cloud platform for development and production of RAG / AI apps
Zerops is a cloud platform built on four core principles - developer experience, flexibility, scalability and of course, affordability. These principles along with the platform design of Zerops make for the ideal platform for the whole lifecycle of developing and operating production of RAG / AI apps.
AlešQuarterly Zerops update — wildcard domains, CDN, external access to DBs, RAM granularity and more
Tackling some long standing issues, flexibility and stability improvements and first steps towards making Zerops global
AlešIn 2024 we re-launched and shipped hard, what's in store for 2025?
In the middle of 2024 we re-launched Zerops under the new ownership and worked hard to increase the flexibility and developer experience. Let's recap and look at our plans for 2025
Aleš