Megh Vyas
Backend · Infra · SRE
← All work

Deployment platform

Zyphron

Push a repo, get a running distributed system. No Dockerfile, no manifests, no infrastructure to hand-write.

Year
2026
Role
Founder, full build
Built with
Fastify, Prisma, Postgres, Redis, Kafka, Next.js, Docker, Helm

// the wall

Every deployment platform stops at the same wall. It can build your code, but you still have to tell it what infrastructure the code needs, which service talks to which, and in what order they start. That specification, the Dockerfiles, the compose files, the IaC, is exactly where multi-service apps go to die, and it is work that has nothing to do with the product.

the build

  1. 01$

    Built the control plane on Fastify with a dedicated worker tier, Prisma over Postgres for durable state, and Redis plus optional Kafka driving the async build-and-deploy pipeline.

  2. 02$

    Detected each service, its runtime, and its dependencies from the repository, then generated the container builds and wired internal networking, secrets, and boot order automatically.

  3. 03$

    Exposed the same API through a Next.js dashboard and a TypeScript CLI (zyphron / zy), so deploy, status, logs, rollback, and stress-test all work from either surface.

  4. 04$

    Shipped the operations real systems need: rolling, blue-green, and canary strategies, per-branch preview environments, and chaos and stress endpoints to prove resilience.

  5. 05$

    Baked in observability from day one with Traefik, Prometheus, Grafana, and Loki, and packaged the whole thing for Docker Compose in dev and Helm on Kubernetes in production.

what shipped

One command turns a Git repository into a live, multi-service stack with routing, metrics, and logs already attached. The infrastructure specification step, the part everyone dreads, simply stops existing.

0

command to full stack

0

API route groups

0

deploy strategies

in the box

  • >

    23 API route groups: deployments, services, env, databases, domains, strategies, edge, observability, chaos, db-branching, self-deploy, teams, audit, and more

  • >

    Deployment strategies: rolling, blue-green, canary

  • >

    Per-branch preview environments and database branching

  • >

    Traefik + Prometheus + Grafana + Loki, wired by default

  • >

    CLI verbs: auth, deploy, status, logs, rollback, stress

  • >

    Docker Compose for dev, Helm chart for Kubernetes