StorkHost — Terms of Service

Last updated: 2026-06-25 · Status: Beta

StorkHost is an agent-first cloud hosting platform. AI agents (and humans, as a fallback) self-serve deploy and run containerized workloads, FaaS functions, and static sites, metered per second and paid for over crypto rails. By creating an account, obtaining an API key, signing a wallet-based admission challenge, or deploying any workload, you ("you", "Tenant") agree to these Terms.

1. Who we are

StorkHost is operated by Storksoft, an independent operator running StorkHost in beta. Storksoft is an operating name, not an incorporated company — there's no registered office or corporate parent. Support, abuse, and disputes are handled by email (below). The service is provided as-is, without warranties; crypto payments are final and non-reversible.

2. Contact

Reach us by email on the storkhost.cloud domain:

  • support@storkhost.cloud — general support, billing questions, disputes, and legal notices.
  • abuse@storkhost.cloud — acceptable-use and abuse reports.
  • privacy@storkhost.cloud — privacy and data requests.

There is no phone line, no postal address, and no ticketing SLA. We read the inboxes and reply, but we do not commit to a fixed support response time during beta.

3. Eligibility and accounts

  • Agent accounts are minted by signing a single-use, address-bound nonce with an EVM wallet (EIP-191 personal_sign). One free Tier-0 account per wallet address. Possession of the wallet's private key is treated as authorization; protect it accordingly.
  • Human accounts authenticate via the web front end.
  • API keys (sk_...) are bearer credentials. Anyone holding a key can act as your account. You are responsible for all activity under your account, keys, wallet, and any agent you authorize to act on your behalf. We do not collect identity documents; we cannot recover an account on the basis of "it was really me." Key/wallet custody is yours.
  • You must be legally permitted to use the service in your jurisdiction and to deploy the workloads you deploy.

4. The service is beta, and "as is"

StorkHost is provided on an "as is" and "as available" basis, without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service is fit for any particular purpose, will be uninterrupted, secure, or error-free. Terms, limits, prices, and remedies may change during beta; material changes are announced via the status page and/or email, and continued use after a change constitutes acceptance.

5. Your data — back it up yourself

We do not guarantee the durability of your data. StorkHost does not promise RAID-class redundancy or durable backups of tenant workloads or tenant-stored data, including PVC-backed volumes. You must keep your own backups of anything you cannot afford to lose, especially during beta.

We run platform-side backups of our own billing/ledger database for the integrity of your credit balance. That is not a durability promise for your application's data — do not conflate the two.

6. Acceptable Use Policy

You may not use StorkHost — directly or via any agent, payload, or workload you deploy — for any of the following. This list is a superset of our upstream host's restrictions: we run on third-party infrastructure and pass through their acceptable-use terms, because anything that gets our tenant nodes suspended takes your workloads down with them.

Strictly prohibited:

  • CSAM — zero tolerance. Child sexual abuse material results in immediate termination, preservation of evidence, and reporting to the relevant authority (NCMEC or local equivalent). No warning, no exceptions.
  • Illegal content or activity under common international norms — including weapons or drug trafficking marketplaces, fraud, phishing, carding, and the hosting or distribution of malware, spyware, command-and-control (C2), ransomware, or botnet infrastructure.
  • Network abuse — credential stuffing, port scanning of third parties, and originating or participating in DoS/DDoS attacks. You may not deploy anything that could overload, disrupt, damage, or degrade the equipment or networks used to provide the service.
  • Spam and abusive bulk automation — unsolicited bulk email/SMS/comment/bot traffic, email bombs, chain letters, pyramid schemes, or spam infrastructure aimed at third parties. Our upstream monitors outbound SMTP and levies fees for blacklist remediation; we pass any such cost and any resulting suspension through to the responsible account.
  • Uncompensated resource abuse — including, but not limited to, cryptocurrency mining, proof-of-work, or any compute pattern designed to extract value from reserved capacity without paying the metered rate for it. Compute, egress, storage, and builds are billed; using them to mine or otherwise monetize unpaid or trial capacity is prohibited and is grounds for immediate suspension and forfeiture of balance.
  • Containment evasion — attempts to escape the tenant sandbox, reach the orchestration/control plane, access another tenant's account, apps, logs, or data, or bypass the egress network policy, except where you are an explicitly authorized security researcher operating under a coordinated arrangement with us.
  • Intellectual-property infringement — publishing, reproducing, or distributing software or other material in violation of third-party IP, trademark, or copyright rights.
  • Hate, incitement, and unlawful violence — content that incites racial or ethnic hatred, is defamatory or seditious, or constitutes unlawful depictions of violence.

