Deploy to a server you own.

ox is a deployment platform: you connect a GitHub repo and ox deploys it to your own Ubuntu server with systemd and Caddy, no Docker. Your app gets a web address with HTTPS, a database if it needs one and daily backups, and every push goes live.

In beta, and our own apps run on it. Free for your first project.

my-server 4 GB, Hetzner Online

Memory used1.5 of 4 GB

my-appmyapp.com
UpdatingLive
blogblog.myapp.com
Live
my-app-stagingTest copy
Live

my-appYou pushed to main

Checked your settings1s
Built your code38s
Updated the database2s
Started the new version next to the old one3s
Switched over, 0 visitors dropped1s
Live at myapp.comDone

Works with the code you already have

Next.js
React
Nuxt
SvelteKit
Astro
Vite
Node.js
Express
Hono
NestJS
Bun
TypeScript
Yarn
Python
Django
FastAPI
Flask
uv
Go
Rust
PHP
Static sites
Postgres
Redis
Qdrant
Neo4j
Hugging Face

One server can run all your apps.

Hosting sites bill by seat, by service or by usage, so a few small projects can add up. One cheap server runs them all. The hard part was always the setup, and ox does the setup.

3 small apps with ox

Your server$5–24
ox Pro$10
Database and cacheIncluded
Background jobsIncluded
Test copies, backupsIncluded

Each month$15–34

Rough prices for small apps. Yours will be different. With one app, ox is free.

The server work, done for you.

ox handles builds, HTTPS, databases, restarts and daily backups for every project.

See all features

~/my-app $ git push

New version live in 41 seconds

Get this app ready for ox.

Reading package.json, prisma/schema.prisma, .env.example

# ox.toml
domains = ["myapp.com"]
[services]
postgres = {}
[cron]
emails = { schedule = "@daily", run = "npm run emails" }

Done. Before you deploy, add STRIPE_KEY in ox.

Live in three steps.

After that, you just push.

Step 1Sign in with GitHub

Your first sign-in creates your account. There's no password to remember.
Step 2Paste one command on your server

Rent a fresh Ubuntu server, from about $5 a month. The command ox gives you locks it down and sets it up, so you won't need to log in to it again.
curl -fsSL https://deploywithox.com/install/… \ | sudo bash
Step 3Pick a repo and press Deploy

ox reads your code and shows what it will run before anything starts. From then on, every push goes live.

Let your AI write the setup.

A simple app needs no setup. A bigger one, with background workers, scheduled jobs, saved files or a build ox can't guess, needs a short ox.toml. Copy our guide into your coding AI. It reads your code and writes that file. ox checks it before every deploy, so a mistake stops the update before your live site is touched.

Download SKILL.md

Works with Claude Code, Cursor, Codex, Copilot, Windsurf and any AI that can read your files.

ox.tomlWritten by your AI

# a Django app with a worker and a nightly job
domains = ["myapp.com"]

[app]
health = "/healthz"

[workers]
worker = "celery -A app worker"

[cron]
digest = { schedule = "@daily", run = "python manage.py digest" }

[services]
postgres = {}
redis    = {}

TerminalYour AI can deploy too

# once: approve it in your browser
$ ox login
# deploy and wait for the result
$ ox deploy myapp --wait --json

Already set up for you.

Things you'd normally wire up yourself, or pay extra for.

HTTPS on every web addressIt turns on by itself and renews by itself.
Databases, ready to usePostgres and Redis, plus Qdrant and Neo4j for AI apps. The connection details just show up.
Background jobs and timersRun a worker all day, or a task every night.
Apps kept apartEach app runs on its own and can't read the others' files. A memory limit stops one busy app from slowing the rest.
Errors in plain wordsIf something's wrong, ox stops before touching your live app and tells you how to fix it.
Live logsWatch your app, your jobs and every update as they happen.
AI models, downloaded for youList a Hugging Face model and it's on the server when your app starts.
No DockerYour app runs straight on the server. Nothing extra to learn or fix.

How ox compares.

