This page states what is true today. It is not a certification. Where a control is planned and not yet in place, it says so.
Hosting#
- Binari products run on Kubernetes clusters we operate on our own hardware, not on a hyperscaler account. The main region is BI-03.
- Images are built once and promoted by digest. Nothing is rebuilt for staging or production.
- Secrets live in Vault and reach workloads through External Secrets. Credentials are never committed to Git or baked into images.
- TLS is issued by cert-manager. Public hostnames sit behind Cloudflare.
Access#
- People sign in with a password and multi-factor authentication, or with Google where a product uses it.
- Integrations get their own service identity and a revocable, scoped access key. They do not use a person's login.
- The API enforces permissions independently of what any interface shows. Denied attempts are recorded.
- Organisation-wide views need an organisation-wide role.
Data#
- Documents are stored once, identified by a SHA-256 fingerprint, and linked to the records they support.
- Audit records hold who, what and when. They do not hold request bodies, query strings or credentials.
- Product data stays inside the tenant and organisation that owns it, enforced with row-level security in PostgreSQL.
- Backups and restore drills are agreed per engagement. There is no automatic offsite backup for Binari Cloud resources yet.
For client engagements#
- You own the code and IP of the paid work. Repositories are yours from day one.
- An NDA is available on request. Contracts use terms your counsel will recognise: IP assignment, confidentiality, GDPR-compliant data handling, defined deliverables.
- We can work inside your SOC 2 or ISO scope and answer your security questionnaire. We do not hold a SOC 2 or ISO 27001 certificate of our own today.
What we do not do#
- We do not sell or share product data.
- We do not load advertising or third-party tracking scripts inside products. The marketing site uses analytics only after consent.
- We do not promise an SLA, a region or a capacity we cannot show running.
Reporting a problem#
Write to [email protected] with "security" in the subject. A senior engineer reads it within one business day.