Enterprise
Your AI key, or your own cloud
Many security teams will approve a tool without a certificate if the sensitive part runs under their own contracts. These two options are for them.
Option 1: bring your own AI key
- Scans for your organisation call the AI provider with your own Anthropic API key.
- The AI traffic falls under your agreement with the provider, including any zero-data-retention terms you have.
- You see and cap the AI spend in your own provider console.
- VizRepo still never stores your source code. Your key is encrypted with AES-256-GCM.
Option 2: self-hosted
- VizRepo runs in your cloud account or data centre: an API service, a web app and a MongoDB database.
- Your code never leaves your network except for calls to the AI provider you choose, with your key.
- You control updates, backups, access and retention.
- Full details on the self-hosted page at /self-hosted.
Which one fits
| Need | Standard cloud | Own AI key | Self-hosted |
|---|---|---|---|
| Source code not stored by the vendor | Yes | Yes | Yes |
| AI traffic under your own provider contract | No | Yes | Yes |
| Code never touches vendor servers | No | No | Yes |
| Setup effort | Minutes | Minutes | A guided installation |
How to get it
Both options are part of Enterprise and are set up with you. Write to info@vizrepo.com with your requirements, or use Talk to Sales. We will tell you plainly what is ready today and what needs work for your setup.
Questions
- Is this self-serve?
- Not yet. Both options are arranged with us on the Enterprise plan.
- Which AI providers are supported?
- Anthropic Claude is the default and recommended model family. OpenAI is supported as a fallback for lighter tasks.
- Do you need access to our self-hosted instance?
- No. Support can be done over calls and logs you choose to share.
Try it on your own repository
Connect a repo, run one scan, and read what each endpoint does. Starter is free. Pro has a 14-day free trial.