ZevCore Primitives
Every Zev product, and eventually anything you build on our infrastructure, is assembled from these building blocks. Learn these names; they're how the whole platform is described.
ZevCloud is the door
The product you actually interact with: the console, the dashboard, the fully-managed experience. When you deploy today, you do it through ZevCloud, and it handles everything for you.
ZevCore is the engine
The infrastructure foundation everything runs on. Mostly internal today, reached through ZevCloud. Later we'll unlock it directly for people who want to build their own platforms on our metal.
The managed advantage: anything we run for you has no single point of failure. Your ZevPod runs across multiple nodes; your ZevDB replicates with failover. Resilience is built in, not something you engineer yourself.
Compute
Where your code and applications actually run.
ZevPod
"Just run my app."
A lightweight container that runs a single application. We run multiple replicas across more than one node, so one failure never takes you down.
ZevBox
"Give me a server."
A standard virtual server with an OS and full SSH access. Install packages, run several services, configure it your way.
ZevCell
"Give me a whole computer."
A fully isolated virtual machine with its own kernel. The strongest isolation boundary, for untrusted code or regulated workloads.
ZevBurst
"Run this once, then disappear."
Ephemeral compute that spins up, does a job (a build, a CI run, a batch), and burns out. You pay only for the seconds it runs.
Storage
Where your files, volumes, secrets, and backups are kept.
ZevStorage
"Buckets of files I can read and write anywhere."
S3-compatible object storage. Files in buckets, accessible by standard S3 tooling, kept resilient with no single point of failure.
ZevDisk
"A hard drive attached to my app."
Block storage. Persistent volumes you attach to your compute, for data directories, app state, anything that must survive restarts.
ZevVault
"A safe for my secrets."
Encrypted storage for API keys, passwords, and tokens, injected safely into your apps at runtime instead of hard-coded.
ZevBackup
"Save points I can roll back to."
Snapshot and restore. Point-in-time copies of your data on a schedule, so you can recover if something goes wrong.
Data
Where structured, relational data lives.
ZevDB
"A database that runs itself."
Managed databases (Postgres, MySQL, Redis) run with replication and failover. You get a connection string; we handle the rest.
Network
How your services connect and how the world reaches them.
ZevEdge
"Fast delivery, everywhere."
CDN and edge delivery. Your content served close to users worldwide, not just near where your server lives.
ZevMesh
"A private network across all our machines."
Internal node-to-node networking. The secure private layer connecting machines across the fleet, including across regions.
ZevRoute
"Send each request to the right place."
Load balancing and traffic routing. Distributes requests across instances and routes by domain, making many servers look like one.
Your whole stack, in primitives
Take one ordinary web app. Every part of running it maps to a primitive you now know, each one fully managed for you through ZevCloud.
Learn to put this together in the Cloud Engineering track.