Introducing Ark: every stack, one click

We are building a local development environment we have wanted for years: install one app, park a folder, and every project inside it is instantly reachable at https://<name>.test with a trusted certificate — running whatever runtime it needs. It is called Ark, and it is in active development.

Why another dev environment?

The tools we admire each stop short somewhere: the polished ones are single-language or single-platform; the polyglot ones lean on Docker and cost you speed, battery, and file-watching sanity. Ark's bet is that developers deserve all three at once: polyglot, native, and tri-platform — PHP, Node, Python, Go, Java, .NET, Ruby and friends, running natively on macOS, Linux, and Windows.

CLI-first, by architecture

Ark is a daemon with two thin clients: a GUI and a CLI. Everything the GUI does goes through the same API the CLI uses, which means team setups and CI can script every bit of it — link a site, install a runtime, start a service, snapshot a database. We use Ark to develop Ark, and our own projects run on it daily.

What's next

We will be writing devlogs here as Ark approaches release — runtime management, the routing and TLS story, services, and team configuration sync. Follow the ark tag on this blog, and get in touch if you want to be an early tester.