Security

Three documents. They are written for people doing a security review, not for reassurance.

Summary of the model

Area Position
Transport TLS everywhere, including into build and trial environments
At rest Encrypted volumes and encrypted object storage, per-tenant keys where the storage layer supports them
Secrets Injected into running processes, never written to logs, never returned to the client except at issue time
Tenant boundary Separate credentials, quotas, storage prefixes, log spaces and build concurrency
Build egress Allowlist — only the dependency registries and mock services the build declared
Trial egress Allowlist, single-tenant container, read-only root filesystem
Data at model providers Contracted, not retained beyond the request, not used for training
Analytics on the marketing site None. No third-party scripts, no tracking cookies
Card data Never seen by us — handled entirely by the payment processor
Audit trail Reconstructable from your repository, plus exportable clause-level history

Reporting a security issue

Security issues should be reported to [email protected] rather than through the public channels. We acknowledge within two business days and aim to have a fix or a mitigation plan within a week.

We will not pursue legal action against a researcher who stays within the letter and spirit of this policy: no denial of service, no access to other tenants’ data, no exfiltration, and no social engineering of staff. If you believe you have found a vulnerability that crosses those lines, tell us before you act on it, and we will work with you.

We do not run a bug bounty programme yet. We will when there is a paying customer base to support one.

Scope

These documents describe the platform. The main website is a separate system with its own hardening, described in the Privacy Policy and covered by the same reporting address.