Zerverless helps teams understand, design, visualize, build, and improve serverless systems — directly inside their own AWS account. It's not a platform that runs your code for you; it's the control plane, the AI, and the tooling around your own AWS account.
Three principles drive every technical decision in this organization:
- Customer workloads always live in the customer's own AWS account. Zerverless never runs your code — it reads, analyzes, generates, and guides.
- Zerverless provides the control plane — visibility, analysis, generation, guidance — never the runtime itself.
- Read-only access and deploy/write access are never the same trust level. A product that only looks at your AWS account (like Air) is architecturally distinct from one that could change it.
Zerverless is currently built and maintained by a single person. The project is organized as 13 repositories across 4 categories so that each piece stays independently understandable, even though one person touches all of them.
| Repo | What it is |
|---|---|
| .github | This repo. Public org profile + governance defaults shared across the org. |
| zerverless-infra | Global AWS foundation: DNS, wildcard certificate, WAF, security & observability baseline. Deploys first, before anything else. |
| zerverless-platform | The control plane: Cognito auth, users, organizations, entitlements, quotas, usage tracking, connected AWS accounts. Every product asks this repo whether a user is allowed to do something — no product decides that on its own. |
| zerverless-web | The public marketing site at zerverless.com — landing page, pricing, blog, docs. |
| zerverless-app | The private customer dashboard at app.zerverless.com — organization settings, billing, usage, links into the products. |
| Repo | What it is |
|---|---|
| zerverless-xero | AI product. Turns a prompt into a serverless architecture proposal, explanation, migration plan, and a CDK/ZDK code skeleton. |
| zerverless-hero | AI product. Analyzes an existing serverless system — cost, security, performance, logs — and recommends fixes. |
| zerverless-air | Read-only visualization of the serverless systems already running in a customer's AWS account. Never writes to it. |
| Repo | What it is |
|---|---|
| zdk | Zerverless Development Kit. An opinionated, secure-by-default L3 construct library on top of AWS CDK. Usable by anyone, with zero relationship to Zerverless the company. |
| oz | Open Zerverless. A CLI for discovering, tracing, and explaining what's running in any AWS account — again, usable standalone. |
| Repo | What it is |
|---|---|
| zerverless-sdk | The one typed client every private app uses to talk to zerverless-platform — auth, entitlements, quotas, usage. |
| zerverless-engines | The shared "AWS brain": discovery, costs, logs, tracing, AI context building, architecture generation. Used by Xero, Hero, and Air so none of them reimplement it. |
| zerverless-ui | The shared Cloudscape component library every private dashboard/product renders through. |
This repository controls two things for github.com/zerverless:
- The public organization profile —
profile/README.mdis what renders on the org's GitHub landing page. - Org-wide governance defaults — the
CODE_OF_CONDUCT.md,SECURITY.md,CONTRIBUTING.md, and issue templates in this repo's root apply automatically to any repository in thezerverlessorg that doesn't define its own. This is a real GitHub feature, not just a convention.
This repo has no infrastructure, no product logic, no application code, no billing, and no deployment code. If you're looking for any of that, find the right repo in the table above.
Defined.