Documentation

Development & Staging
without infrastructure worries

Managed Kubernetes. Security by default. Self-service environments. Focus on code, not infrastructure.

terminal
$ pbd env create development
→ Creating Kubernetes cluster... → Configuring network & security... ✓ Environment ready → Kubernetes 1.28 | 2 CPU, 4GB RAM → Kubeconfig: ~/.kube/proxy-dev
$ git push origin main
→ Deploying to development... ✓ Deployment successful → URL: https://dev.your-app.com
$ kubectl get pods
NAME READY STATUS RESTARTS AGE api-7d8f9c6b-xk2p9 2/2 Running 0 45s worker-5f7b8d-9mn4k 1/1 Running 0 45s

The problem

Kubernetes is complex. Security patches, network configuration, SSL certificates. Developers want to deploy, not manage infrastructure. Weeks waiting for a new environment.

Traditional

Setting up Kubernetes cluster takes weeks

Security patches and updates applied manually

Network, firewall, SSL certificates configured manually

Development ≠ staging ≠ production

Team waits for DevOps for every environment change

With Proxy Platform

Managed Kubernetes: everything configured automatically

Security patches applied automatically

SSL, network, firewall: out of the box

Identical environments via Infrastructure as Code

Self-service: developers create environments themselves

GitOps workflow

Push to git = auto-deploy. Infrastructure as Code. Preview per PR.

1. Feature branch

git checkout -b feature/new-api

Create branch → Auto preview environment

→

2. Develop & test

git push → auto-deploy

Live URL per environment

→

3. Merge to main

git merge feature/new-api

Preview environment auto-cleanup

Self-service Environments

Developers create new environments themselves via CLI or dashboard. No tickets, no waiting. Development, staging, production: all configured identically.

terminal 
$ pbd env create staging

→ Creating Kubernetes cluster...
→ Configuring network & security...
✓ Environment ready

Kubernetes 1.28 | 4 CPU, 8GB RAM
URL: https://staging.your-app.com
Kubeconfig: ~/.kube/proxy-staging

In practice

Developer has a new feature and wants to test it on a dedicated environment. Within minutes:

  • New environment created
  • Kubernetes cluster fully configured
  • Security, network, SSL: automatic
  • Deploy via git push

No DevOps team needed. No weeks of waiting. Just do it.

No more surprises

"Works on my machine" is a thing of the past. Development, staging and production run on the same Kubernetes version, same services, same configuration.

The only difference? Resource limits. Development gets 2 CPU, production gets 8.

Production Parity

Identical environments. No config drift. Test with real services: PostgreSQL, Redis, S3, queues.

Same Kubernetes version

Development runs K8s 1.28, production also 1.28. Always.

Real managed services

PostgreSQL, Redis, S3. Not Docker Compose, but real cloud services.

Infrastructure as Code

All configuration in Git. Reproducible. Versionable.

CLI-first & Kubernetes native

Developers work in the terminal. Proxy CLI for platform management. Native kubectl access for your clusters. Dashboard when you need it.

Proxy CLI

Manage clusters, deployments, environments and firewall rules from your terminal.

Native kubectl access

Full kubeconfig access. Use kubectl, helm, or any Kubernetes tools you want.

Dashboard optional

Web UI for overview and monitoring. But deploy the way you're used to: terminal first.

Tools you already know

No need to learn vendor-specific tools. Just the standard Kubernetes tooling:

kubectl
helm
ArgoCD
Flux
k9s
Lens

Plus the Proxy CLI for platform-specific tasks.

Managed Kubernetes

Kubernetes without the complexity. Security patches automatic. Network and SSL out of the box. Focus on your application, not infrastructure.

Automatic security patches

Kubernetes updates and security patches are applied automatically. No downtime.

SSL & network out of the box

SSL certificates, firewalls, load balancing: automatically configured and managed.

Monitoring & alerting

Metrics, logs, alerts: built-in. See immediately what's happening in your cluster.

What you don't have to do

  • ✗ Set up and maintain Kubernetes cluster
  • ✗ Apply security patches manually
  • ✗ Manage SSL certificates
  • ✗ Configure firewalls and networks
  • ✗ Set up monitoring and logging
  • ✗ Plan backups and disaster recovery

We handle the infrastructure. You write code.

Ready to get started?

Sign up for early access and discover how the Proxy Platform gives you cloud freedom. Get first access to the platform with direct support from our team.

Sign up for Early Access

Use your preferred payment method · Cancel anytime