Appearance
Accounts & Licensing
Clusto requires a license. This page covers creating a Clusto account, claiming the permanently free Personal plan, buying Pro or Team, activating the desktop and mobile apps, signing in on the web client, managing devices, and what happens when a license goes offline, expires, or is revoked.
Accounts
- Register at clusto.app/register. Public registration does not require an invitation or access code during normal operation. Registration and password management always happen on the website, not in the app. Open the verification link Clusto emails after registration before signing in. An unverified account cannot sign in with email and password or claim the Personal plan.
- Manage your account, license, and devices at clusto.app/account.
- Sign in inside the app from the full-screen license gate shown on first launch, or later via Settings > Account. Sign in with your email and password, with Continue with GitHub, or with Sign in with browser (see Signing in with the browser).
Clusto may temporarily require an access code for new registrations during an abuse or service incident. If the registration page asks for one, new sign-ups are temporarily restricted until public registration reopens. Existing account holders can continue to sign in normally.
Using the website on smaller screens
On a phone or narrow window, open the navigation menu to reach Account and the other website pages. Press Escape to close the menu and return keyboard focus to its button.
Administrators can switch sections using the tabs on the admin page. Wide tables scroll horizontally within their own area so all columns and row actions remain available. With a keyboard, tab to the table's scroll area and use the arrow keys to reach columns outside the current view.
Signing in with GitHub
Continue with GitHub works everywhere: the web client, and the desktop and mobile apps.
- Web client - runs on its own site, web.clusto.app. It opens the Clusto sign-in page on clusto.app, which sends you to GitHub, and then returns to the web client with a one-time code that only the browser that started the sign-in can redeem (the same PKCE exchange as the apps, below). This is how accounts with two-factor authentication sign in on the web (or use Sign in with browser, described below).
- Desktop / mobile app - opens your system browser to complete the GitHub sign-in, then hands the session back to the app automatically over a
clusto://link. Approve the prompt to reopen Clusto if your browser asks. Once signed in, a device with an available license seat is activated automatically, same as an email sign-in.
The callback never carries your Clusto session token. The app or web client creates an unpredictable sign-in state and a PKCE verifier before opening the browser. After GitHub sign-in, the browser returns a one-time code that is bound to that PKCE challenge and expires after two minutes. The app checks the returned state, then exchanges the code over HTTPS. Reusing the code, presenting it from another client, or exchanging it without the verifier fails.
On Android and iOS, a successful sign-in should leave the browser and reopen Clusto. If the browser remains on the website, or Clusto reopens but stays signed out, update Clusto to the latest version and try again. Older mobile builds did not handle the browser callback correctly.
GitHub sign-in reuses an existing Clusto account with the same GitHub-verified email. Creating a brand-new account still goes through public registration; GitHub sign-in does not create a new account automatically.
Linking GitHub with repository access, so the GitHub view can reuse the sign-in as its token, is a separate step at clusto.app/account/connect-github that grants the repo and read:org scopes. The GitHub account must have the same email as the Clusto account. See Account Cloud Sync for how the token is stored.
The OAuth bridge keeps an allowlisted legacy route for the old Hive client. Clusto explicitly selects the clusto:// callback and Android package dev.vazac.clusto; omitted or unknown client values stay on the legacy route instead of becoming arbitrary deep-link schemes.
Signing in with the browser
The desktop, mobile, and web apps show a Sign in with browser button next to Continue with GitHub, in Settings > Account and on the sign-in gate. It opens clusto.app, where you sign in the usual way (password plus your 2FA code, a passkey, or GitHub) and then confirm Continue as followed by your email. The app is then signed in. Use it for any account with two-factor authentication on: typing your email and password into the app itself cannot answer the 2FA code. It is free on every plan.
Managing your password
Signed-in users can manage their password on the account page:
- If you joined with GitHub and do not have a Clusto password, enter and confirm a password under Password, then click Set password. Passwords must be 10 to 128 characters. You can then sign in with either your email and password or GitHub. Setting a password asks you to sign in again first (see below).
- If your account already has a password, click Reset password. Clusto sends a secure reset link to your account email so you can choose a new password. Resetting a password signs out every device, apps included, so each one has to sign in again.
Signed-in devices and sessions
A sign-in on a browser, the web client, or a Clusto app lasts 30 days from its last use. Using it again within that time keeps it going; a sign-in nobody uses for 30 days ends, and the app tells you under Settings > Account that you were signed out and asks you to sign in again. Existing sign-ins from before this change end 30 days after the update at the latest.
The Security card on the account page holds, in this order, two-factor authentication, passkeys, and Signed-in devices. The device list shows every browser and Clusto app signed in to your account, with a description such as "Chrome on Windows" or "Clusto app on Android", when it signed in, and when it was last used. The device you are on is marked This device. Use Sign out on a device you do not recognize, or Sign out all other devices to keep only this one. Neither asks you to sign in again, and a device you sign out must sign in again before its next request. If you see a device you do not recognize, sign it out and change your password. The list never shows IP addresses or session tokens. The list is paged, 5 devices per page, with this device first.
Confirming it's you
A few changes need a sign-in from the last 10 minutes: deleting your account, setting a password, opening billing, changing your GitHub connection, replacing the license key, changing two-factor authentication, and adding or removing a passkey. If your sign-in is older, Clusto asks you to sign in again first with any method (your password, GitHub, or a passkey), then lets you continue. A sign-in handed to a Clusto app or the web client through the browser approval never counts as recent, so make these changes on the website. If you cancel the prompt you are signed out of that browser.
Two-factor authentication
Two-factor authentication (TOTP) is available to every account on every plan, Personal included. Under Security on the account page, click to turn it on and follow the step-by-step dialog:
- Intro. A short explanation of what you are about to set up.
- Scan the QR code with any authenticator app. If you cannot scan it, type the setup key by hand or open the
otpauthlink on the same device. - Enter the 6-digit code your app shows.
- Save your 10 backup codes. Each works once. Copy or download them, then tick I have saved my backup codes to finish.
Starting setup needs a sign-in from the last 10 minutes, made with any method (password, GitHub, or passkey). GitHub and passkey users are not asked for a password. New accounts are offered the setup once right after sign-up, and you can skip it. Clusto emails you when two-factor authentication is turned on or off.
To turn it off or create a fresh set of backup codes (which cancels the old ones), enter a current authenticator code or a backup code.
Once it is on, signing in with your password on the website asks for the 6-digit code or a backup code. Ten wrong codes lock that account's two-factor sign-in for 15 minutes. Signing in with GitHub or a passkey does not use the code.
The desktop and mobile apps and the web client cannot ask for the code when you type your email and password into them. For an account with two-factor authentication on, use Sign in with browser (or Continue with GitHub). Administrator accounts must have two-factor authentication to use the admin panel, and the panel asks for a fresh code every 12 hours, even after a passkey sign-in.
Passkeys
A passkey signs you in with a fingerprint, face, device PIN, or security key instead of a password. Under Security > Passkeys on the account page you can add and remove passkeys. Adding or removing one needs a sign-in from the last 10 minutes and emails the account owner.
To sign in, click Sign in with a passkey on the login page, or pick the passkey your browser suggests in the email field. A passkey sign-in skips the two-factor code step, like GitHub. The Confirm it's you dialog can also use a passkey. Passkeys are free on every plan.
Transactional emails
Clusto sends account and sign-up messages, password resets, team invitations, and license notices from Clusto noreply@clusto.app. Replies are directed to the monitored support@clusto.app address. If an expected message does not arrive, check your spam folder and allow messages from noreply@clusto.app before requesting it again.
OpenRouter API key
Open Settings > Account > OpenRouter API, or press F1 and run Configure OpenRouter API key. This credential is independent of your Clusto account sign-in. One saved key is used by native OpenRouter chats and teams across the whole cluster. There is no node picker and no need to configure each node separately.
The key is write-only. Clusto reports whether the connected node is using the shared cluster key or a local environment fallback, but it never sends either value back to the app. Saving or replacing the key distributes it to every connected node and applies it to the next OpenRouter turn without restarting any daemon. A node that is offline during the change receives the latest value when it reconnects.
Clear stored key removes the shared key cluster-wide with the same immediate and reconnect-safe behavior. A node-level OPENROUTER_API_KEY is only a local fallback when no cluster key exists. Environment keys are not distributed and must be changed in each node's service environment. See Native OpenRouter API for environment, model, and runtime details.
Free Personal plan
Personal is permanently free for one verified Clusto account and one user. It includes activation on up to 3 devices and ongoing updates.
Claim Personal from clusto.app/pricing or the account page. Your email must be verified first. Claiming the plan creates the license directly and does not open Stripe or ask for payment details.
Earlier Clusto versions issued 14-day trial licenses. Existing trial licenses remain recognized for compatibility and still expire at the end of their original 14-day term. New account and pricing screens offer Personal instead of promoting a new trial.
License keys
New license keys use CLST-XXXX-XXXX-XXXX. Existing HIVE-XXXX-XXXX-XXXX keys remain valid during and after the rename overlap; both prefixes use the same checksum and activation rules. Personal includes one seat and up to 3 devices. Paid Pro and Team licenses carry the seat and device capacity shown at purchase. The web client does not consume a device slot - it checks the license on sign-in instead.
Replacing a license key
If a key may have been shared, the license owner can replace it from the account page with Replace key (it asks you to sign in again first, and is limited to 5 times per hour). The old key stops working immediately and is never accepted again; the new key is shown once.
- Devices activated by signing in keep working and pick up the new key at their next online check.
- Devices activated with the key alone are deactivated and need the new key, or a sign-in, to activate again. The confirmation tells you how many.
- On a Team license the key alone cannot activate a device at all (see below), so after a replacement members simply keep using their sign-ins.
On a Team license the key is also replaced automatically when the owner removes a member or a member leaves, so a departed member's copy of the key stops working. The owner gets an email when a member leaves.
Pro and Team billing
Choose Pro or Team at clusto.app/pricing, then select Monthly or Annual billing. Both paid plans are subscriptions, completed securely on Stripe-hosted Checkout. Personal stays free and is claimed directly without Stripe.
| Plan | Monthly | Annual | Capacity |
|---|---|---|---|
| Pro | EUR 6 | EUR 59 | 1 user, up to 10 devices |
| Team | EUR 15 | EUR 149 | 5 users, up to 99 devices per user |
Every plan, including free Personal, includes end-to-end encrypted Account Cloud Sync of your connection profiles and app settings. Team licenses can also share end-to-end encrypted connection profiles with every member. See Team Profiles.
Team also adds a Team bucket to the Pull requests tab of the GitHub view: open pull requests written by, or waiting on a review from, teammates who linked GitHub to their Clusto account. Teammates see only your display name and GitHub user id. Personal and Pro do not show the bucket.
Plugins are included on every plan, Personal included.
Notes keeps one vault on the free Personal plan. Creating a second vault needs Pro, Team or a trial. If a plan lapses, existing vaults keep working; only creating another one is blocked.
On every plan, including Personal, Settings -> GitHub -> Use my Clusto GitHub sign-in reuses the GitHub account linked to your Clusto account as the GitHub view's token, so you do not have to paste a personal access token. See GitHub.
Paid access lasts through the paid subscription period. Renewal extends that period after payment succeeds. There is no perpetual license or version you can keep using after a paid subscription expires.
Account owners can open the Stripe Customer Portal from the account page to manage payment methods, download invoices, switch plans or billing intervals, and cancel renewal. Cancellation takes effect at the end of the paid period, so access continues until that date.
Clusto activates a purchase only after Stripe verifies that payment succeeded. Returning to the website after Checkout does not activate a license by itself, so allow a short time for payment confirmation if the account page still shows the purchase as processing. A refunded payment, or a payment dispute that revokes the purchase, deactivates the license on its next online validation.
Activating desktop and mobile
The desktop (Windows / Linux / macOS) and mobile (Android) apps must be activated on each device. On first launch a full-screen gate asks for a license; after that, activation lives in Settings > Account. Two paths:
- Sign in with your Clusto account (email/password or Continue with GitHub). The device is activated automatically using the account's license - no key to type.
- Anonymous activation - enter the license key only, no account sign-in. Useful for machines you would rather not tie to an account session. This works on single-seat licenses (Personal and Pro). Team licenses activate devices only by signing in with an account that holds a seat, so the key alone is refused with a message asking for a sign-in.
Activation stores an Ed25519-signed license blob on the device. The signature is verified offline on every launch, so day-to-day use does not need network access to the license server (see Offline behavior below).
How your plan reaches your nodes
Your nodes (the clustod daemons) do not hold your account. The desktop or mobile app hands its signed license to the node it connects to: on connect, after you activate, and after each online re-validation. The node verifies the clusto.app signature, keeps the paid license that runs longest, stores it, and passes it to its peers in the cluster, including a peer that comes back online later.
- A Personal device never downgrades a cluster that already holds a paid license.
- A cancelled plan stops applying at its own deadline, not when you disconnect.
- The web client cannot hand over a license, because it keeps none. Connect once from a desktop or mobile app for the plan to reach the nodes.
- Until a paid license arrives, a node runs with Personal limits. For the Software Factory that is 2 agent slots per runner node and Full auto merging T0 only; paid plans get 8 slots and merging up to T3. See Software factory.
Web client sign-in
The web client at web.clusto.app works differently: there is no device activation on the web. Instead you must sign in with a Clusto account that holds an active license. Without a licensed account, the web app does not let you past the sign-in gate. The web client is its own site, so signing in on clusto.app does not sign you in there; the web client has its own sign-in and keeps a session token in the browser (see Web Client). Old clusto.app/app links redirect to the new address. An account with two-factor authentication on signs in to the web client with Sign in with browser or Continue with GitHub.
Linked nodes
To reach a node through the Clusto Tunnel relay from the web client, the node must be linked to your account. The Clusto app signed in to your account links each node it connects to as an administrator, and a node you can only reach from a browser can be linked with clusto daemon link on that node, which prints a link to open on clusto.app. The account page lists your Linked nodes and lets you Unlink one; an unlinked node is not reachable through the relay until it is linked again. Node linking is free on every plan, and a link only lets the relay route to the node: you still need the node's token to connect. Deleting your account removes its links.
Managing devices
Deactivate a device to free its slot:
- From the account page - clusto.app/account lists every activated device with a deactivate action. Use this for devices you no longer have access to.
- From the app - Settings > Account > Deactivate this device (requires being signed in).
Renaming a device
Each device in the account dashboard has a Rename button next to Deactivate. The license owner can rename any device on the license; a member can rename their own devices. Renaming only changes the label shown in the dashboard - it does not re-activate the device or consume a seat.
On smaller screens, device actions appear below the device details.
The desktop app reports its real machine hostname when it activates, so a new device lands in the list under a recognizable name. Earlier builds could register a generic label such as "linux-device"; rename any of those from the dashboard.
Deleting your account
You can delete your account from the account page. It asks you to sign in again first and to type DELETE to confirm. Deleting removes your account data, including your devices' activations and linked nodes, and cannot be undone.
Deleting also stops billing for every paid subscription you own, before anything is deleted:
- An active or trialing subscription is set to end when the time you paid for runs out. There are no further charges and no refund, and Team members keep access until that date.
- An overdue, unpaid, incomplete, or paused subscription is cancelled right away, without a final invoice.
- A subscription that has already ended, or is already set to end, is left as it is.
If Stripe cannot be reached or refuses the cancellation, nothing is deleted and you are told to try again or write to support@clusto.app, so a deleted account is never charged. The same applies if billing is unavailable. Stripe keeps its own customer and invoice records for tax purposes. Devices that were activated with the account show that the account was deleted when they next check in.
Website and API safeguards
Clusto enforces Personal-plan claims, legacy trial issuance, access-code use, license seats, team invitations, and device capacity in atomic PostgreSQL operations. Concurrent requests cannot claim a second Personal license for an account, mint a second legacy trial, redeem a bounded code too many times, or exceed the seat or device limits shown in the account dashboard. Expired invitations do not consume a seat.
Public and authentication-adjacent endpoints use shared PostgreSQL rate limits with atomic counter updates, so the limits remain effective across multiple website processes. Sensitive auth pages and API responses disable browser caching and referrer forwarding. The website also sends strict transport, content-type, framing, permissions, and Content Security Policy headers.
Offline behavior
- The signed license blob is verified offline, and the app re-validates online periodically in the background.
- Personal has a 30-day offline grace period from the last successful check. After that, reconnect so the app can re-validate the license.
- Pro and Team require an unexpired paid subscription period. The 30-day offline grace never extends access beyond the paid expiry date. Connect after a renewal so the device can download its updated signed license.
- Legacy trials expire 14 days after issue, regardless of offline grace.
- Expiry returns desktop, mobile, and web clients to the license gate even if the app stays open. Leaving a client running does not extend paid access.
Troubleshooting
The app surfaces the license state in Settings > Account and on the license gate. The states you may see:
| State | Meaning | Fix |
|---|---|---|
| Expired | A time-limited license, including a legacy trial, is past its end date. | Claim Personal or renew or buy a paid plan at clusto.app/pricing, then re-activate. |
| Revoked | The license or key was revoked (refund, abuse, key replacement). The next online check picks this up, and the app says why: the owner replaced the key, you were removed from or left the Team license, the device was deactivated, or the account was deleted. | Sign in with an account that has a seat, or enter the new key. On a Team license only a sign-in activates a device. Contact support if the reason is unexpected. |
| Stale | No successful online re-validation within the 30-day grace window. | Get the device online once so it can re-validate; if the device is permanently offline, deactivate and re-activate it. |
| No seats / device limit | Every device slot on the seat is in use. | Deactivate an old device from the account page, then activate again. |
If sign-in fails on the web client with a valid account, check that the account actually holds an active license on the account page - a web sign-in without a license is rejected by design. If the account has two-factor authentication on, use Sign in with browser or Continue with GitHub. If the web client says the node is not linked to your account, see Linked nodes.