Cloud, planned: an address and backup space, never your twin.

• Free comes first. Every paid convenience has a free, documented route, and the free route ships first.
• Nothing moves behind the paywall. Nothing the open-source version does today will ever need a subscription.
• No account, ever, to use Mirrin. Cloud won't have a sign-up, login, password or email account with us either: you'd be an account number, tied to a key your computer makes for itself.
• We don't host twins. Not yours, not anyone's.
• The twin never pitches Cloud. No persona will mention it. Cloud will appear only where you ask for the capability, such as choosing how your twin is reached or where backups go, and it will be listed last. If a subscription lapses you'd get one calm line, never a push notification.
• No trial, no countdowns. A 30-day refund instead.
• The code stays open. The twin and everything Cloud would run are open source, with the licences explained in plain words.

Every paid convenience has a free route, and the free route came first. All of these are part of the free, open-source version, in the first release. The parts that run on a phone are still being tested on real phones, and say so.

• Being tested A web app you add to your Home Screen (no app store). Scan one QR code on your computer and watch each step light up as your phone joins. Every device gets its own key, and you can revoke any of them. Each new device is announced on your channels, with a way to revoke it if it wasn't you.
• Being tested Lock-screen approvals. Your machine sends the notification itself, encrypted, straight to Apple's, Google's, Mozilla's or Microsoft's push service. No server of ours in between. Tap it to see the picture and decide.
• Being tested A passkey for the dangerous ones: Face ID, a fingerprint or your device PIN. Approving a payment, a command or a call from the phone needs it, and the web app refuses dangerous approvals until you've set one up. Replying yes 12 in your own chat keeps working as it does today.
• Available now Reach from anywhere, your way. Secure access through Tailscale, your own certificate, or your own relay on your own domain. The relay is open source.
• Available now Encrypted backup. To a folder, iCloud Drive or any S3-compatible bucket, locked with 12 words only you hold.

Cloud would be $6 a month or $60 a year, and the first 500 subscribers would pay $48 a year for as long as they stay. Supporter would be $20 a month: everything in Cloud, plus next-business-day support, for people who want to fund the free version. Free stays the whole twin.

Fair use would be about 100 GB relayed a month, and up to 20 Mbit/s for your address, shared by all its connections. No trial, a 30-day refund, and no lifetime deals.

The tiers side by side, with Free as the longest column, the licences in plain words, and what we would and couldn't see with a command to check each line, are on the pricing page.

Your computer will connect out to two relays we'd run, with two different hosting providers. When your phone opens your address, a relay will read only the name on the envelope and pass the still-sealed connection through to your computer. The encryption will end on your computer, with a certificate only your computer holds. The relays will never hold a key that could open it.

The relay is the same program you can run yourself, free, today: mirrin reach use relay points your twin at it, with no MavrkAI server involved.

We wouldn't store your email address. It would stay with the payment provider that handles checkout.

Raw connection records would be kept in memory for 72 hours, then only as hourly totals for 30 days. We'd never log what's inside a connection. mirrin cloud me would show every field we store about you. Each line, with why we couldn't see it and a command to check, is on the pricing page.

Promises should come with a way to check them. You can check a download, your address and your backups today, for free. The Cloud checks would answer once Cloud opens.

• Available now Every release after 0.2.0 lists its files' checksums in SHA256SUMS, signed with Sigstore by the release workflow, and the installers check them. To check a download yourself, open a terminal in the folder you downloaded it to. On a Mac or Linux, this checks the signature (with cosign installed) and then the checksums:
  macOS and LinuxCopy

  wf='^https://github\.com/MavrkAI/Mirrin/\.github/workflows/release\.yml'
  cosign verify-blob SHA256SUMS --bundle SHA256SUMS.sigstore.json \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-identity-regexp "$wf@refs/tags/v"
  shasum -a 256 -c SHA256SUMS --ignore-missing

  On Windows, put the name of the file you downloaded on the first line. The last line prints True when the file matches its checksum:
  Windows PowerShellCopy

  $f = 'mirrin-windows-amd64.exe'
  $want = (-split (Select-String -SimpleMatch $f SHA256SUMS).Line)[0]
  (Get-FileHash $f).Hash -eq $want

• Available now mirrin reach verify and mirrin reach fingerprint show the key your address presents. Compare it with what the rest of the world sees:

  openssl s_client -servername <your address> -connect <your address>:443

• Today Search for your address on crt.sh, a public log anyone can read, to see every certificate ever issued for it.
• Available now mirrin backup key --age prints your backup key, so you can decrypt a copy with the standard age tool, without us.
• Available now The relay is open for you to read, on GitHub: about 4,200 lines of code.
• Planned · not on sale mirrin cloud me will show every field we store about you. The command is already built; it has nothing to ask until Cloud opens.
• Planned · not on sale mirrin cloud egress will list every request your machine has sent us: method, path and size, never the contents.

An automated test already checks that a default install sends nothing to Cloud.

You should be able to leave in an afternoon, without asking us. The way out is ready today:

1. mirrin backup migrate --from cloud --to <place> copies every backup, byte for byte, to a folder, iCloud Drive or a bucket of yours.
2. Run your own relay. It is one container.
3. mirrin reach use relay points your twin at it.
4. Pair your phone again. A new address means adding the web app again, and setting up notifications and your passkey again.
5. Cancel with mirrin cloud billing, and mirrin cloud delete-account if you want the record gone.

Your twin carries on after you cancel. Your address would keep working for up to seven days past the end of your paid period, then your free route takes over. New backups wouldn't be stored after the paid period ends, but for 90 days after it you could still list and download every backup. Your address would never be passed to anyone else. Delete your Cloud record and you'd have seven days to change your mind; after that the records, DNS entries and stored backups would be removed.

Cloud will only ever sell availability, so a shutdown would take nothing from your twin. It keeps running on your computer. Your backups will be in a standard encrypted format (age) that your 12 words unlock without us. Everything Cloud runs is open source, so anyone could run the same thing. Your computer's Cloud pass will be a signed token it checks itself, valid for up to 35 days: if the servers that manage subscriptions went quiet, you wouldn't notice for weeks.