one cloud.
every server you own.
add any linux machine in one command, then run containers, vms, databases and models across the lot. no public ips, vpns or firewall rules. the cloud workflow, on hardware that stays yours.
- open beta / free to use
- no card required
- amd64 + arm64
good hardware should not be idle while the cloud bill grows.
most teams own more computing than they use. the workstation with the big gpu. the servers in the office that outlived their project. the machine at home that runs a nas and not much else. using any of it the way you use a cloud means public addresses, vpns, port forwards and a weekend of setup for every box. so it sits there, and the cloud bill keeps growing.
odalr is the layer that makes those machines behave like one cloud. you add each one with a single command, and from then on you deploy to the fleet, not to a server.
three steps, and the first two happen once.
- 01 step / 01
Create a fleet
Sign up and give your fleet a name. It gets its own console, and it is empty for about a minute.
acme.odalr.com machines 0 add a machine -> - 02 step / 02
Add your machines
Copy one command from the console and run it on each machine. Office, home, colocation, behind any router: nothing to open, nothing to forward.
$ curl -fsSL https://acme.odalr.com/install.sh | sudo sh -s -- odalr_join_... > office-1 joined the fleet - 03 step / 03
Deploy
Get the odalr command — one line, macOS or Linux, no root. Then say what you want to run: odalr picks a machine with room, keeps it running, and puts it on the internet with HTTPS when you ask.
$ curl -fsSL https://odalr.com/cli.sh | sh $ odalr run web --image ghcr.io/acme/web $ odalr expose web:8080 > https://web.acme.run.odalr.com
the convenience of a cloud, on machines you control.
- 01
Reach every machine, wherever it is
The box at home is as usable as the one in the rack. Your machines talk to each other over an encrypted private network that works through any router, so you never touch a firewall, a VPN or a public IP again.
- 02
Deploy to the fleet, not to a server
You say what to run; odalr picks a machine with room, installs what it needs and keeps it running. Add a machine and it gets used. Take one out and the work on it moves.
- 03
On the internet in one step
Anything you run can have a public address with HTTPS, or your own domain with a single DNS record. Share a preview, host the company site, ship the product. No reverse proxy to babysit.
- 04
Everything you expect from a cloud
Containers, virtual machines, functions, managed databases, object storage, queues, Kubernetes clusters and GPU-backed models. All of it on your own hardware, all of it from one console.
- 05
Your data never leaves your hardware
Your applications, disks and files live on your machines and nowhere else. We coordinate; we do not hold your data. Leave whenever you like and everything is still on your disks.
- 06
It keeps running
What crashes is restarted. Disks can be mirrored across two machines and backed up to a third. Updates arrive on their own without interrupting anything, and roll back if something is wrong.
bring the stack you already run.
images, manifests, clients and runbooks keep their familiar interfaces. odalr changes where the work lands, not how your team ships it.
- 01
ship
deploy the artifacts your team already produces.
- 02
connect
your applications keep using the protocols they already speak.
- 03
operate
automation, access and observability come with the workload.
anyone with hardware and something to run on it.
-
A team with a rack
Turn the servers in the office into staging and production, with the same deploy flow you would have on a cloud.
-
A lab with GPUs
Serve a model from the workstation under the desk at an OpenAI-compatible URL the whole team can use.
-
An agency
Host client sites on hardware you control, each with its own domain and certificate, all from one console.
-
A home lab
Run your own services at home and reach them from anywhere, without opening a single port on your router.
we run the coordination. you run everything else.
managed where that saves you work, yours where it matters.
odalr runs
- the console and the api
- choosing which machine runs what
- connecting your machines to each other
- dns and certificates for your public addresses
- updates, delivered without downtime
your machines run
- your applications and virtual machines
- your databases, disks and files
- your object storage and container images
- your kubernetes clusters
- your models, on your gpus
free while in beta.
open sign-up, no limits and no card. the machines are yours, so there is nothing to meter but our own work. pricing for that will be announced well before anything is charged, and you will hear it from us first.
before you sign up.
What machines can I add?
Any Linux machine you can run a command on: a server, a workstation, a mini PC, or a VM at another provider. Intel, AMD and ARM all work. It does not need a public IP or any network setup.
Do I need to open ports or set up a VPN?
No. Each machine connects out to odalr, and your machines reach each other over an encrypted private network that works through any router. Visitors to your public sites reach them without you opening anything.
Where does my data live?
On your machines. odalr keeps the description of your fleet: what should run, where, and with which settings. Your applications, disks, databases and files are on your hardware only.
What happens if odalr is unavailable?
Your machines keep running whatever they were running. You cannot make changes until we are back, and traffic to public addresses passes through odalr today, so those would be unreachable in the meantime.
Can I use my own domain?
Yes. Add one DNS record to prove it is yours, and odalr issues and renews the certificates for it.
Is it secure?
Traffic between your machines, and between them and odalr, is encrypted end to end. Secrets are stored sealed and only opened on the machine that needs them. Every person and API key acts under a role you define.
How do I get the odalr command?
One line: curl -fsSL https://odalr.com/cli.sh | sh. macOS and Linux, Intel and ARM, and it does not need root or a package manager. It updates itself when you ask it to, with odalr upgrade — never on its own, and never in the middle of something you are running.
Can I leave?
Any time. Nothing you deploy is stored with us, so removing a machine from a fleet leaves everything on it in place.
put your hardware to work.
create a fleet, add a machine, deploy something. it takes less time than reading this page did.