Spring Boot
Pyahu reads your Spring Boot service and deploys it the way it expects.
- Framework, build tool, and Java version detected
- Postgres, Kafka, and RabbitMQ picked up from your code
- Config and profiles read from application.properties
The delivery platform for JVM teamsProduction-ready code, from day one.
Production-ready code, from day one.
Quality, security, and observability built into every step.
You write the code; one config file describes the rest, and the Pyahu CLI reads the same file locally and in the cloud. It provisions what your app needs on demand (Postgres, RabbitMQ, Kafka, Zitadel SSO), runs the pipeline, and deploys to as many environments as you want, from staging to production. No pipeline to maintain, no Kubernetes to wire up by hand.
Pyahu Community runs that workflow locally, for free. Pyahu Cloud runs it for you, deploying to our cloud or to your own cluster. Your infra, your choice, no lock-in.
From commit to cluster
- 01DevelopOn your machine, same config as the cloud
- 02Quality and securityOn push: review, fix suggestions, security scans
- 03ProvisionPostgres, RabbitMQ, Kafka, SSO, on demand
- 04DeployTo as many environments as you want, your cluster or ours
Local dev to production/Quality and security built in/Deploys to your cluster
Why Pyahu exists
Give every JVM team the leverage of a platform team, without hiring one.
Pyahu is the platform that understands your Java code. We standardize the whole path from a developer's laptop to production: open-source standards you run locally, and a managed platform that takes over when you're ready to ship, driven by the same CLI from end to end.
From git push to production. No Kubernetes in your face. Quality, security, and observability are part of delivery, not an afterthought.
- From your code to production
- Kubernetes improved, never hidden
- Prod on Pyahu or your own cluster, no lock-in
- Quality, security and observability built in
The problem
Most teams don't need more infrastructure to wire together. They need a delivery system.
Serious JVM teams ship product with ad hoc DevOps and pay for it every sprint. Pyahu standardizes the path from code to running system instead of leaving it to whoever has time.
Local environments drift; every workstation is set up by hand.
Secrets are improvised and CI/CD pipelines stay fragile.
Staging is unreliable and production knowledge lives in a few heads.
Too much platform work falls on too few people.
Bring your own code
Pyahu already understands your code.
Pyahu understands most Spring Boot, Quarkus, and Next.js projects out of the box: it detects your framework, build, config, and the services you depend on. Want a head start? Our certified template ships every piece we use to raise quality, security, and observability. Either way, templates are optional.
Quarkus
Pyahu understands your Quarkus service, from dev mode to native builds.
- Build and image strategy detected
- Dev Services mapped to the same stack
- Env vars read from application.properties
Certified template
Prefer a head start? Pyahu's certified template ships every piece we add to raise quality, security, and observability, with local, staging, and production aligned. Not required, just a strong default.
Certified toolchain
The same tools, pinned, on every machine.
The Pyahu toolchain is a mise config. No Docker image to pull, no rebuilds. Tools are pinned per repo and resolve to the exact same versions for everyone. Stack only the profiles you need.
Basestarship · fzf · zoxide · ripgrep · fd · bat · eza · jq · yq · gh · delta · lazygit · neovim
JavaTemurin 25 · Maven · Gradle
Gogo · golangci-lint · delve · air · ko
Pythonuv · ruff · ipython
Cloud & K8skubectl · k9s · kind · helm · telepresence · terraform · awscli · doctl
AIclaude-code · codex · opencode
Two ways to run Pyahu
Open source for local dev. Production-grade when you ship.
Same services, same flow in both: Postgres, RabbitMQ, Kafka, Redis, SSO, load balancing. Community runs them on a local k3s-in-Docker cluster for development; Cloud runs them production-grade, managed for you.
Open Source
Pyahu Community
Free · local dev
The whole Pyahu workflow on your machine: a k3s-in-Docker (k3d) cluster with Postgres, RabbitMQ, Kafka, Redis, Zitadel SSO, and a load balancer, plus the certified templates and the CLI. Built for development.
- Local cluster: k3s in Docker (k3d), built for development
- Postgres, RabbitMQ, Kafka, Redis, Zitadel SSO, and a load balancer, locally
- Certified Spring Boot and Quarkus templates
- Pyahu CLI and a mise-managed toolchain
Managed Platform
Pyahu Cloud
Managed staging and production
The same project, built, checked, and shipped for you, from git push to production. Production runs on our cloud or on your own Kubernetes cluster, your call, with full kubectl access and no lock-in.
- Production on Pyahu's cloud or your own Kubernetes cluster, your choice, no lock-in
- Understands your Java code: detects Spring Boot / Quarkus and provisions Postgres, RabbitMQ, Kafka, and SSO on demand
- Managed Postgres: daily backups, point-in-time recovery (PITR), and pg_dump restores
- Multi-tenant SSO for your app: Zitadel-as-a-service, no IdP to build
- CI/CD, controlled releases, and one-click rollback
- Observability built in: logs, metrics, and traces
- Managed Redissoon
- Security scanning and quality gatessoon
Community vs Cloud
Same foundation. You decide where it runs.
| Capability | Community | Cloud |
|---|---|---|
| Certified project templates | ||
| Pyahu CLI (one binary) | ||
| Mise-managed toolchain | ||
| Postgres, RabbitMQ, Kafka, Zitadel SSO, load balancer | ||
| Redis | soon | |
| Automatic, on-demand provisioning | ||
| Local k3s-in-Docker cluster (k3d), for dev | ||
| Production-grade, HA infrastructure | ||
| Managed Postgres: backups, PITR, pg_dump restore | ||
| CI/CD, secrets, and one-click rollback | ||
| Observability: logs, metrics, traces | ||
| Security scanning and quality gates | soon | |
| Production on Pyahu or your own cluster, no lock-in |
Get in touch
Want to know more?
Leave your email and we'll get in touch with more about Pyahu Community and Pyahu Cloud.