Catch-all (sole discretion): we may suspend, stop, or delete any payload that we judge — at our sole discretion — to be abusive, harmful, or reputationally toxic to the platform or to our upstream hosts.

7. Tenant responsibilities

You are solely responsible for:

  • The lawfulness, content, and behavior of every workload you deploy, and for any data you process or store.
  • Securing your wallet private key and API keys; rotating keys you believe are compromised; and the actions of any agent you authorize.
  • Maintaining your own backups (see §5).
  • Keeping a sufficient prepaid balance to run your workloads (see §8), and monitoring your own spend caps and usage.
  • Complying with all laws applicable to you and your end users, including data protection, export, and sanctions law.
  • Any third-party costs your workload causes us to incur (e.g. SMTP blacklist remediation, abuse-handling fees from our upstream), which we may charge to your account.

8. Billing, metering, and crypto payments

  • Metering. Usage is metered per second against your prepaid credit balance, denominated internally in micro-credit units (µ; 100,000,000 µ = $1). Billable dimensions include reserved compute, egress, provisioned storage, and per-build fees, at the rates published on the pricing page.
  • Zero balance. When your balance reaches zero you get a short grace period, after which the affected workload is stopped. We are not liable for any loss resulting from a workload stopped for non-payment.
  • Crypto payments are final and non-reversible. Top-ups are made in cryptocurrency (USDC via the x402 rail for agents; a hosted crypto checkout for humans). Blockchain transactions are irreversible; once a payment is confirmed and credited, it cannot be reversed, recalled, or charged back. You are responsible for sending the correct asset, on the correct network, to the correct address — funds sent incorrectly may be unrecoverable.
  • No cash refunds. Credits are prepaid and are not refundable for cash. Unused balances are not redeemable for fiat. During beta the SLA is best-effort and grants no service credits (see sla.md); any post-beta service-credit scheme would issue account credit, never cash.
  • Trial and promotional credits have no cash value, may be capped, may expire, are non-transferable, and may be revoked in the event of abuse.
  • Forfeiture. Credits or balances forfeited due to a policy violation are non-refundable.
  • Rate limit. Documented platform rate limit: 300 requests/min per API key, burst 60; exceeding it returns HTTP 429 with a Retry-After header.
  • Taxes. You are responsible for any taxes applicable to your use of the service.

9. Suspension and termination

We may suspend, stop, throttle, or delete any workload, key, or account, without notice and without refund, if we reasonably believe it violates these Terms or the Acceptable Use Policy, threatens the platform or our upstream hosts, or is required by law. For a CSAM violation, termination is immediate and irreversible. You may stop using the service and delete your workloads at any time; this does not entitle you to a refund of prepaid balance. We may also discontinue the service, in whole or in part, during beta, on reasonable notice where practicable.

10. Limitation of liability

To the maximum extent permitted by law:

  • The service is provided without warranty (see §4).
  • We are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost or corrupted data, or business interruption, arising from or related to your use of the service.
  • Our total aggregate liability for any claim arising out of or relating to the service is limited to the amount you paid to StorkHost for the service in the 30 days preceding the event giving rise to the claim. During beta the SLA grants no service credits, so no additional credit-based remedy applies. Because trial/free usage involves no payment, our liability for free-tier usage is limited to the value of credits granted, if any.

11. Indemnity

You agree to indemnify and hold harmless Storksoft and its operator(s) from any claim, demand, loss, or expense (including reasonable costs) arising out of your workloads, your content, your breach of these Terms or the AUP, or your violation of any law or third-party right.

12. Disputes and governing law

Disputes are handled informally by email at support@storkhost.cloud; the service is provided as-is. Storksoft operates as an unincorporated independent operator, so no governing law or jurisdiction is asserted today; a formal clause will be added if an entity is formed.

13. Changes to these terms

Because StorkHost is in beta, these terms may change. We announce material changes via the status page and/or email. Continued use after a change constitutes acceptance.

Honesty is the differentiator. We would rather tell you plainly what we don't promise than bury it in boilerplate and surprise you later.