← Hosted Isomux

Terms of Service

Last updated: 16 August 2026

These terms are the agreement between you and Isomux LLC ("we") for Hosted Isomux. Signing up means you accept them.

What we run for you

We rent a virtual private server on your behalf, install isomux on it, and serve it at the name you picked, over HTTPS. You get a sign-in link when it is ready.

The price covers the server. The agents run on your own Claude or ChatGPT plan, which you sign in to from inside the office. We do not resell model usage and never sit between you and your model provider.

The box is yours to use

You decide what runs on the server, what it connects to, and who you invite into the office. That makes it your responsibility, including anything your agents do. The server provider's acceptable-use terms apply to the machine on top of these.

Exporting your work is also yours to do. See cancellation below for when the window closes.

Your content

Everything you and your agents create on the server is yours. We take no license to it, and the access rules below mean we cannot read it.

Getting into your own server

During signup, your browser creates a server administrator key. You must save it somewhere only you can access. We receive only its public half and install it on your server so you can access it with the private half. You need the private key to install software, manage the server, recover office access, and verify that our setup key is gone. For safety reasons, Isomux agents and the built-in terminal cannot act as a privileged user. Only you can do so with the administrator key.

If you lose the private key, you cannot add administrator access from inside Isomux. You must ask us in writing to use the VPS provider's rescue console under the access rules below, or reinstall the server and erase its disk.

Our access to your server

We hold an SSH key to your server while we set it up, and only then. If you confirm from your office that you are in, we remove the key, prove the removal by requiring a reconnect attempt to fail, and destroy our copy. If you do not confirm, the server makes the key unusable seven days after signup and removes it during cleanup. After either event, we have no way into your running office, and we never see what is inside it.

If you later ask us in writing to look at a specific problem, we can open the provider's rescue console, which reaches the disk. We do that only on that request, we record what we do, and the access ends with the problem.

What we keep as the renter

The provider account is ours, so provider-level controls stay ours: reboot, power off, power on, reinstall, and the rescue console, which follows the rules in the section above. The power controls we use in three situations, and no others: when you ask (your account dashboard's reboot button is one of them), when a payment fails, and when your subscription ends. Both of the latter are described below.

This is administrative control, not a way to read your files, and it is not something we can technically give up while we hold the account.

For comparison: the rescue capability is not something we added - it comes with renting servers at all. Every major provider documents a rescue environment available to whoever holds the account (Contabo, Hetzner, DigitalOcean), which is why we spell out how we govern it instead of pretending it does not exist. Managed hosts of similar products keep wider access than ours: OneClickClaw, for example, offers customers opt-in SSH for its own staff and logs those sessions, commands included (terms, privacy policy).

Payment

Plans are monthly: Stripe charges at the start of each monthly period, beginning the day you sign up. Change your card through Stripe's customer portal.

We can change prices with 30 days' notice by email; a change takes effect at your next renewal after the notice.

If a payment fails

Stripe retries on its own schedule. Until the retries run out, the office keeps running as normal, so you can take your work out at any time. Then we suspend it by powering the server off; your data stays on the disk, untouched, and the office comes back exactly as it was when the payment goes through. Payment-failure suspension is separate from cancellation. The current system does not automatically delete a payment-suspended server on a fixed schedule.

Cancelling

Cancel from your account dashboard at any time. Your office keeps running through the end of the period you paid for. At that instant, we power the server off and access stops. The server is not deleted for 14 days. During that time, restarting your subscription reinstates the same server after payment is confirmed. After 14 days, we ask the provider to delete the server as soon as the provider permits.

Cancelling partway through a period does not refund the rest of it. Two exceptions: your first week - cancel within 7 days of first signing up and we refund in full - and cases where we failed to deliver, at our discretion.

Uptime, updates and maintenance

The office runs entirely on your server - there is no isomux cloud service that can take it down - so its availability is your server's. We do not add an uptime promise of our own on top of the provider's. When a new isomux release is out, your office tells you and you apply it when you choose, so updates happen on your schedule, not ours; a failed update rolls back on its own. The server provider's own maintenance and security work can interrupt service without notice - that work is theirs, not ours.

Isomux keeps seven daily backups on your server. You can keep external copies for additional protection.

Support

Reach us at llc@isomux.com or in the Discord. We aim to respond within 24 hours or less, but do not commit to a response time.

When we can suspend or close an account

For non-payment, as above. Otherwise only for illegal use, or use that breaks the server provider's terms and puts the machine or our account at risk. We tell you why, and where the situation allows it we give you a chance to fix it first.

No warranty

The service is provided as is. Agents make mistakes, run commands, and change files; you are responsible for what you let them do and for keeping copies of anything you cannot lose.

Limit on liability

To the extent permitted by law, we are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, business interruption, or lost data. Our aggregate liability is limited to the greater of $100 or the fees you paid us in the 12 months before the event that gave rise to the claim. These limits do not apply to liabilities that applicable law does not allow us to exclude or limit.

Governing law

These terms are governed by the law of the State of Oregon, USA, and disputes are handled in Oregon courts.

Changes to these terms

If we change them we will say so on this page and email you before the change takes effect. Continuing to use the service after a change means you accept the new terms.

See also the privacy policy.