Terms of Service

These Terms of Service (“Terms”) govern your use of Voxen Cloud (“Voxen”, “we”). By signing up, deploying a project, or otherwise using the platform, you agree to these Terms, the Acceptable Use Policy, and the Service Level Agreement.

1. Your account

You are responsible for maintaining the confidentiality of your credentials and for all activity that occurs under your account, including activity by collaborators you invite. We may suspend or terminate accounts for material breach of these Terms or the AUP.

2. Your content and code

You retain all ownership of the code, data, and content you upload, deploy, or generate on Voxen. You grant us a non-exclusive license to host, transmit, and process that content solely as necessary to operate the service for you.

You are solely responsible for the quality, behavior, security, and uptime of your code. Voxen runs your code on isolated infrastructure with documented resource limits, but does not audit, debug, or warrant that any code you deploy will function correctly.

3. What Voxen is responsible for

Voxen is responsible for the availability, integrity, and performance of the Voxen Platform — the dashboard, the build pipeline, the request-routing proxy, managed databases we provision for you, and SSL certificate renewal on hosts we issue. The platform’s availability target is described in our Service Level Agreement.

4. What Voxen is not responsible for

Voxen is not responsible for downtime, errors, data loss, or other failures arising from your code, your dependencies, your configuration, third-party services you integrate with, or content you publish. Examples include but are not limited to:

Your container exiting with a non-zero code, looping, or running out of memory;
Bugs or vulnerabilities in your application code or its dependencies;
Outages of external APIs you call (Stripe, OpenAI, your own backend, etc.);
Misconfiguration of environment variables, DNS, custom domains, or build commands;
Exceeding the resource limits documented for your plan.

We provide tools — logs, status pages, deploy history, automated restart with backoff — to help you diagnose and recover from these events. We do not monitor them on your behalf, and SLA credits do not apply to project-level incidents.

5. Bounded auto-recovery

When your container exits unexpectedly, we will attempt up to three automatic restarts with backoff (1 second, 5 seconds, 30 seconds). After the third failure, the project enters the CRASHED state, we capture the last 200 lines of standard error, and we stop further restart attempts until you push a new deploy. This bounded behavior is by design — we will not silently keep retrying broken code.

6. Fees and credits

Voxen offers a free tier with documented quotas, prepaid credits with no expiration, and metered usage that is debited against your credit balance or a payment method on file. Stripe processes payments on our behalf. Detailed pricing is published on the Billing page.

7. Suspension and termination

We may suspend or terminate your account if your use violates these Terms or the AUP, if you fail to pay, or if your usage causes harm to other Voxen users. Upon termination, you may export your data for thirty (30) days; thereafter we may permanently delete it.

8. Disclaimer and liability

Voxen is provided “as is”. To the fullest extent permitted by law, Voxen disclaims all warranties, express or implied. Our aggregate liability for any claim arising out of or related to these Terms is limited to the fees you paid us in the 12 months preceding the claim.

9. Changes

We may update these Terms by posting a new version with a new effective date. Material changes will be communicated by email at least 14 days before they take effect.

10. Contact

Questions: hello@voxenlabs.cloud.