Semvane treats repository access, tenant boundaries and human approval as foundations of the product. This page describes how the platform works today.
The recommended way to connect is the Semvane GitHub App: you choose the repositories, and each task runs with an installation token that expires within an hour and is limited to one repository and to the permissions that task needs. GitHub's webhook deliveries are signature-checked. As an advanced option you can connect a Personal Access Token instead; it is encrypted at rest with ASP.NET Core Data Protection and only used server-side.
Per-repository, least-privilege tokens
Encrypted at rest
Uninstall or revoke anytime in GitHub
Verification and execution
Customer code does not execute inside the control plane. The default verification runner is deterministic: it records a simulated result and runs no build or test commands. Isolated sandbox execution is on the roadmap and not yet available.
No customer code runs by default
Simulated results are labelled as such
Sandbox isolation: planned
Tenant isolation
Organizations share a schema keyed by TenantId. Tenant-owned queries are filtered automatically and fail closed when no tenant is resolved, and every endpoint checks membership and role.
Fail-closed query filters
Role-based permissions
Platform admin role for operators
Sessions and abuse protection
Access tokens are short-lived and refresh tokens rotate on every use and are revoked on sign-out. Public endpoints such as sign-in and the contact form are rate limited.
Rotating refresh tokens
Rate limiting
Password reset via emailed link only
Human control
Semvane prepares migrations and opens draft pull requests. Developers remain responsible for review, approval and merge decisions.