ZCP

zerops

Zerops Platform, the developer-first cloud made to run the whole development lifecycle, from remote development to highly available production, the same infrastructure at every stage. No more “but it works on my machine”.

Up to $65 credits

Zerops Mate. Hire an AI engineer that ships, not just codes. A team for a solo founder or developer, extra hands for a team, an engineer of their own for designers and project managers, the whole agency for a business. It comes back working, live when you say so.

Soon

Zerops Box, a real VM for every agent your product runs. Persistent, with SSH and Docker inside, fork or snapshot in seconds, any size up to the whole machine. Beside it, Postgres, a queue, storage and hosting, one bill.

Soon

We built Zerops from the ground up, on our own hardware, to cover an app’s whole lifecycle, from the first dev environment to production. It is made of six building blocks that fit together any way an app needs. Platform, Mate and Box are three faces of the same engine.

Compute

A full Linux system with root, SSH and cron, or any Docker image in its own VM, on AMD EPYC, NVMe and ECC RAM. Nothing abstracted past where you can debug it. Soon, sandboxes to fork and snapshot.

Private network

db:5432 api:3000 zcli vpn up

One per environment, your laptop on it over VPN. Every one built from one definition gets the same hostnames, so the app’s wiring never changes.

Managed services

Credentials injected, backups, scaling, object storage beside them. HA is a toggle, not a tier.

Environments

API CLI SDK MCP

Any number from one definition, made and unmade by any of these, the same infrastructure under every one. Each one costs only while it runs.

Pipeline

zcli push build deploy live

One zerops.yaml, one build system for the artifact and the runtime image, soon the sandbox images too. Every environment, built the same way. Zero-downtime deploys, ten versions kept, rollback is a switch.

Production

Runtimes, databases and storage run HA on either core, and on the Serious core the balancers do too. Logs, metrics, encrypted backups, none of them behind a tier. Access set per environment, no token outranks its maker.

Platform, for developers who run production and want every engineer and every coding agent working on the same thing.

LikeFlyRailwayRender

Mate, for whoever needs an engineer. The ones who know what needs shipping and can’t ship it themselves, and the teams with more to ship than hands.

LikeDevinAmpJules

Box, for the ones building products that run agents, or any code they can’t trust, per user, per task, per session.

LikeE2BDaytonaModalbox.ascii.dev

The same engine under all three, so you can switch any time. Platform and Mate can both use Box.

All three at work on one app. Platform runs every environment, Mate has one of its own, Box is a VM in each of them, and a pull request is what carries a change to production.

Claude Code

db

cache

queue

storage

box

appdev

appstage

Their own environment, built from production’s definition; their agent proves each change on appstage before the pull request.

Mate

db

cache

queue

storage

box

appdev

appstage

The same, for the engineer you hired. One pull request at a time.

app

db

cache

queue

storage

box

Where a pull request is proven before anyone approves it: built the production way, on its own data.

app

db

cache

queue

storage

box

More than one container of everything. Who may release is a role you set.

GitHub,Giteaorany git

• CI checksany CI
• Reviewoptional
• Approvala person

Four ways to use Zerops. As the whole team for a solo founder or developer, as the one place a team builds and runs its product, as an engineer of their own for designers and project managers, as every client’s production on one account for a business.

Mate the appyou say yes prodHA

A solo founder or developer. Production runs on Zerops from day one, and Mate is the rest of the team: it builds the first version with you, and every change after that is tried exactly as it will run before you say yes.

johnd mateone gate prodHA

A team with a product in production. Production on Zerops, no agent in it. Every engineer and every coding agent in an environment built from its definition, Mate hired into one of its own, every pull request through the same gate. More to ship: hire another.

“Move the checkout above the fold” Mate stage · open it the team says yes prodHA

Designers and project managers, with an engineer of their own. Ask Mate in your own words. It comes back running on a page you can open, and goes live on Zerops once the team has said yes.

the client asks pull request the studio says yes prod×10HA

A business with many apps. A studio building web shops runs each client’s shop on Zerops: production on its own, no agent in it, the studio’s developers and their coding agents in environments built like it. A client’s small changes go to Mate and come back as a pull request the studio reviews. Ten clients, ten productions, one account. One bill, metered, no seats.