trust

last updated 2026-05-10 · phase 0 private alpha · operated by flndrn Limited (Cyprus)

where data lives

briven runs on a dedicated Hostinger KVM in Frankfurt (eu-west-1). Customer databases live in a shared Postgres 17 cluster (pgvector enabled) with one schema per project — every query is scoped to the project's schema at the application layer plus search_path at the connection layer. Team-tier projects graduate to a dedicated cluster.

encryption

• TLS 1.3 on every public endpoint, Let's Encrypt auto-renewed.
• Per-project env vars: AES-256-GCM at rest with a platform-held KEK.
• Session cookies: HTTP-only, SameSite=Lax, Secure in production.
• API keys: SHA-256 hashed, only the last 4 characters kept for display.

backups

pg_dump nightly to off-box object storage (Backblaze B2), 30-day retention. Restore drills monthly. Point-in-time recovery arrives in Phase 3.

access

SSH to the control-plane host is key-only; root password auth is disabled. Every platform-level mutation (deploy, member change, env edit, key revoke) is written to an append-only audit log tied to the authenticated actor. IPs are hashed before storage per our privacy policy.

incident disclosure

We will disclose incidents that affect customer data within 72 hours of detection to affected accounts and will publish a post-mortem here within 30 days. No incidents to report yet.

open source

briven-core is AGPL-3.0. The CLI and client SDKs are MIT. Source lives at code.konnos.org/flndrn/briven.