Security
Built for teams that care about their code
SREDify needs your engineering history to do its job. Here is how we keep it under your control.
Read-only access
Repository connections only read history. SREDify never pushes code or changes settings.
Your AI keys
Bring your own OpenAI, Anthropic, Google or OpenRouter key, so you control which models see your data.
You stay in control
Every AI suggestion is reviewable. Nothing goes into a draft or export without your approval.
Your data, exportable
Export your claim at any time. AI keys and repository tokens are encrypted, and everything is scoped to your organization.
Security questions
What access do repository connections need?
Read access to the repositories you choose, so the scanner can read commits, pull requests and issues. You can limit which repositories are included in each claim and disconnect at any time.
Where does my data go when the AI runs?
To the AI provider whose key you connect, under your account and their data terms. You pick the provider and model for each task.
How are credentials stored?
AI keys and repository tokens are encrypted before they are stored and are only decrypted on the server when they are needed.
Who in my company can see a claim?
Each business has admin, developer, support and finance roles, so engineers answer technical questions, finance manages the numbers, and everyone sees only what they need.
Start with read-only access
Connect one repository on the free tier and see what SREDify finds.