Trust
Security at Lionhouse
Last updated: 13 October 2026
Lionhouse builds security, observability, and compliance software, so we hold our own systems to the same standard. This page explains our approach and how to report a vulnerability.
Our approach
- Deployment options that keep customer data in your own environment: self-hosted, dedicated VPC, or air-gapped.
- Single sign-on (SAML / OIDC) and role-based access across the product suite.
- Encryption in transit (TLS) for all public endpoints, including this website.
- Strict separation of customer tenants, with no cross-tenant data pooling.
Compliance documentation
Security questionnaires, architecture documentation, and the current status of our compliance programs are available to prospective customers on request. Email security@lionhouse.dev.
Vulnerability disclosure
If you believe you have found a security vulnerability in lionhouse.dev or any Lionhouse product, email security@lionhouse.dev with a description, the affected URL or component, and steps to reproduce.
- We will acknowledge your report within 3 business days and keep you informed of progress.
- Please give us reasonable time to fix the issue before disclosing it publicly.
- Do not access or modify other users’ data, degrade service, or use social engineering or physical attacks.
- We will not pursue legal action against good-faith research that follows this policy.
Machine-readable contact details are published at /.well-known/security.txt.