Terms of service

Last updated 2026-10-25

These terms are the agreement between you and ox for ox Cloud (deploywithox.com) and the ox program (the command-line tool and the agent). By signing in, you accept them. If you use ox for a company, you accept them for that company. Questions: contact@deploywithox.com.

The short version

• ox's Free plan costs nothing, ox Pro is USD 10 a month or USD 80 a year, and ox makes no uptime promise.
• Your server, your code and your data stay yours, and you are responsible for them.
• Your apps keep running on your server if ox stops.
• Check your backups yourself. ox does not back up everything.
• Do not use ox to break the law or to harm others.

1. Who ox is

ox Cloud is run by Saurav Sharma, one person in India, as an individual, not through a company. In these terms, "ox" means him.

2. What ox does

ox deploys your GitHub repositories onto Ubuntu servers that you rent and own. ox Cloud is the control plane: it runs on ox's server and keeps your account, settings and run records (the privacy policy lists them). Your apps, databases, variables and backups run and live on your server.

When you add a server, the install command you run as root on it:

• installs the ox agent, which connects out to ox Cloud and carries out the jobs you ask for, and Caddy, the web server that serves your sites with HTTPS;
• hardens the server: SSH by key only with no root login, a firewall that opens only SSH, 80 and 443, fail2ban, and Ubuntu's automatic security updates;
• adds an operator account, ox_user, with sudo, and moves root's SSH keys to it;
• then, as you deploy, adds a system user, a folder, systemd services and the packages and databases each project needs.

Security lists what ox sets, and sudo ox uninstall removes what ox created there, but leaves the firewall, fail2ban and automatic updates on. Connect only servers that you are free to change this way.

3. The beta

ox is in beta. It is provided "as is" and "as available". There is no service level agreement: no promise of uptime, of support response times, of features, or that it is free of bugs or data loss. ox can change, break or be withdrawn.

4. Your account

• ox is for people 18 or older (or the age of majority where you live) who can make a binding contract. ox does not check ages; if ox learns an account belongs to a minor, it may close it.
• You sign in with GitHub. Keep your GitHub account secure: anyone who controls it controls your ox account.
• You are responsible for what happens under your account, your tokens and your servers. Tell ox at once if you think someone else got in.

5. Your servers, code and content

• You are root on your server and responsible for it: renting it, paying for it, its security, its data, and your account with your hosting company. Anyone with an SSH key for its operator account is root on it too.
• You are responsible for your code, your apps, your data and your users, and for what your apps do. You need the right to deploy what you deploy, and to use the software, licences and services in it.
• You are responsible for following the laws that apply to your apps and to the personal data they handle. The privacy policy says what ox does with it, and section 18 sets out how ox handles it for you.

6. Acceptable use

Do not use ox, or a server you run through ox, to:

• host or share illegal content, or content that infringes others' rights;
• send spam, or run phishing, scams, malware or botnets;
• attack, scan or disrupt other people's systems, or ox's;
• mine cryptocurrency, or run open proxies or similar services for others;
• get around ox's limits or security, or reach another account's data;
• load ox's servers so much that it harms other customers.

7. Backups are your job to check

ox backs up your PostgreSQL databases and most other services it runs for you (not a custom service set to backup = false) once a day and when you ask, on your server and, if you set one, in your own S3-compatible bucket with any provider you choose. Those backups are yours to look after: the bucket, its provider and its terms are your choice. It does not back up files you keep in a project's storage folders (other than SQLite databases), your variables, or your server itself, and it does not test that a backup can be restored. A server lost without an S3 bucket loses its backups with it. Backups and restore has the details. Keep your own copies of what matters, and test a restore now and then.

8. Suspension

• ox may suspend your access to ox Cloud, or stop jobs for a server or project, if it reasonably believes you broke these terms, or to protect people, ox's servers or other customers. Where it can, ox will tell you first and say why.
• Suspension stops ox Cloud from working for you. Your apps keep running, and ox does not delete or change your apps or data on your server unless you ask. What ox removes on its own follows fixed rules: old backups past the counts in Backups and restore or past a project's share of the disk, preview copies once their branch has had no push for 7 days or is gone, and the server's trash after 7 days (sooner for service copies when the disk is nearly full).

9. Leaving, and the end of the service

