Lapdev - Kubernetes Development Environments
How Lapdev works
Your cluster is the source of truth and Lapdev does the rest
Lapdev treats your Kubernetes cluster as the source of truth. We read the workloads you already run, assemble App Catalogs, and keep every environment in sync with the manifests you ship to production.
1
Connect your Kubernetes cluster
Install the lightweight lapdev-kube-manager deployment. It opens an outbound TLS tunnel to Lapdev, so no need to open port on firewall to your cluster.
2
Create an App Catalog
Select the workloads that make up your application. Lapdev automatically pulls the related ConfigMaps, Secrets, and Services into an App Catalog blueprint.
3
Launch environments instantly
Spin up personal namespaces, shared team baselines, or cost-efficient branch environments. Lapdev keeps them in sync and highlights when production manifests change.
4
Iterate with Devbox & preview URLs
Use Devbox to intercept traffic to localhost, attach your IDE, and ship faster. Share production-grade preview URLs with PMs, QA, or stakeholders in a click.
Core capabilities
Everything your platform team needs to empower developers
Lapdev brings environment orchestration, traffic routing, and local debugging together to offer developer ergonomics without bespoke scripts.
App Catalogs
Define your application once by reading the workloads already running in production or staging. Catalogs eliminate YAML drift and power every environment Lapdev creates.
Environment models
Give every developer a personal namespace, maintain shared baselines, or branch only the services you modify. Lapdev automates the routing and sync for each workflow.
Devbox local debugging
Run services locally while staying connected to in cluster dependencies. Devbox handles the secure tunnel and header propagation so your IDE sees the same traffic your pods would.
Preview URLs
Expose any service through secure, auto-managed HTTPS endpoints. Lapdev provisions DNS, TLS, and access control so you can share in-progress features instantly.
Branch environments
Route traffic per developer without running 100 copies of every service
Lapdev’s branch environments reuse a shared baseline and only duplicate the services you change. Our sidecar proxy routes requests using OpenTelemetry tracestate headers, so each developer sees their own version end to end.
- • Up to 88% infrastructure reduction versus full clone environments
- • Keep databases, queues, and caches shared while isolating HTTP services
- • Sync with production manifests when you are ready no surprise restarts
Designed for platform efficiency
Lapdev automatically:
- • Monitors your source namespace for manifest changes
- • Alerts developers when new versions are available
- • Handles TLS tunnels between your cluster, Lapdev, and Devbox clients
- • Provides auditability across clusters, catalogs, and environments
Bring Kubernetes developer environments to your team
Connect your cluster in minutes and give every developer a production-aligned environment. Free during beta.