Welcome to Orchy!

Hi, I’m Daniel, the creator of Orchy. Let me first start by helping you to pronounce the word. Orchy is pronounced Or-Key. Orchy was created because I believed that there was a place for an orchestrator that had features that rivaled something like kubernetes but was magical and easy for first-time users. I could also see the age of AI taking up the vast majority of business’ cloud compute and we have a lot of “free” compute just laying around in things like company laptops, old pcs, print servers etc etc. The majority of compute needed on the cloud doesn’t need a lot of memory or CPU so to me, there was a space for an orchestrator that made it easy to install on a bunch of devices and get some clustering happening pretty quickly.

It was also important to me that the majority of deployments could happen with just a single command. Today’s modern vibe coders don’t want to have to worry about configuring this and that, they just want to run a single command and have it “work”.

To that end, Orchy is a vibe-coded orchestrator. I’m a Senior developer, I’ve had the AI follow stringent coding best practices and as is typical it hasn’t followed it half the time. However it’s helped me to to get 90% of the way there and I aim to work with the open-source community to make this something incredibly scalable that all sorts of applications can be put on.

Let’s highlight a couple of in-built features of Orchy that I absolutely love:

Orchy automatically schedules things across the devices you give it. It checks things like uptime and device type to determine where is best
Orchy can ideally deploy anything by just running orchy deploy and it works out sane defaults for you!
Orchy has an in-built replicated volume storage on top of which we’ve built an s3 compatibility layer AND on top of that a materialized-view style key-value db.
Orchy has an in-built pipeline runner to allow you to run and schedule jobs across your orchy

There’s a bunch of cool tech behind the scenes too like built-in ntp time sync etc. which I can’t wait for the more technical among the community to discover.

Guess what? This website, the release pipeline is all being hosted on my personal orchy.

Here’s to more!

Dan H.