Get started with plans and billing

Everything about plans and paying, then the rules in plain words. Prices are always on the [Billing page](/billing), next to what you've used. ## 1. Start free ```diagram type: stats title: The Free plan, across Zaryn --- ∞ | public repositories | 5 private, 2 GB in all | | 400 | CI minutes a month | 2 CPUs, 4 GB a step | | 10 | network devices per site | every check, the twin, rollouts | | accent 500 MB | packages and images | public; mirrors never count | | ``` Every product has a Free plan you can use for real work, not a trial: repositories, CI, packages and mirrors, file sharing, network sites, virtualization, the proxy. Nothing to pay to start, and nothing is deleted if a limit is reached: you're told, and can choose what to do. ## 2. What Premium adds ```diagram type: cards --- 🕸 | Private networks | A WireGuard mesh for your devices | accent 🔒 | Private packages and images | Only you or your organization can install them | 📈 | Room to grow | 10,000 CI minutes, 100 GB for packages, up to 1,000 network devices | good 🌊 | Safer big changes | Canaries, waves and maintenance windows for rollouts; failure drills on the twin | ✍ | Proof for audits | Change certificates on design repositories; a year of device-access recordings | 🧮 | Deeper analysis | Availability, capacity and disjoint-path intents; multi-arch image builds; semantic search | ``` The full list, with today's prices, is on the [Billing page](/billing). ## 3. Credits: a prepaid balance ```diagram type: flow title: Dollars in, Premium out --- Pay USDC | From any wallet, on Solana or Base | | 💵 ~ credited once the network confirms it Credits | 1 credit = 1 US dollar, in your account | accent | 🪙 ~ buy, then renew automatically Premium | For a month or a year | good | ✦ ``` Credits aren't a token or currency: they live in your Zaryn account, can't be transferred or cashed out, and only pay for Zaryn. Prices are in dollars, so a credit is always worth exactly one. ## 4. Top up ```diagram type: flow title: From the Billing page, in under a minute --- Choose | An amount and a network | | 🧾 ~ Get payment details Pay | Scan the QR code or open the link in your wallet | accent | 📱 ~ the network finalizes it Credited | Usually well within a minute; the page updates by itself | good | ✓ ``` Send **only USDC**, only on the network you chose. ## 5. Solana or Base ```diagram type: cards --- 🟣 | Solana | A Solana Pay request: amount, address and the invoice's reference filled in for you (Phantom, Solflare, Backpack…) | accent 🔵 | Base | Scan or open the link in an Ethereum wallet (Coinbase Wallet, MetaMask, Rabby…), or send exactly the amount shown | good 🔢 | Exactly that amount | On Base, a unique tail of a few millionths of a dollar tells Zaryn which invoice you paid: send it to the last digit | warn ``` ## 6. When something's off ```diagram type: cards --- ⏰ | Paid late | A payment that arrives after the invoice's timer still counts | good ➖ | Paid less | What arrived is credited; top up the rest | ❓ | Wrong amount on Base, or no invoice | Kept safe for review: contact support with the transaction | warn ``` ## 7. Buy Premium, and let it renew ```diagram type: flow title: Set and forget, or not --- Buy | A month or a year, from your credits | accent | ✦ ~ when it ends Renews | From your balance, automatically; you can turn that off | | ↻ ~ a day before, if credits are short Reminder | A notice, so it doesn't lapse by surprise | warn | 🔔 ``` ## 8. Organizations pay for the team ```diagram type: cards --- 🏢 | Their own credits | An organization has a balance separate from its members' | accent 👑 | Owners and admins | Top it up and buy Premium for the whole organization | 🤝 | Everyone benefits | The organization's repositories, sites and networks get Premium | good ``` ## 9. Every payment, on record ```diagram type: cards --- 📜 | History | Every top-up, charge, refund and bonus, with the balance after each | accent 🧾 | Receipts | A printable receipt for every payment | 📊 | Usage | What you've used against your plan, on the same page | ``` ## 10. How payments are kept safe ```diagram type: graph title: Where the money goes, and who can move it alt: Your wallet pays the company's multisig treasury; Zaryn's servers only read the blockchain and credit your account height: 34 --- node wallet | your wallet | 12 16 | user | | You sign the payment node treasury | multisig treasury | 50 16 | lock | accent | No single key, and none on Zaryn's servers node servers | Zaryn's servers | 88 16 | server | good | Only read the blockchain: each transfer credited exactly once link wallet treasury | USDC | path link servers treasury | read only | ghost ``` Zaryn's servers never hold keys that can move money. Every balance change is a permanent ledger entry. Payments from addresses on sanctions lists are held for review, as the law requires. ## 11. Your content stays yours ```diagram type: cards --- ©️ | You keep the rights | To everything you upload: code, models, datasets, packages, comments | accent 🏠 | Used only to run the service | Hosting, serving, backing up, pinning to IPFS when you ask | 🌐 | Public means public | Anyone may view and copy public content; what's published to IPFS can't be pulled back from copies | warn ``` ## 12. Your data ```diagram type: cards --- 🚫 | Never | No selling personal data, no ads, no training models on your private content | good 🔍 | Visits | Counted without cookies; detailed logs kept 90 days, then only daily totals | 🙋 | Your rights | See, correct, export or delete your data, mostly yourself in Settings | accent ``` ## 13. The house rules ```diagram type: flow title: If something's wrong --- Report | Report on any repository or profile; reports are confidential | | 🚩 ~ reviewed Action | From a request to fix it, to hiding content or suspending an account; nothing deleted yet | warn | ⚖ ~ if we got it wrong Appeal | Reviewed by a different person; content can be restored | good | ↩ ``` The short version of the rules: no malware or phishing, no abusing the infrastructure (mining in CI, many accounts), no infringing or illegal content, no harassment or spam, and one account per person. > **The legal pages are being finalised.** This chapter summarises them in plain words and doesn't replace them: read the [Terms](/docs/en/terms), the [Privacy policy](/docs/en/privacy) and the [Acceptable use policy](/docs/en/acceptable-use).