Deployment
Swiss-hosted (Google Cloud, Zürich, via Northflank) by default, or on-prem inside your own perimeter, on request.
Security & architecture deep-dive
The 6 areas from the Enterprise Trust block, in depth: what runs where, who can do what, and exactly what is still in progress. Honest status throughout, no polished facade.
Read how beacon platform governs AI in software development
6 available · 5 on request · 1 in progress
As of September 2026
beacon.build runs on Google Cloud in Zürich (europe-west6), via our hosting provider Northflank, so your data stays Swiss-hosted by default. If your organization needs the platform inside its own perimeter, on-prem deployment is available on request, agreed individually rather than self-serve.
Every model call is a deliberate, visible hop through your own provider contract, never a hidden default.
Bring your own model and your own keys. Every model call runs on your own provider contract, never through us, and never against a bundled token quota we resell. When an agent calls a hosted model, that prompt goes to the provider you picked: a visible, deliberate choice, never a hidden default.
Access is role-based, and every agent acts under its own identity, not a shared service account: who did what, on which Spec, with which model, is traceable and live in the product. Single sign-on is on request: not built yet, set up as soon as your engagement needs it, and the platform is designed so adding it is straightforward.
A single-instance or on-prem deployment gets its own isolated environment: no shared tenancy, no shared token quota, no model lock-in. Two decisive human control points frame agent work (after the Spec, and before merge), with a human integrator as the sole merger, so nothing ships without an explicit go.
Our hosting provider, Northflank, holds SOC 2 Type 2 (details on request via their trust center); its infrastructure runs on Google Cloud in Zürich. A data processing agreement with Northflank is in progress. We answer security questionnaires and vendor assessments on request today; beacon. would pursue a certification such as ISO 27001 if a customer engagement required it, not before. Google Cloud publishes its own infrastructure-level certifications (see the source link below); those are Google’s, never a beacon. or Northflank claim.
Google Cloud publishes its own compliance and certification program for its underlying infrastructure. Google Cloud's compliance offerings
Seat pricing starts from 10 users. Single-instance deployments and org-wide site licenses are negotiated individually for your setup, not sold off a list price, so the contract reflects your actual deployment and volume.
Architecture overview
No invented components: this mirrors the same platform capabilities described on /platform, laid out as the pieces a reviewer needs to see together.
Deployment
Swiss-hosted (Google Cloud, Zürich, via Northflank) by default, or on-prem inside your own perimeter, on request.
Model access
BYOK. Calls run on your own provider contract; no bundled token quota we resell.
Identity & access
Role-based access; agents act under their own identity, not a shared account.
Human control points
After the Spec, and before merge: a human integrator is the sole merger, agents never ship unreviewed.
Guardrails & quality gates
Constitution and Engineering Practices, Spec Test Driven Development, and a Definition of Done enforced on every change.
Audit trail
Every unit of work traceable: who did what, on which Spec, with which model.
What's not there yet
What a thorough evaluator asks about next, stated plainly rather than glossed over.
Guided evaluation
For organizations deciding where to start. Eight questions, two minutes, based on the AI Adoption Maturity Model.
For organizations evaluating on-prem or Swiss-hosted deployment with their own infrastructure and keys.