You get the ease of a hosting site like Heroku, Vercel or Render and pay for a plain server, plus $10 a month for ox Pro once you run more than one project.

ox compared with running a server on your own
Question	A server on your own	ox on your server
3 small apps, each month	$5–24	$15–34
Time to put an app online	A weekend, if it goes well	Minutes
Site stays up while it updates	Only if you build it	Yes
Daily database backups	You write the script	Included
Test copy for each branch	Hard to set up	Included
You own the server and data	Yes	Yes

Tested on real servers before every release.

We rent brand-new servers, deploy an app in every supported stack, and put apps through updates, failed builds, backups and reboots. Here is our latest full run.

We moved our own apps, databases and all, onto ox using only its dashboard. Nobody had to log in to the server.

Saurav Sharma, builds ox. Lazy Planner runs on ox.

Release test run 14 Oct 2026, fresh 4 GB servers

36 of 36stacks went live

No visitors dropped during an update
A failed build leaves the live app running
The ox agent uses 40 MB of memory or less on an idle server
Removing ox leaves only its security setup and swap file, checked file by file

Run 20261014-084728-1506, commit 09daaef1

Popular open-source apps, deployed and checked on a real server.

ox deployed each app from a pinned commit on a fresh server, then redeployed it and rebooted the server. A separate test agent, one that did not write the config, then used the app.

85 apps, each with the ox.toml that passed

Read the app guides

Free for one project. $10 a month for all of them.

Every feature is in both plans. The only difference is how many projects you run. Your server is billed by your cloud company, as it would be anyway.

Free

$0forever

Your first project, with every feature. No card needed.

1 project
Its staging copy and branch previews don't count

Start free

ox Pro

$10a month, or $80 a year

Every project you have, on every server you connect.

No limit on projects

Start free

Upgrade from Settings when you need a second project.

Every plan includes

Push to deploy, with no downtime
HTTPS that renews by itself
The services your app declares, set up and connected for you
Daily backups of your services' data, and restore
A staging copy, and branch previews when you turn them on (3 at once by default)
Background jobs and nightly tasks
Live logs and plain-words errors
Alerts, uptime checks and webhooks
Undo to a recent version: ox keeps the last 3
The CLI and the AI setup guide

You pay your cloud company for the server, from about $5 a month, and ox $10 a month, or $80 a year (4 months free). No seats, build minutes or bandwidth fees.
ox emails you 4 days before each renewal. Cancel any time and keep ox Pro to the end of the month or year you paid for.
If you leave ox Pro, your apps keep running, but ox stops deploying, backing up and watching all but your free project. If a payment fails, deploys stop at once and the rest stops 7 days later, unless your card goes through.
Prices are in US dollars. Tax is added at checkout where the law asks.

Coming next.

None of these are ready yet.

ox writes the setup for youRight in the dashboard, with no AI tool needed. You check it before anything runs.
A home for AI agents and botsRun them all day, with a log for every task they do.
Invite your teamLet others help run your apps.

Questions.

Will my app work on ox?

ox runs JavaScript and TypeScript (Node.js, Bun, Deno), Python (Django, FastAPI, Flask), Go, Rust, PHP (Laravel, Symfony), Ruby on Rails, Java (Spring Boot, Quarkus), .NET, Elixir (Phoenix) and static sites. It reads your project files to pick the versions and shows you the plan before anything runs. The stack guides show each one deployed on a real server.

How much does ox cost?

Free for one project, with every feature and no card. ox Pro is $10 a month, or $80 a year (4 months free), for every project, on every server you connect. A project's staging copy and previews don't count. You pay your cloud company for the server, as you would anyway, and there are no seats, build minutes or bandwidth fees. ox emails you 4 days before each renewal. Cancel any time and keep ox Pro to the end of the month or year you paid for. If you leave ox Pro, your apps keep running, and ox keeps deploying, backing up and watching only your free project.

What server do I need?

A fresh server running the latest Ubuntu LTS that you can reach as root, rented from a company like Hetzner, DigitalOcean, Vultr or Linode. ox accepts any size from 1 GB of memory and 10 GB of free disk, and if an app needs more memory than the server has, ox tells you that is why it stopped. Your server runs only the small ox agent, Caddy and what your apps ask for, as how ox self-hosts your apps shows.

