Security

All traffic to repowise.dev and our API is TLS 1.2+ enforced. Source code is cloned only over HTTPS or signed GitHub App installation tokens; no SSH keys leave your environment.

The primary database (managed Postgres) is encrypted at rest. Integration credentials (OAuth tokens for connected Git hosts and Jira / Confluence, and webhook signing secrets) are additionally encrypted with application-level keys before being written. GitHub App installation tokens are short-lived (one hour) and minted on demand from the app key held in our secret store.

Each indexing run executes inside an ephemeral, isolated container with no persistent disk and no network access to other tenants. The cloned working tree is wiped at container exit; only the derived artifacts (graph, wiki pages, hotspots, decisions) persist to your tenant's rows.

Access to a snapshot is gated on the authenticated user's ownership of the underlying repository. Workspaces add explicit membership. Production database access is limited to a small set of named engineers and is logged.

API keys (where available) are scoped, revocable, and rate-limited. Keys are shown to you exactly once at creation; we store only a one-way hash.

Service-to-service credentials live in our hosting providers' secret stores, never in source. We rotate provider keys quarterly and immediately on any suspected exposure.

If you believe you have found a security issue, please email security@repowise.dev with steps to reproduce. We acknowledge reports within 2 business days and aim to remediate critical issues within 7 days. Please give us a reasonable window before public disclosure; we credit good-faith reporters in release notes.

On detection of a confirmed incident affecting customer data, we will notify affected customers without undue delay (and, where required, within statutory breach-notification windows) with a description of the incident, scope, and remediation.

Enterprise runs entirely inside your perimeter. Repowise never receives, stores or processes your code or data, so the deployment sits under your own controls and certifications. Repowise Hosted is reviewed directly against your security questionnaire. Enterprise customers also get a DPA and the right to audit our security practices. Request any of these at security@repowise.dev.

For organisations with strict data-residency or air-gap requirements, the OSS CLI runs entirely inside your infrastructure and inherits your controls. Your code never leaves your network. See the GitHub repository for installation and operation guides.