SafeGrd console

Protected surfaces
Encrypted snapshots
Threat Shield status
Fire Drill restores
verified

02 / Surfaces

03 / Hosts

01 / Overview

04 / Snapshots

05 / Fire Drills

Each drill restores a snapshot and checks what came back. The result is recorded against the surface.

You are this organization's auditor. Each drill below restored a backup and checked what came back, and SafeGrd signed the record. The Evidence Pack collects them for a period.

Each surface's next drill: when, where, and how often the plan drills. Overdue first.

One cell a day, Monday first, UTC. Filled: a passing drill. Alarm: a failing one.

07 / Access tokens

Tokens authenticate the CLI, GitHub Actions and Kubernetes sidecars. A token can enroll a host, read, and ask for a backup or drill. It cannot delete backups, remove surfaces or change storage.

Token name Key prefix Scope Created at Expires Actions

06 / Projects

Projects group surfaces and set where their backups go. Unlimited on every plan.

Project Slug Status Locks Storage Surfaces Actions

Project storage

SafeGrd-hosted storage, where the plan includes it, or your own S3-compatible bucket. Every snapshot is encrypted before upload, so storage only ever holds ciphertext.

S3 storage

Presets:
Leave it empty for AWS S3. R2, MinIO, Wasabi and others need theirs.

Object Lock
Under compliance mode a backup cannot be deleted before this many days, so this is also a storage bill.
More buckets How copies work

Every backup of this project is also written to each bucket below, under its own key and lock. A bucket that is behind is caught up by the host.

08 / Activity

Key access record

Every key and credential SafeGrd released, to which host and when, and every refusal. Reads of hosted storage are listed there and not in the activity log.

09 / Billing

Every paid plan protects unlimited surfaces. Plans differ in drill cadence, whether a drill loads a real database, and evidence export.

Billing

11 / Help

Guides

Support

Write to support@safegrd.dev, or use the contact form. Paste the diagnostics below into the message: support asks for them first.

They hold no token, key or password.

What's new

Every change to SafeGrd, newest first, is on the changelog.

10 / Settings

Theme

Profile

To change it, write to support@safegrd.dev.

This account signs in with Google or GitHub and has no password. To add one, we email a link to .

At least 12 characters.

Two-factor sign-in

Sign-in methods

Organization

Plan
Protected surfaces
Team members
Organization ID

Security policy

Key access record

Every key and credential SafeGrd released, to which host and when, and every refusal.

Activity log

Sign-ins and changes in this organization, with who made them, are under Activity.

Alerts

SafeGrd alerts you when a backup or drill fails or is blocked, a host goes silent, a surface is overdue or storage runs low, and again when each recovers.

Webhook:
PagerDuty:
Email:

Owners and admins change where alerts go.

A failure or a warning opens an incident on the PagerDuty service, and its recovery resolves it. Where to find the URL in Slack, Discord or Teams, and the key in PagerDuty

Compliance platform

Each Fire Drill record is sent to your compliance platform as signed, dated evidence with a verify link. SafeGrd keeps the API token sealed.

Team members

Name Email Role Sign-in Added Actions

Delete organization

Deleting removes this organization's projects, members and settings, and signs you out. Retire every host and cancel the subscription first. Backups already written stay in their storage. Copy hosted ones out first with safegrd export. 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.

Platform overview

Global telemetry, multi-tenant directory, and early access waitlist across all organizations.