Enterprise security for
autonomous coding agents.
FlukeBase protects your source code, runtime credentials, and agent sessions with strict tenant boundaries, human approval gates, and zero model training on your data.
Data Isolation & Privacy
Strict logical separation across every tenant. Every memory, session transcript, and secret is isolated by project ID. Your code and prompts are never shared across tenants.
Zero AI Training
We do not train, fine-tune, or evaluate models on your code, prompts, or session memories. Your intellectual property remains solely yours.
Approval Gates & Audit Logs
Prevent runaway agent ops. Destructive database migrations, production pushes, and payment events can require human approval, with every action logged in an immutable audit trail.
1. Deployment Architecture & Data Residency
FlukeBase is compiled into a single Go binary that can be operated under two distinct models:
Managed Cloud
Multi-tenant SaaS hosted on certified infrastructure located in the European Union (Germany/Finland) and North America. Logical segregation enforced at database and application layers.
Self-Hosted / Single-Tenant
Deploy the identical binary inside your own VPC via Docker, Docker Swarm, or Kubernetes. Zero outbound telemetry; 100% of data remains within your sovereign network boundary.
2. Encryption Standards & Secret Vaults
- ✓ In Transit: All HTTP and WebSocket traffic is protected via TLS 1.3 / TLS 1.2 with HSTS enforced. Legacy ciphers are disabled.
- ✓ At Rest: Persistent volumes and PostgreSQL databases are encrypted with AES-256.
- ✓ Cryptographic Vault: LLM provider keys, git tokens, and external integration credentials are encrypted using AES-256-GCM authenticated encryption. Secrets are never exposed in log outputs, client traces, or error messages.
- ✓ Token Hashing & Rotation: MCP access tokens are stored as one-way SHA-256 hashes; OAuth refresh tokens are automatically rotated upon each exchange.
3. Authentication & Access Control (RBAC)
FlukeBase enforces server-side identity verification on every request. Client-side authentication assertions are never trusted without cryptographic validation.
- • OAuth 2.1 & PKCE: Standard-compliant authorization server implementation supporting RFC 7636 PKCE (S256 mandatory) and RFC 8707 resource indicator scoping.
- • Role-Based Access: Granular permissions (Admin, Member, Viewer, Service Agent) separating sensitive billing and administrative settings from agent task dispatch.
4. Compliance Posture & Standards Alignment
FlukeBase is architected to satisfy SOC 2 Type II Trust Services Criteria (Security, Availability, and Confidentiality) and HIPAA Security Rule safeguards. We are currently completing our formal controls implementation in preparation for our independent third-party SOC 2 Type II assessment.
gosec), dependency vulnerability scans (govulncheck), and race detection prior to merge.
5. Third-Party Subprocessors
For our managed cloud platform, we partner with industry-leading infrastructure providers under strict Data Protection Agreements (DPAs):
| Partner | Purpose | Location | Certifications |
|---|---|---|---|
| Hetzner Online GmbH | Core Compute & Database Hosting | Germany / Finland (EU) | ISO 27001 |
| iDrive Inc. (e2) / AWS | Encrypted Object Storage & Backups | EU / US | SOC 2 Type II, ISO 27001 |
| Stripe, Inc. | Subscription Billing & Payment Processing | United States | PCI-DSS Level 1 |
| Postmark / Resend / Mox | Transactional Email Delivery | EU / US | SOC 2 Type II, GDPR compliant |
6. Responsible Disclosure & Incident Response
We take reports of security vulnerabilities seriously. If you discover a potential vulnerability in FlukeBase, please contact our security team:
We commit to acknowledging receipt within 24 hours and providing an initial severity assessment within 48 hours. We request that you refrain from public disclosure until we have had an opportunity to address the issue.