Terms and Conditions

These Terms and Conditions govern access to and use of Rustbox, including the public website, documentation, dashboard, playground, APIs, SDKs, webhooks, examples, sandbox execution service, and related beta programs.

By creating an account, requesting an API key, using the playground, calling the API, or otherwise accessing the service, you agree to these terms on behalf of yourself or the organization you represent.

If you have a separate written agreement, order form, or enterprise contract with Orkait, that signed agreement controls if it conflicts with these public terms.

Rustbox is currently offered as an open beta service. Features, limits, endpoints, runtime profiles, language support, pricing, retention periods, and documentation may change as the product matures.

During beta, Orkait may add, remove, throttle, pause, or modify functionality to protect the service, improve reliability, or respond to abuse and infrastructure constraints.

We try to announce material breaking changes through documentation, release notes, or product notices, but beta users should not rely on any endpoint, profile, or limit remaining unchanged without a separate written commitment.

You are responsible for the accuracy of account information, OAuth account details, project settings, API key labels, webhook endpoints, and contact information you provide.

API keys, session cookies, dashboard access, OAuth tokens, and webhook signing secrets are confidential credentials. Keep them secure, rotate them if exposed, and do not publish them in source control, client-side code, logs, package registries, or public issue trackers.

You are responsible for all activity under your account, API keys, projects, and integrations, whether performed by you, your team, your users, or an automated system using your credentials.

Rustbox is designed to execute untrusted code in controlled sandboxes. That does not authorize attacks against Rustbox, Orkait, other users, third-party systems, cloud providers, package registries, identity providers, or networks.

You may not use the service to distribute malware, mine cryptocurrency, conduct denial-of-service activity, scan or attack third-party systems, exfiltrate data, bypass rate limits, evade authentication, overload infrastructure, or violate law.

Security testing of your own submitted workloads is allowed only when it stays within documented limits and does not attempt to escape the sandbox, attack the service infrastructure, attack the host, or target third parties.

Orkait may block, rate-limit, suspend, delete, or investigate submissions, API keys, sessions, projects, or accounts that appear abusive, unsafe, fraudulent, or operationally risky.

You retain ownership of code, stdin, test cases, request bodies, files, prompts, outputs, and other material you submit to Rustbox. Orkait does not claim ownership of your submitted content.

You grant Orkait a limited license to process submitted content as needed to run the sandbox job, return results, generate verdicts, maintain evidence, enforce quotas, debug failures, investigate abuse, and operate the service.

Do not submit secrets, production credentials, regulated personal data, confidential customer data, export-controlled materials, or data you are not authorized to process through Rustbox.

Execution output, verdicts, timing data, memory measurements, exit status, syscall evidence, logs, and related metadata may be stored for operational, billing, quota, support, and abuse-prevention purposes as described in the Privacy Policy.

Rustbox may enforce language-specific limits, wall-time limits, CPU limits, memory limits, process limits, filesystem restrictions, network policy, seccomp policy, namespace isolation, queue priority, and payload size limits.

A job may fail, time out, be killed, be rejected, return partial output, or produce a different verdict if it exceeds resource limits, violates policy, triggers isolation controls, or depends on nondeterministic runtime behavior.

Sandboxing reduces risk, but no isolation system is perfect. You should treat results, logs, and outputs as untrusted unless your own application validates them.

Published plans may include request-per-minute limits, daily limits, queue priority, support response targets, runtime profile differences, webhook features, or other capabilities. Actual limits may vary during beta.

Free and beta access may be changed, paused, revoked, or rate-limited at any time. Paid plan details, if available, are governed by the plan description, invoice, order form, or separate written agreement.

Unlimited or high-volume plans remain subject to fair use. Sustained usage that threatens service stability, materially exceeds expected plan behavior, or resembles abuse may trigger an upgrade conversation, throttling, or suspension.

Unless expressly stated in a signed agreement, fees are non-refundable, taxes are your responsibility, and missed or failed payments may result in suspension or downgrade.

If you configure webhooks or integrations, you are responsible for endpoint availability, endpoint security, signature verification, retry behavior, payload storage, and access controls on your receiving system.

Orkait may retry, drop, disable, or delay webhook deliveries to protect service reliability or when an endpoint repeatedly fails, rejects payloads, times out, or appears unsafe.

Third-party services such as OAuth providers, cloud platforms, email providers, repositories, package registries, and customer-managed endpoints are governed by their own terms and privacy policies.

Orkait owns Rustbox, including the platform, website, APIs, SDK names, documentation structure, runtime profiles, sandbox orchestration, infrastructure, trademarks, logos, product design, and service-generated operational systems.

You may use SDKs, examples, and documentation only under their applicable license and solely to integrate with Rustbox or evaluate the service.

If you send feedback, bug reports, ideas, benchmarks, feature requests, or suggestions, Orkait may use them without restriction or compensation, while you retain ownership of any underlying content you independently own.

Support channels, response times, and escalation paths depend on your plan or written agreement. Beta support is provided on a best-effort basis unless stated otherwise.

Orkait may send service messages about account security, API key changes, incidents, billing, feature changes, abuse investigations, or policy updates. These transactional messages are part of operating the service.

Documentation, examples, latency numbers, benchmark references, and availability statements are informational and may not match every region, workload, language, profile, or infrastructure condition.

Rustbox is provided on an as-is and as-available basis unless a separate written agreement says otherwise.

Orkait does not warrant that the service will be uninterrupted, error-free, secure against every attack, compatible with every workload, or suitable for a particular legal, compliance, production, safety-critical, or regulated use case.

You are responsible for testing your integration, validating results, handling failures, applying retries safely, protecting credentials, and deciding whether Rustbox is appropriate for your use case.

To the maximum extent permitted by applicable law, Orkait will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, business interruption, or replacement services.

Unless a separate written agreement states otherwise, Orkait's total liability for claims relating to the service is limited to the greater of the amount you paid to Orkait for the service in the three months before the event giving rise to the claim or USD 100.

Some jurisdictions do not allow certain limitations, so some limitations may not apply to you. In that case, liability is limited to the fullest extent permitted by law.

You agree to defend and indemnify Orkait from claims, losses, liabilities, damages, costs, and expenses arising from your submitted content, your use of the service, your integration, your violation of these terms, or your violation of law or third-party rights.

Orkait will promptly notify you of a claim when legally permitted, allow you to control the defense where appropriate, and cooperate reasonably. You may not settle a claim in a way that admits fault or imposes obligations on Orkait without written consent.

You may stop using Rustbox at any time. You may request account or project deletion through the support contact listed below.

Orkait may suspend or terminate access immediately for security risk, abuse, payment failure, legal risk, platform attack, credential exposure, quota evasion, or violation of these terms.

After termination, provisions that by their nature should survive will survive, including ownership, submitted content processing needed for retention and audit, disclaimers, liability limits, indemnity, and dispute-related provisions.

Orkait may update these Terms and Conditions as the product, pricing, infrastructure, or legal requirements change. The last-updated date will identify the current version.

Material changes may be announced through the website, dashboard, documentation, email, or other service notice. Continued use after an update means you accept the updated terms.

Questions about these terms can be sent to [email protected].