Building in public

Dev tools for people who ship.

Catmocha has no products yet. That is deliberate. The first one is dev machines as a service: production-like environments in seconds, deleted when the work is done.

Products shipped
0 — yet
First up
dev machines
machinesConcept preview
api-7f3a4 vCPU · 16 GBready in 3.8s
web-2c912 vCPU · 8 GBready in 3.1s
old-laptopfan noises · full diskretired

Opinionated about

  • Linux
  • Containers
  • SSH
  • TypeScript
  • Rust
  • MCP
  • Agents
Products

Coming soon. One thing at a time.

No launch theater. This is what comes first, what is being explored, and what has no name yet.

Coming soon
Dev machines
Dev machines as a service. Your repo and tools preloaded, ready in seconds, deleted when the work is done.
Exploring
Team environments
Shared, reproducible workspaces, so works-on-my-machine covers the whole team.
Later
Whatever earns it
We work in small slices. The second thing gets a name when the first thing ships.
Manifesto

Your laptop shouldn't be the build farm.

Most dev tools ask for too much before they give anything back. And most dev machines are worse: underpowered laptops running production-shaped workloads, or cloud setups that take a week of YAML before the first green build.

We think it should work the other way around: a production-like environment in seconds, with your repo and tools already there. You get something useful before you configure anything.

Catmocha is still pre-product. That's the honest version, and we'd rather say it plainly than dress up a roadmap as a launch.

When we ship, it will be one small thing that does its whole job. Environments that feel local and go away when the work ends.

Principles

How we decide what to build.

Four filters every idea has to pass before it gets a single line of code.

Ephemeral by default
Machines that live for the task. Ready in seconds, deleted on merge.
Feels local
Your editor, your dotfiles, your muscle memory. The network in between is our problem, not yours.
No lock-in
Standard images, standard protocols. Export your environment and walk away whenever you want.
Composable, not monolithic
API-driven pieces that script into the workflow you already have.