Organizations and billing
Billing, quotas and members belong to an organization. Inside it, projects keep environments apart, such as production, staging or a client. Each host belongs to one project.
org list prints your organization's profile, its current plan and how much of
its quota is used. To enroll a host into a particular project, run
safegrd enroll --project <id-or-slug>. Without --project, the
host goes into the organization's default project. If your credential can see more than one
organization, name the one you mean with --org.
Signing in
| Command | When |
|---|---|
| safegrd login | Interactive. Opens a browser to confirm the session. --no-browser prints the URL instead. |
| safegrd login --token sg_pat_... | CI and headless hosts. A personal access token, non-interactive. |
| safegrd enroll --token ... | Registering a host rather than a person. A personal access token registers a new host. A node token belongs to one host and can only re-enroll that host. |
You create and revoke tokens in the console under Tokens.
To create a token, or to authorize safegrd login in the browser, you enter your
password again. Someone who finds your console open cannot make a token without it. SafeGrd
also emails you when a token is created in the console. If you get that email for a token
you did not create, revoke the token and change your password.
Two-factor sign-in
Turn it on under Settings, in Two-factor sign-in:
- Enter your password. An account made by a Google or GitHub sign-in has no password. If you have not signed in recently, the console asks you to sign in with the provider again.
- Scan the QR code with an authenticator app (1Password, Google Authenticator, Authy or similar), or type the key it shows.
- Enter the 6-digit code the app shows.
- Save the ten recovery codes. They are shown only once. If you lose the app, each code signs you in one time. New recovery codes replaces the whole set.
Turning two-factor on signs out every other session. From then on, sign-in asks for a code after the password. The console also asks for a code before you:
- delete anything
- create an access token
- authorize
safegrd login - cancel a subscription
- change an organization's sign-in rules
One code covers those actions for five minutes. After five codes in one minute, you have to wait a minute before the next. A password reset does not turn two-factor off, except on an account whose address was never verified.
When you enter a code at sign-in, you can tick Remember this browser for 30 days. For the next 30 days, that browser asks only for the password or the provider. Signing out does not forget the browser, so leave the box unticked on a shared computer. Every browser asks for the code again after a password reset, after you sign out everywhere, and after you turn two-factor off or on again. A remembered browser still asks for a code before you delete something or take another of the actions listed above.
An owner or admin who has two-factor on can require it for every member of the organization, from the same card. A member who has not set it up is sent to the setup step at sign-in and cannot use the console until they finish. While the rule is on, members cannot turn two-factor off. Ask for a code at every sign-in stops members from using remembered browsers, including browsers they had already chosen to remember.
Personal access tokens and node tokens are never asked for a code, so the CLI and enrolled hosts keep working when you turn the rule on.
Google and GitHub
If the server has them configured, the sign-in and sign-up pages offer Google and GitHub. SafeGrd accepts only an address the provider has verified (for GitHub, the primary address). What happens next depends on the address.
- If SafeGrd already has an account for the address, you sign in to that account and the provider is linked to it. Later sign-ins follow the link even if your address at the provider changes. For a Gmail address, or a Google Workspace account on the address's own domain, the link is made straight away. For any other address, SafeGrd emails a link to confirm, and the provider is linked once you open it and press Link. If the account's address was never verified, the provider is not linked. Use Forgot password first. That link verifies the address and ends the sessions, access tokens and two-factor set up before it. Then the provider links.
- If SafeGrd has never seen the address, it creates a new account with its own organization, as a sign-up would. The account has no password.
- An invitation does not create an account. To join with Google or GitHub, sign in with the invited address first, then open the invitation link and accept.
An account without a password confirms sensitive actions (creating a token, authorizing
safegrd login, turning two-factor on) with a 6-digit code mailed to its address.
The code works once, for 10 minutes. With two-factor on, a code from the authenticator
confirms these actions instead, and turning two-factor off takes that code alone. Signing in
with the provider again does not count as confirmation, because a browser already signed in
to Google or GitHub comes straight back without asking.
To add a password, press Email me a link under Settings, or use Forgot password on the sign-in page. After that, you can sign in with either the password or the provider.
Sign-in methods in Settings lists the Google and GitHub accounts linked to yours. Unlink removes one. If you later sign in with it from the same verified address, it links again, after the email confirmation where one is needed. You cannot unlink a provider in two cases: the provider created your account and you have not set a password yet, or your organization requires that provider.
Sign out everywhere ends every console session, including this one, and makes every remembered browser ask for the code again. Access tokens keep working, so review them under Tokens.
Require Google or GitHub
An owner or admin can require members to sign in with Google, or with GitHub, under Two-factor sign-in in Settings. You have to be signed in that way to set the rule. Password sign-in then stops working for the organization's members, and a session signed in another way is sent back to sign in. Personal access tokens and node tokens are not affected. Two-factor still applies: with it on, a provider sign-in asks for a code too.
An account signs in one way at a time. So a person cannot belong to one organization that requires Google and another that requires GitHub. SafeGrd refuses the invitation, or the rule, that would cause that.
With Google required, you can name the Google Workspace domain the accounts have to belong to,
such as example.com. SafeGrd then refuses a sign-in from another domain or from a
consumer Google account, and an invitation to an address outside the domain. Your own address
and every member's have to be in the domain before you can set it.
Members of an organization that requires a provider get a session of 1 day instead of 7. If the provider suspends an account, that account loses the console within a day, and its next sign-in goes through the provider again.
Expiry and scope
A new personal access token expires after 90 days. The console shows the date and warns you two weeks before. You can set a shorter lifetime when you create a token, but you cannot make one that never expires. Tokens created before this rule have no expiry date and keep working.
You can also limit a token to one organization or one project. The token then reaches only that organization or project, whatever your account itself can reach. A token limited to a host's project can reach only that project if it leaks.
Plans and quotas
The pricing page lists each plan, what it includes and its price. The
same list is at /api/v1/plans, and SafeGrd enforces exactly what it lists.
Paid plans differ by how often and how thoroughly they test a restore. The only thing a plan meters is hosted storage, the bytes SafeGrd keeps locked for you. Paid plans do not count surfaces (databases, file trees or mailboxes) or team members, and every paid plan backs up hourly. The free plan is for one person and one surface, backed up daily to hosted storage. Backups to your own bucket are never metered.
The trial, and the free floor
During the 14-day trial, you get Growth’s Fire Drills. If the trial ends without an active subscription, your organization moves to the free plan.
On the free plan, your backups stay encrypted and locked, and a Fire Drill runs on them once a week, in memory. The pricing page lists how many surfaces it covers. Any organization without a paid plan is on the free plan, whether its trial expired or its subscription was paused or canceled.
What lapsing does not do
A billing failure never stops a backup.
If your subscription lapses, every surface you already have keeps backing up, and everyone already in the organization keeps their access. Only new surfaces and new team members are blocked. Snapshots in your own bucket stay there, under your Object Lock, whatever happens to the subscription or to SafeGrd. With a customer-managed key, you can read them with your key without SafeGrd.
Your plan changes when SafeGrd receives the payment provider's signed webhook. Returning from the checkout page does not change it.
Team members
Owners and admins invite people from Settings, Team members. You can invite someone as an admin, a member, a viewer or an auditor. Team members are included on every paid plan and during the trial.
An auditor is someone outside the team who checks that the backups were tested. An auditor
can sign in and see the organization's drill records, each drill's signed certificate and the
Evidence Pack. They cannot see surfaces, hosts, snapshots, storage, members or settings, and
they get no button that starts or changes anything. An auditor's personal access token reads
the same records, so they can run safegrd verify history to verify the chain on
their own machine. Only an owner or admin can invite an auditor.
How an invitation works:
- The invited address gets an email with a link that works for 7 days. Until the person accepts, the list shows the address as Invited, and it has no access to the organization.
- Someone who already has a SafeGrd account accepts while signed in as that address. Someone without one creates an account on the link's page, and joins with no organization of their own.
- Resend mails a new link, and the old one stops working. Revoke cancels the invitation. The person can also decline from the link.
- A plan without team members refuses new invitations. It also refuses an invitation sent before the plan changed, when the person tries to accept it. Members who already joined stay.
Two switches on Settings, Security control what members can do. Owners and admins can always do both.
- Members can invite people lets a member invite members and viewers, but never an admin. It is off in a new organization.
- Members can create projects is on in a new organization.
An organization created before 17 October 2026 has both switches off until an owner or admin turns them on.
The owner
The account that created an organization owns it. You cannot hand ownership to another member yet. Each account owns one organization, so after you delete it, the same account cannot create another.
Invoices and the card on file
Under Billing, the owner sees the card that renewals are charged to and every invoice, with a PDF to download. To replace the card, click Update, which opens the payment provider's form. The payment provider emails a receipt for each charge. It issues no PDF for a $0 invoice.
Deleting an organization
- If your backups are on hosted storage, copy the ones you want to keep with
safegrd export. After the organization is deleted, you cannot download them. - Decommission every host under Nodes, and cancel the subscription under Billing. SafeGrd refuses the delete until both are done, and tells you which one is left.
- Under Settings, choose Delete organization and type its name.
The organization is removed from SafeGrd straight away, and you are signed out. Backups already written stay in their storage. We keep the organization's records for 12 months so it can be restored, then erase them. To have them erased sooner, write to support@safegrd.dev, and we erase them within 30 days (Privacy Notice).