What Is Lapdev? Kubernetes Development Environments from Existing Manifests

Updated

Lapdev is a Kubernetes development environment platform that turns the manifests you already run into production-aligned environments for every developer. Instead of writing new YAML, you point Lapdev at your cluster; it reads your running workloads, builds an App Catalog, and spins up personal namespaces, shared team baselines, or branch environments that stay in sync with what you ship to production. It is aimed at platform teams who want to give developers realistic environments without maintaining bespoke scripts.

How Lapdev works

Lapdev treats your Kubernetes cluster as the source of truth. The workflow has four steps:

  1. Connect your Kubernetes cluster. Install the lightweight lapdev-kube-manager deployment. It opens an outbound TLS tunnel to Lapdev, so you don't need to open a port on your firewall to the 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 and preview URLs. Use Devbox to intercept traffic to localhost, attach your IDE, and share production-grade preview URLs with PMs, QA, or stakeholders.

Core capabilities

App Catalogs

Define your application once by reading the workloads already running in production or staging. Catalogs are designed to 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.

Traffic routing per developer

Lapdev routes traffic per developer without running 100 copies of every service — useful when a full application has many services but a developer only needs to change one.

Devbox and preview URLs

Devbox intercepts traffic to localhost so you can attach your IDE and debug locally, while preview URLs let you share a running environment with non-engineers in a click.

Who it's for

Lapdev fits teams that already run Kubernetes and want developer environments that mirror production without duplicating every service per developer. Platform teams get environment orchestration, traffic routing, and local debugging in one place rather than through custom scripts.

If your team doesn't run Kubernetes, or you're looking for a hosted preview service that doesn't read your existing cluster, Lapdev's model — cluster as source of truth — won't match your setup.

Availability and pricing

Lapdev is in public beta. A pricing page exists at lap.dev/pricing/, but the available material doesn't specify plan details or costs, so check that page directly for current terms. The docs and dashboard are linked from the site for setup and team management.