• You can leave at any time. Delete your account in Settings (or with ox account delete): your apps keep running on your servers, an ox Pro subscription is cancelled first, and the ox agent on each server removes itself and leaves a note at /etc/ox/LEFT.txt. After that, ox no longer deploys, backs up or watches those apps; they are yours to run. To remove the apps as well, run sudo ox uninstall on a server: it deletes everything ox created there, backups included, so copy first: What ox backs up, and how to leave lists what to copy. You can download your account data in Settings.
• Your apps run on your own server, so they keep serving while ox is down or after it stops. What ox Cloud starts pauses: deploys, the daily backups (03:00 UTC), uptime checks, alert emails and agent updates.
• ox may end the beta or the service. It will email you at least 30 days before ox Cloud shuts down, unless that is impossible (for example, for legal or security reasons).
• After your account ends, what is kept is as the privacy policy says. Sections 5, 11, 12, 13, 14, 16, 18 and 19 still apply.

10. Price

ox Cloud has two plans, Free and ox Pro. ox Pro is on sale from 2026-10-14. Nothing is charged until you choose ox Pro and agree to it at checkout. The plans:

• Plans: Free covers one project, with its environments and previews. ox Pro is USD 10 a month, or USD 80 a year, flat, for any number of servers and projects.
• Testing credit: AI testing of pull requests (section 19) is paid from prepaid credit, sold as one pack of USD 100, paid once, plus any tax, on any plan. Credit never expires and is not refunded. ox emails you once when your credit falls to 30% or less of what you had after your last top-up.
• Who bills you: Dodo Payments is the merchant of record. It sells you the subscription and the testing credit, collects any sales tax, and holds your card details under its own terms. ox never sees or stores your card details.
• Renewal reminder: ox Pro renews on its own each month or year. ox emails you once, 4 days before each charge, with the amount, the date and how to cancel. It is the only reminder for that charge.
• Cancelling: Payments are not refunded. Cancel any time and you keep ox Pro to the end of the month or year you paid for. Cancel plan is on the Plan card in Settings, or run ox plan cancel.
• Charged by mistake: If you paid for a second ox Pro subscription that renews while your first one also renews, or paid after your account was deleted, ox cancels it and refunds its payments in full. A testing credit pack paid after your account was deleted is refunded in full too. A second subscription you set to end yourself is not cancelled or refunded: it ends with the month or year it paid for. For any other charge you think is wrong, write to contact@deploywithox.com.
• If a payment fails or a plan ends: your running apps keep running. Projects beyond the free one pause their deploys, backups, metrics, uptime checks, alerts and webhooks until you upgrade. After a failed payment, their deploys pause at once and the rest 7 days later, unless your card goes through. The project you pick to keep free (your oldest, unless you pick another) keeps all of them.

Your hosting company and any other service you use bill you themselves.

11. Who owns what

• Your code, apps, data and content are yours. You give ox only the rights it needs to run the service for you: reading the repositories you pick, showing deployments on them in GitHub, and running the jobs you ask for.
• ox's software, site and name are ox's. ox gives you a personal, non-exclusive right to use the ox program with ox Cloud while you have an account.
• If you send ox an idea or feedback, ox may use it without owing you anything. ox will not name you without asking.

12. No warranty

As far as the law allows, ox gives no warranties, express or implied, including that the service is fit for a purpose, available, or free of errors. ox does not promise that a deploy will succeed, that a backup can be restored, or that your server will stay reachable.

13. Limit of liability

As far as the law allows: ox is not liable for indirect or consequential losses, for lost profits, revenue or data, or for downtime of your apps or servers. ox's total liability for all claims about the service is limited to the greater of what you paid ox in the 12 months before the claim and USD 100. Nothing here limits liability that the law does not let anyone limit, such as for fraud.

14. Claims against ox caused by you

If someone else makes a claim against ox because of your code, your content, or your breach of section 6, you will cover ox's reasonable costs of that claim, as far as the law allows.

15. Changes to these terms

ox may change these terms. For a change that matters, ox will email you at least 14 days before it takes effect. If you keep using ox after that, you accept the change. If you do not agree, stop using ox and delete your account. The date at the top is the last change.

16. Law and disputes

• These terms are governed by the laws of India, and the courts of India decide any dispute about them or about ox. Please write to ox first: most problems can be fixed by email.
• Wherever you live, the consumer rights your own country's law gives you and that cannot be waived still apply.
• These terms and the privacy policy are the whole agreement between you and ox about the service. If one part cannot be enforced, the rest still applies.

17. Contact

contact@deploywithox.com

18. Data processing terms

Your apps' data lives on your own server, and ox mostly never sees it. Some of it does pass through ox when you ask: the logs you open or download, what you open in Explore, a backup you download or upload, the variables you view or save, and the error of a failed run, which ox keeps with the run's record, and what tested deploys send and keep (the privacy policy, sections 1 and 2, lists each). For any personal data in it, you are the controller and ox is your processor, and this section is the agreement the GDPR (Article 28) and laws like it ask for.

