Sentrail

Sentrail documentation

Getting started

Create a Sentrail project, connect GitHub and Supabase, optionally connect Vercel, and run your first evidence-gated security assessment.

Updated August 17, 2026

Before you start

You need a Sentrail account and access to the systems you want to connect. The person connecting a provider must be able to authorize the relevant GitHub installation, Supabase project, or Vercel account.

  • A GitHub account that can install or use the Sentrail GitHub App.
  • A Supabase account with access to the project you want to audit.
  • A Vercel account if you want deployment posture included.
  • Permission to create or administer the Sentrail project.

Create and connect a project

  1. 01

    Create the project

    From Projects, create a project and open its workspace.
  2. 02

    Connect GitHub

    Install or reuse the GitHub App, grant it access to the intended repository, link that repository, and select the primary repository when more than one is connected.
  3. 03

    Connect Supabase

    Authorize Supabase through OAuth and select the Supabase project that belongs to this application. Sentrail does not ask for a raw database password.
  4. 04

    Connect Vercel

    Optional: authorize the Vercel integration and link the deployment project whose environment and protection posture should be inspected.
  5. 05

    Run readiness

    Open Launch readiness and run the assessment. Missing or stale required evidence is collected when possible before the verdict is computed.

Interpret your first result

  • Ready: every required check has fresh evidence and there are no open critical or high findings.
  • Needs review: evidence is complete, but medium or low findings need a human decision.
  • Blocked: at least one open critical or high finding prevents a ready verdict.
  • Insufficient evidence: a required check is missing, failed, or stale, so Sentrail does not report a score.

What to do next

Open each finding to review its source, severity, evidence, and recommendation. Mark false positives deliberately rather than ignoring them. For an actionable issue, prepare a remediation proposal and review the proposed files, risks, base commit, and verification plan before approval.