The questions worth answering up front.
No marketing fluff. Each answer is what the system actually does — if it changes, this page changes with it.
- + Base
eip155:8453 - + native: BTC
Do you require KYC?
No. There is no email field, no phone field, no name field, and no identity verification at any point in our flow. You can place anonymous one-shot orders without an account; if you sign up, your username is a random H<10 hex> handle that we generate and you cannot change.
What payment methods do you accept?
USDC via x402 on Base. Native VM checkout rails currently enabled: BTC. Domains and network requests use x402 for this launch. The payment list is read from the backend at order time — we never hardcode it in the UI.
What data do you collect about me?
vm_id, the VM config you typed in, your SSH public key, the wallet address that paid (for x402 orders only), your random account handle and an argon2id password hash (if you signed up), and a sha256 of your /64 IPv6 prefix for abuse rate-limiting. We do not collect: email, phone, name, address, full IP, or anything inside your VM.
Where are you located? What jurisdiction applies?
Solo operator in the Netherlands. Compute is at OVH France. Routing peers are in NL and DE. See /transparency for the full host inventory.
What if I lose my password?
Two paths. (1) The recovery code we showed you once at signup — argon2id-hashed at rest, single-use, auto-rotated after consumption. (2) If you have ever settled an x402 EVM payment on the account, you can recover via wallet signature from the same wallet that paid. If you have neither, the account is unrecoverable — that is the cost of no-KYC.
Can you read what's running on my VM?
No. The VM is bare: cloud-init drops your SSH key in and configures the firewall defaults, then we step out. There is no monitoring agent on customer VMs, no introspection API, no scheduled checks of disk contents.
Why IPv6-only? What if my client needs IPv4?
We don't have IPv4 to spare — the OVH host gives us one /32, used by the router for NAT64 egress. Every VM gets a routable IPv6 /128 inside 2a0c:b641:b51::/48. NAT64 + DNS64 on the router translate to IPv4 destinations transparently. Inbound IPv4 to your VM is not available in v1.
How fast is provisioning, really?
The homepage shows a live number computed from the backend's most recent provisioned_at - created_at values. Typical is ~60 seconds. Cold templates can take a little longer.
Can AI agents use Hyrule Cloud?
Yes. We ship an x402 service manifest at /.well-known/x402.json so agents can discover, price, and pay per-call. POST /v1/vm/create with an X-Payment header is the whole flow. Scoped API keys (read, power, extend) for non-payment management land in plan Block D.
How do I report abuse?
Send precise reports to abuse@as215932.net with reporter contact, URL or hostname or IP, allegation, evidence, timestamp, and urgency. Operational reports go to noc@as215932.net; customer support goes to support@hyrule.host. See /abuse and /legal for the notice/action flow.
What does 'anonymous checkout' actually mean for the VM management?
At order time we return a one-time management URL of the form /order/manage/{vm_id}?token=hyr_vm_…. The token cleartext is shown ONCE — save it. The token is sha256-hashed at rest; without it (or without an account that owns the VM), the management endpoints return 404. Status pages remain visible by vm_id alone.
What if I overpay on a native crypto intent?
When native intent rails are enabled, overpay is fine — it provisions normally and the surplus stays in the receive wallet. Pay late but match a fresh rate quote within 1% slippage and it still provisions (LENIENT policy). Underpay queues the intent for manual review.