• What, why and how long. ox handles this data only to run the service for you, for as long as you have an account. It can be any personal data your apps hold, about your users, your staff or anyone else your apps deal with.
• Only on your instructions. Your instructions are the actions you take in ox: in the dashboard, with the CLI, through the API, or by setting up a deploy, a preview or a backup. ox does nothing else with the data. If ox thinks an instruction breaks data protection law, it will tell you. If a law makes ox handle the data in another way, ox will tell you first, unless that law forbids it.
• Where. You agree that ox handles the data on its server in Germany, reaches it from India, where ox is run, and keeps its backups in the United States, with the safeguards in section 4 of the privacy policy. With tested deploys on, ox also sends what section 19 lists to DigitalOcean's AI inference, in a region ox does not choose, under DigitalOcean's data processing agreement.
• Confidential. Only the person who runs ox can reach the data, and he keeps it confidential.
• Security. ox protects it with the measures in section 9 of the privacy policy.
• Subprocessors. You agree that ox uses these companies, each under a data processing agreement with the same duties as this section: DigitalOcean (hosts ox's server and its backups, and runs the AI model of tested deploys), Cloudflare (carries traffic between your browser and ox), Resend (sends alert emails, which can hold the start of a failed run's error), Sentry (stores reports of errors inside ox's own server, in the EU) and Dodo Payments (takes payments for ox Pro and testing credit, where it acts for ox). ox stays responsible for them. Before adding or replacing one, ox will email you at least 14 days ahead. If you object, you can cancel and delete your account before the change takes effect.
• Helping you. ox will help you answer requests from people about their data, and meet your duties on security, breach notices, impact assessments and talks with an authority (GDPR Articles 32 to 36), as far as ox's part allows. Most of the data is on your own server, where you can act on it yourself.
• Breaches. If ox learns of a breach that touches this data, it will email you without undue delay, with what it knows and what it is doing about it.
• At the end. When you delete a project or your account, ox deletes the data it holds for you, as the privacy policy, section 8, says, and its backups age out within 30 days. Your apps' data is on your own server, so ox has no copy of it to give back. What ox does hold, such as a failed run's error, is in the file from Settings, Your data, Download my data (or ox account export); download it before you delete.
• Showing it. ox will give you the information you need to show that these terms are met, and will answer your written questions. If that is not enough, ox will allow a reasonable audit by you or an auditor you choose, at your cost, at most once a year and with 30 days' notice.

19. Tested deploys

• Tested deploys are off until you turn them on, first for your account in Settings, Beta features, then for a project. The first time you turn them on for a project, ox asks you to agree to the data they send.
• When they are on, an AI tester uses each pull request's preview in a browser, like a person would, and writes checks that run again on later pushes.
• To write and judge the checks, ox sends the pull request's title, description and commit messages, its changes, the files the tester reads, the text of the preview's pages and what the checks print, the pages a crawl of the app found, the test accounts' names and roles, what you wrote about the app and your Not a bug reasons to DigitalOcean's serverless AI inference, which runs the open-source model deepseek-v4.1-flash-1017. Email addresses and co-author and sign-off lines are taken out of the pull request's text and commit messages before anything is sent.
• The checks run on your own server, against the preview and the staging copy, never against production. A preview starts with production's variables, so keep every key it copies test-only, such as payment and mail keys.
• While a copy still holds production's value of a key that looks like a credential, its runs wait until you mark the key Production only, give the copy its own value, or confirm the key as test-only. A live Stripe key, or a value that names production's address, can never be confirmed.
• AI testing is prepaid credit at cost: you pay what the model costs ox, with no markup. Credit never expires and is not refunded. Each pull request's run uses what its AI calls cost, from your testing credit (section 10). When your credit is less than the most a run may cost, or at USD 10 of AI in a day for your account, a pull request's run only replays the saved checks; at a daily limit for all of ox, runs wait for the next day. Production deploys never wait on your credit.
• The results are advice. You can mark a failed check Not a bug, and the held deploy goes ahead.
• When the ox GitHub App may write checks, each pull request's run shows on it as the ox tests check. For a public repository or a password-protected copy, that check holds only the state, the counts, and each red check's name and finding in a user's words.
• You can turn tested deploys off at any time, for a project or for your whole account. ox then completes the GitHub checks it had open, marked stopped, and sends nothing more to the model or to GitHub.
• ox does not promise that the checks find every bug, and section 13 limits ox's liability for a bug they miss.