Self-hosting
Security
What Vigie does to keep your telemetry and your app safe.
- Nothing leaves your servers. Vigie sends no telemetry of its own anywhere.
- Secrets are masked at ingest, before anything is stored: secret-named fields, tokens in paths, email addresses and card numbers, plus your own redactors. The Adonis and NestJS packages mask
secretPathsbefore data even leaves your app. - Keys are hashed at rest and shown once: ingest keys (
vk_), API tokens (va_), MCP tokens (vm_) and deploy tokens (vd_). - Sign-up is closed after the first owner, who needs a one-time setup code from the server's logs. Roles: viewer, operator, admin, owner.
- ClickHouse has no published port. Vigie runs as a non-root user, on a read-only filesystem, with no Linux capabilities.
- Your app's database is read-only. Vigie connects with a role that cannot write, and refuses raw SQL if that role can read credentials.
- Actions run as people. Requeueing a task calls your app's API as the person who clicked, so your app's permission checks still apply.
- MCP never returns payloads, only fields and summaries, after masking.
Found a problem? Open a private security advisory on GitHub rather than an issue.