Lapdev keep teams in flow while they ship Kubernetes apps.
We started our dev tools journey with Lapce, a code editor designed around remote development from its first commit, and built our own GUI toolkit Floem when nothing in Rust works well. Those projects taught us how much smoother workflows become when you remove friction.
As we embedded with teams running sizeable microservices deployed on Kubernetes, we saw the same loop play out: developers waited on namespace plumbing, ops teams maintained copies of manifests, and the feedback cycle stretched from minutes to days.
Lapdev exists so that shipping on Kubernetes feels as natural as working locally. Our mission is to turn production truth into developer momentum, without forcing teams to rework the platforms they already trust.
That mission shows up in a few promises we make to every team we work with:
We still ship open-source tools, still obsess about interface polish, and still believe the best dev tools come from building alongside the people who use them daily.
We respect the systems teams already run. Lapdev amplifies production practices instead of replacing them with tool-specific workflows.
Fast iteration and shared trust are inseparable; our tooling keeps engineers moving quickly without sacrificing security.
From Lapce to Floem, we build in the open because shared knowledge and community feedback lead to better developer tools.
We stay close after launch, tuning workspace templates, and incorporating feedback into the platform. The goal is a long term practice where developers feel empowered and operations trusts the tooling.
If that sounds like the way your team wants to build, we would love to talk.
We are the maintainers behind Lapce and Floem—open-source projects trusted by thousands of developers—and we are bringing that focus on developer ergonomics to Kubernetes environments.
Kubernetes Dev Env
The Code Editor
The GUI Toolkit