Security posture, stated plainly.
No badges we haven't earned, no claims we can't demo. This page describes how Relym is actually built; ask us to show any of it live.
Tenant isolation enforced by the database
Every organization's rows are isolated with forced row-level security in Postgres. Application code cannot opt out: queries run inside a per-tenant context, and cross-tenant reads are limited to one audited operator surface.
Credentials are sealed, not stored
Third-party tokens and API keys are encrypted with AES-256-GCM before they reach the database, opened only at the moment of an integration call, and never shown again after saving — not to admins, not in exports, not in logs.
AI acts behind approvals
The agent proposes; your rules decide. Consequential actions — access grants, provisioning, destructive identity operations — sit behind approval chains you configure, and workflow runs pause until a human approves. AI output is labeled and audited like any other actor.
An audit trail that can't be edited
Every significant action lands in an append-only audit log with actor, subject, and timestamp — including operator and support access, which is visible to the customer in their own trail. Filterable in-app, exportable as CSV.
Deletion with a real deadline
Workspace deletion is a deliberate two-step with a 30-day window, after which data is purged permanently across every table — the same window our privacy policy promises. Full-workspace export is available for offboarding and portability.
Encryption in transit, everywhere
All traffic is TLS. Webhooks are signed with rotation grace so receivers can verify authenticity. API access uses scoped keys with per-key rate limits.
Enterprise identity, when you need it
On the Enterprise plan, your team signs in through your own identity provider (SAML SSO — Okta, Entra, Google, or any provider), configured by your admins through a hosted setup portal so we never touch your certificates. SCIM directory sync provisions people as they join and removes their access when they leave; just-in-time provisioning is opt-in for teams that want it. One person can belong to several workspaces and choose which to enter at sign-in.
Questions, disclosures, or a deeper review?
Security questionnaires and architecture walkthroughs are part of every Enterprise conversation. Read the privacy policy for the data-handling details, or contact us directly.