Terms of Service

1. Your account

• Provide accurate information and keep your credentials secure. Anything done with your account, your API keys, or agents you connect through them is your responsibility — including actions taken autonomously by an LLM agent you've given a key to.
• API keys can be scoped and revoked; mint the narrowest scope that works, and revoke keys you no longer use.
• You must be legally able to enter into this agreement (and old enough to do so where you live).

2. The service

z3.run runs your workloads in hardware-isolated Firecracker microVMs with deny-all networking by default, and provides domains, TLS, storage volumes, logs, metrics and an API/MCP surface to manage it all. We aim for high availability but the service is provided "as is" and "as available" — features may change, and maintenance or incidents may cause interruptions. Workloads are stopped and restarted as part of normal platform operation (e.g. migrations, host maintenance); design your apps to tolerate restarts.

3. Credits & billing

• Usage is billed from prepaid credits (1 credit = $1). Running pods consume credits continuously, metered by allocated CPU and memory; storage volumes consume credits for as long as they exist — at the per-unit monthly rates shown in your project's Usage & Credits page.
• When a project's credit pool reaches zero, its pods are stopped automatically. Your data (volumes, persistent root filesystems, configuration) is kept so you can top up and restart, but keeping a project funded is your responsibility. Optional auto top-up can refill a project from your wallet monthly.
• Credits are not transferable outside the platform and have no cash value; unused credits are refundable only where required by law or at our discretion. Rates may change with reasonable notice.

4. Acceptable use

Don't use z3.run to harm others or the platform. In particular, you may not:

• Run, store or distribute content that is illegal where you or we operate, or that infringes others' rights.
• Operate malware, botnets, command-and-control, phishing, or launch attacks (DoS, port-scanning, credential stuffing, spam) from the platform.
• Attempt to escape the microVM sandbox, access other tenants' data, probe the control plane, or interfere with the isolation and firewall mechanisms. (Good-faith security research is welcome — contact us first.)
• Mine cryptocurrency or run similar sustained resource-abuse workloads without prior written agreement.
• Resell the service in a way that hides who is responsible for the workloads.

5. Your content

• You keep ownership of everything you deploy. You grant us only the limited rights needed to host, run, store, route and back up your workloads — that is, to provide the service.
• You are responsible for having the rights and licenses to whatever you deploy (code, images, models, data), and for its lawfulness.
• Exposing a workload on a domain makes it publicly reachable — you decide what gets exposed, and you're responsible for securing your own applications.
• Keep your own copies of anything you can't afford to lose. Volume and rootfs persistence is a convenience, not a guaranteed backup service.

6. Suspension & termination

• We may suspend or stop workloads that violate these terms, threaten the platform or other tenants, or run without credits. Where practical we'll warn you first; genuine emergencies (active abuse, security incidents) may require immediate action.
• You can delete projects or your account at any time; deletion removes your workloads and data as described in the Privacy Policy.
• If your account is terminated for a serious violation, remaining credits may be forfeited to the extent allowed by law.

7. Disclaimers & liability

To the maximum extent permitted by law: the service is provided without warranties of any kind, express or implied, including fitness for a particular purpose and non-infringement. Strong isolation is the core of our design, but no security boundary is absolute, and we are not liable for what your own applications or agents do. Our total liability for any claim relating to the service is limited to the amount you paid us in the 12 months before the claim arose. We are not liable for indirect, incidental or consequential damages, or for loss of data you did not back up.

8. Changes to these terms

We may update these terms as the service evolves. Material changes will be announced (in-product or by email) with a reasonable notice period; continuing to use the service after they take effect means you accept them. The "last updated" date above always reflects the current version.

9. Contact

Questions about these terms: legal@z3.run. For security reports: security@z3.run.