Gantrel
Get started

Security

What is protected, and what is yours

This is source code you run, so we say plainly where the platform helps and where the review is yours.

Tenant isolation fails closed

Every workspace-owned collection carries an organisation id and a model plugin refuses a query that does not name one, and an update that tries to move a row to another workspace. A test enumerates every model.

Read the guide

Sessions you control

Cookies are signed, HTTP-only and secure in production. People see each device, end any session, and every sign-in and failure is recorded for 90 days.

Read the guide

Step-up for the risky moments

Creating or rotating a key, revealing a webhook secret and transferring ownership ask for the password or a code again, valid for ten minutes.

Read the guide

Roles that cannot grant more than they hold

Permissions are checked on the server for every action. API keys are capped by the role of the person who made them, and can expire or be limited to addresses.

Read the guide

Outgoing calls are guarded

Webhooks, payment gateways, AI and OAuth requests go through a fetch that refuses private, loopback and metadata addresses. Webhook bodies are HMAC-signed.

Read the guide

Money paths are race-tested

Renewals, seat changes, coupons and credit are claimed with conditional updates, so two runners never charge a period twice.

Read the guide

Everything privileged leaves a trail

Console actions, role changes, exports and impersonation are written to the audit log with the actor. Impersonation is view-only by default.

Read the guide

Secrets stay out of the repo

Keys live in environment variables. Live calls to paid providers need both a key and an explicit switch; tests always refuse them.

Read the guide

Yours to review

  • Your own models and routes: use the generator and the tenant plugin.
  • Secrets management, backups and rate limits at your proxy.
  • A security review and your own penetration test before taking real money.
  • The legal pages: the shipped terms and privacy text are templates, not legal advice.

Found a problem? Write to the contact on the contact page. The production checklist lists what to do before launch.