Do I need to know Linux or Docker?

No. You paste one command on your server once, and everything after that happens in the dashboard. ox doesn't use Docker, and you won't need to log in to the server. If you can push code to GitHub, you can use ox.

Is my server safe with ox?

ox locks it down when you add it: SSH with keys only, where you log in as ox_user with your same keys instead of root, a firewall where ox opens only SSH, 80 and 443, fail2ban, and daily security updates. The ox agent dials out to ox, so it needs no open port, ox holds no SSH key, and the agent refuses any command ox did not sign. Each app runs as its own user in a sandbox. Security lists every setting and how to check it.

What if a deploy fails, or ox goes down?

Your live app keeps running. ox checks everything it can before it changes anything, and if a step still fails, it tells you which step, why, and how to fix it. You can also go back to an earlier release in seconds, with no rebuild, and your database stays as it is. If ox itself goes down, your apps, workers and cron jobs keep running on your server. Deploys, backups and alerts stop while ox is down, as When ox is down explains.

Can I leave?

Yes. Your server and your data were always yours, your database backups are standard pg_dump files, and your variables live on your server. When you delete your account, ox removes only its agent from each server (or tells you the one command to run there), and your apps, databases and Caddy keep running with nothing managing them. How to leave lists what to copy.

What does ox store, and what stays on my server?

ox keeps only what it needs to run your account. Your app and its data stay on your server.

ox keeps:

Your GitHub login, name, picture and email.
The servers and projects you add, and a short record of each run.
For a failed run, its last 40 lines of output, with secrets hidden.
Usage numbers for the charts: one-minute points for 24 hours, then 15-minute points for 30 days.
A log of who did what in your account, with the IP address it came from, kept for 12 months.
Your settings, like which alerts you want.
Your plan and its Dodo Payments subscription, never your card number.
Tokens and keys, encrypted or stored only as a hash.
Each browser you are signed in on, with its IP address, a short browser name, and when it signed in and was last active.
Sign-in codes for ox login, with the IP address that asked.
ox's own server logs, which can name your account and hold IP addresses, kept up to 5 weeks.
A copy of its own database every hour. The newest 24 copies stay on ox's own server, and the newest 168 copies (7 days) in a storage bucket ox owns.

Stays on your server:

Your code, builds and releases.
Your variables and secrets. ox shows them to you but keeps no copy.
Your databases, files and uploads.
Backups of your services. A copy goes to your own S3 bucket only if you add one.
Your app's logs. ox reads them only when you ask to see them.

The privacy policy has every detail, and the security docs say it in short.

Does my app's data ever leave my server?

Only to do what you ask. Logs you open, rows you browse in Explore, and backups you download pass through ox to your screen. Your variables pass through ox when you view or save them, and when ox copies them to a new staging copy or preview. A page that only lists them asks your server for the names, never the values, and your server keeps its own record of each time it hands them over. ox does not save them.

Your server also sends ox its health, its usage numbers and the output of each run while it runs. Your code goes from GitHub straight to your server, with a short-lived, read-only token for that one repo (a repo with private submodules also gets one for just those repos). Alert emails go out through Resend. You choose which: a failed run or backup, a crashing process, a site or server that stops answering, high memory or CPU, a nearly full disk, a server that drifts from its security setup, or a finished deploy. Each says what happened, and for a failed run the start of its error.

ox itself adds no analytics, ads or tracking scripts. Cloudflare, which sits in front of the site, adds a small security check script, as the privacy policy explains. ox never reads your app's data for its own use.

What is ox?

ox Cloud, at deploywithox.com, is a deployment platform: you connect a GitHub repo and ox deploys it to your own Ubuntu server with systemd and Caddy, no Docker. It is not Open-Xchange's OX App Suite or OX Security, which are unrelated products.

ox looks after the server
while you build the app.

Put your next app on a server you own.

Free for your first project. $10 a month for all of them.