Lapdev keeps teams productive while they ship Kubernetes apps.
We started with Lapce, a code editor designed around remote development from its first commit, and built our own GUI toolkit Floem when nothing in Rust worked well. Those projects taught us how much smoother development workflows become.
As we embedded with teams running sizeable microservices deployed on Kubernetes, we saw the same loop play out: developers waited on namespace setup, 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 help developers move faster, without forcing teams to rework the platforms they already trust.
In practice, that means:
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.
Lapdev works with what you already run in production, not around it.
Fast iteration and shared visibility are inseparable; our tooling keeps the whole team moving.
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 App Catalogs and environment configurations, and incorporating feedback into the platform. The goal is a lasting practice where developers can ship without waiting and platform teams trust the tooling.
We are the maintainers behind Lapce and Floem, open source projects trusted by thousands of developers. We are bringing that same focus on developer ergonomics to Kubernetes environments.
Kubernetes Dev Env
The Code Editor
The GUI Toolkit