Security & Trust

Augustus acts inside your business systems, so trust is the product. Here is how the platform is built to keep you in control and your data isolated.

Tenant isolation

Every customer workspace is a hard tenancy boundary. Data is isolated at the database level with Postgres row-level security — not just application filtering — so one workspace can never read another’s rows. Third-party customer data lives in a Supabase project dedicated to the product, separate from our internal systems.

Credential encryption

Keys and tokens you add to your Environment are sealed with AES-256-GCM before they ever reach the database; the stored value is ciphertext only, and plaintext exists solely in memory at the moment of use. Connection status is visible in the product; secrets are never shown again after you save them.

Human-in-the-loop and reversibility

The agent proposes before it acts. Every change is previewed (a dry run), classified by risk, and — for anything consequential — held for your explicit approval. Reversible actions can be undone; irreversible ones (sending a message, moving money) are queued with a cancel window rather than fired blindly. While a system is in testing, it touches nothing real.

Controls

Role-based access (owner, admin, approver, viewer), an emergency stop that halts all live activity, per-workspace spend caps, and an immutable audit log of consequential events. You can export or delete your workspace data at any time.

Infrastructure

The application runs on Vercel; data and authentication on Supabase; payments on Stripe. Model inference runs on Anthropic and OpenAI. Your business data is not used to train shared models. See the full subprocessor list in our Privacy Policy.

Responsible disclosure

Found a vulnerability? Please report it to security@augustus.so. We investigate all reports and will work with you on a fix.