Security at the core. Audited by default.
Every agent runs in its own VM. Every request crosses a zero-trust boundary. Every action is logged, reviewable, and reversible.
Audited, documented, accountable.
Where we stand today - and where we are heading. Status is updated as audits progress. Attestation letters available on request.
SOC 2 Type II
Type I controls mapped; Type II observation window underway with an independent CPA firm.
ISO 27001
Statement of Applicability drafted. Formal certification scheduled once SOC 2 Type II lands.
GDPR
EU-based processing options, DPA available, lawful basis documented per processing activity.
HIPAA
BAA and HIPAA-aligned controls available for healthcare customers on enterprise plans.
Penetration testing
Third-party black-box and grey-box testing each year. Findings tracked to closure in our SDLC.
Encryption everywhere
TLS 1.3 in transit, AES-256 at rest, customer-managed key option on enterprise.
Defense in depth, one layer per concern.
Each layer has its own threat model and its own controls. No single failure exposes customer data.
Identity is verified at the edge and re-verified at every internal hop. Tokens are short-lived, scoped per action, and never reach the sandbox.
Workloads are isolated at the hardware boundary. Each agent gets a fresh VM with its own filesystem, network namespace, and egress allowlist.
Storage is encrypted with rotating keys. Audit logs are immutable and exported to a write-once sink for forensic investigation.
Zero trust, by default.
Every action is authenticated, authorised, and attributable to a real principal - human or machine.
SSO (SAML / OIDC)
Bring your identity provider. Enforce single sign-on across the team workspace, with JIT provisioning supported.
SCIM provisioning
Automate user lifecycle from your IdP. Joiners, movers, and leavers reflected within minutes.
MFA enforced
TOTP and WebAuthn supported. Workspace admins can require MFA for all human principals.
RBAC + audit logs
Granular roles for owners, admins, members, and read-only. Every privileged action is logged and exportable.
Short-lived API tokens
API tokens are scoped, expiring, and rotatable. Long-lived static credentials are not supported by default.
Session lifecycle
Idle and absolute session timeouts. Admins can revoke any active session from the workspace dashboard.
Your code, your data, your control.
We hold customer data with the same posture you would: encrypt by default, minimise retention, prove deletion.
All data is encrypted in transit with TLS 1.3 and at rest with AES-256. Encryption keys are managed by a dedicated KMS with rotation enforced on a quarterly cadence.
Primary processing happens in the EU by default. US, UK, and customer-specified regions are available on enterprise plans. Data residency is contractually documented.
Operational logs are retained for 30 days. Customer-generated artefacts follow the retention policy you configure per workspace, with a hard upper bound enforced by the platform.
On termination, we issue cryptographic erasure within 30 days and deliver a written deletion certificate on request. Backups age out under the same policy.
One VM per agent. Always.
Sandboxes are the hard boundary between an agent and the rest of the world - and between one customer and the next.
Every agent run launches in a fresh micro-VM with its own kernel, filesystem, and network namespace. There is no shared mutable state between sandboxes.
Network egress is allowlist-only and recorded. The sandbox cannot reach internal CodeCourier services and cannot reach another customer's resources - the routing table makes that impossible.
When the run ends, the VM is destroyed. Snapshots are encrypted and namespaced to the originating workspace; they cannot be mounted by anyone else.
Hardened infra, audited continuously.
Production runs on tier-one cloud providers with multi-region redundancy and continuous attack-surface monitoring.
Multi-region cloud
Tier-one cloud providers with primary and standby regions. Documented RPO and RTO for each tier.
DDoS protection
Layer 3, 4, and 7 protection at the edge. Adaptive rate limits keep abuse from reaching origin.
Private networking
Internal services communicate over private VPC links. No production traffic transits the public internet between hops.
Hardware-rooted attestation
Build and deploy pipelines use signed artefacts with attestation traceable back to source commit.
Continuous vulnerability scanning
Dependencies, containers, and infrastructure are scanned continuously. Criticals are patched within 24 hours.
Vendor security reviews
Every subprocessor is reviewed before onboarding and re-reviewed annually. Findings drive contractual controls.
Process is the other half of security.
Strong controls only matter if humans operate them well. Our SDLC and on-call practices are built to keep us honest.
Least-privilege defaults
Engineers start with no production access. Elevated access is time-bound, reviewed, and logged.
Quarterly access reviews
Every access grant is re-justified quarterly. Stale or unused permissions are revoked automatically.
Mandatory code review
No code reaches production without review by a separate engineer. Security-sensitive paths require two reviewers.
Secret management
Secrets live in a Vault-style store with leasing and rotation. Secrets never enter source code or build logs.
Incident response runbook
Documented severities, paging matrix, and customer-notification timelines. Post-mortems are blameless and shared.
Annual tabletop exercises
We rehearse breach, ransomware, and key-compromise scenarios at least once per year, with leadership in the room.
Subprocessors, by category.
We work with a small set of vetted vendors: cloud infrastructure, identity, email delivery, observability, and payment processing. Each one is bound by a written agreement with security and data-processing obligations.
Full subprocessor list - including legal entity, region, and purpose - available on request under NDA.
Request the subprocessor listReport a vulnerability.
We treat researcher reports as a gift. Send us a finding in good faith and we will respond, fix, and credit you.
4AF1 2C9B 7E03 51D4 8A6F 29BD 7C4A 0F12 9E58 B6D3placeholderIn scope: codecourier.dev and subdomains, our SDKs, our published Docker images.
Out of scope: customer code running inside sandboxes, social engineering, denial of service.
The questions every CISO asks.
Can I get a copy of your SOC 2 report?
Where is my data stored geographically?
How are secrets handled inside sandboxes?
Do you train models on customer code?
What happens to my data when I cancel?
Do you support BYOK (bring your own key)?
Got a harder question? We answer those too.
Hire your first AI engineer.
Ship by lunchtime.
5 minutes to onboard. First PR within an hour. Cancel anytime.