Hi
Starting a blog. A short note on why orkestr exists and what you'll find here.
You know that feeling. You wrote something - a service, an API, a side project that turned into a real product - and now you need it on the internet. So you open AWS, or spin up a VPS, and suddenly you’re neck-deep in Terraform modules, load balancer configs, and IAM policies you don’t fully understand. Four hours later, nothing’s deployed and the bill is going to be €70 a month for something that should cost €4.
That’s the feeling orkestr is built around. And it’s not just a solo developer problem - teams burn entire sprints wiring up infrastructure instead of shipping the thing they’re actually building. Orkestr exists so you don’t have to choose between “simple but limited” and “powerful but now you need a DevOps hire.”
We run everything on Hetzner servers in Germany. Your code gets built in an isolated container and goes live with a real TLS cert. Push to main, it’s live in about twelve seconds. Set up staging environments, get deploy previews on pull requests, hook up a managed Postgres - without writing a single line of infrastructure code.
This blog is where we’ll write about the things we build and the decisions behind them. Why we picked Hetzner over AWS, how the wake-on-request system works, what actually breaks in production, the weird corners of auto-detecting forty different frameworks. Less “content marketing,” more engineering notes I’d have wanted to read before building this.
If any of that sounds useful, stick around. If you spot something wrong, email me (stefan at orkestr dot eu). I read everything.
More soon.