**Lapdev** gives your team production-accurate development environments that run directly in your Kubernetes cluster. Install the lightweight `lapdev-kube-manager`, choose the workloads you care about, and Lapdev keeps isolated or shared environments in sync with your production manifests. Developers iterate quickly using the [Devbox CLI](https://lapdev.gitbook.io/docs/core-concepts/devbox) for local debugging while staying connected to real cluster resources.
## What Lapdev Does
- **Reads production manifests** – Lapdev builds an App Catalog straight from your production Deployments, StatefulSets, ConfigMaps, Secrets, and Services.
- **Creates tailored environments** – Launch fully isolated personal namespaces, shared team baselines, or lightweight branch environments with intelligent traffic routing.
- **Keeps everything in sync** – Monitor production for changes, notify developers, and apply updates when you are ready—no manual YAML drift.
- **Enables local-style iteration** – Devbox routes cluster traffic to your laptop, so you debug locally while remaining wired into in-cluster dependencies.
- **Publishes secure preview URLs** – Share HTTPS endpoints for any service without juggling DNS, certificates, or ingress rules.
## Architecture at a Glance
Lapdev is made of three components that work together:
1. **Lapdev API Server** – SaaS control plane that handles auth, orchestration, and secure tunneling.
2. **Lapdev-Kube-Manager** – In-cluster operator that mirrors production workloads into development namespaces.
3. **Devbox CLI** – Developer tooling for traffic interception and access to cluster services from your local machine.
Dig deeper in the [Architecture docs](https://lapdev.gitbook.io/docs/core-concepts/architecture/).
## Getting Started
1. [Connect your Kubernetes cluster](https://lapdev.gitbook.io/docs/how-to-guides/connect-your-kubernetes-cluster)
2. [Create an App Catalog](https://lapdev.gitbook.io/docs/how-to-guides/create-an-app-catalog)
3. [Provision your first environment](https://lapdev.gitbook.io/docs/how-to-guides/create-lapdev-environment)
4. [Develop locally with Devbox](https://lapdev.gitbook.io/docs/how-to-guides/local-development-with-devbox)
## Resources
- [Traffic routing architecture](https://lapdev.gitbook.io/docs/core-concepts/architecture/traffic-routing-architecture)
- [Branch Environment Architecture](https://lapdev.gitbook.io/docs/core-concepts/architecture/branch-environment-architecture)
- [Preview URLs](https://lapdev.gitbook.io/docs/core-concepts/preview-url)
- [Lapdev Docs](https://lapdev.gitbook.io/docs/)
•Reads production manifests – Lapdev builds an App Catalog straight from your production Deployments, StatefulSets, ConfigMaps, Secrets, and Services.
•Creates tailored environments – Launch fully isolated personal namespaces, shared team baselines, or lightweight branch environments with intelligent traffic routing.
•Keeps everything in sync – Monitor production for changes, notify developers, and apply updates when you are ready—no manual YAML drift.
•Enables local-style iteration – Devbox routes cluster traffic to your laptop, so you debug locally while remaining wired into in-cluster dependencies.
•Publishes secure preview URLs – Share HTTPS endpoints for any service without juggling DNS, certificates, or ingress rules.