When the product becomes a delivery responsibility.
Move when you need SaaS-level profiles, the full standard worker set, and a supported operating path across a software product team.
Commercial editions
Choose the level of control, ownership, and support the work requires.
Build Profiles define what a delivery must prove. Editions define the working machinery, integration, source rights, and support your organization receives.
The distinction that keeps the offer honest
An edition is not a maturity claim.
Foundation is not an inferior product and Mission Critical is not a blanket certification. Each edition gives a real, stated operating base. Higher editions increase the scope of profiles, organizational integration, ownership, and the assurance work that can be delivered and demonstrated.
 |  |  | |
|---|---|---|---|
| FoundationFirst controlled delivery base | ProductMaintained software product | OrganizationMulti-team operation | |
| Best suited to | Solo developers, startups, and small product teams establishing their first controlled delivery base. | Teams delivering a maintained software product without taking ownership of the factory source. | Companies standardising AI-assisted delivery across several teams. |
| Included Build Profiles | PoC and MVP, with a stated baseline-security scope in MVP. | PoC, MVP, and SaaS. | Product profiles plus customer-defined profiles. |
| Working delivery base | Core managers, workers, gates, evidence, repository workflow, and remediation appropriate to PoC/MVP work. | Full standard worker set, model routing, review, recovery, evidence controls, and SaaS delivery machinery. | Product working base plus operating controls designed for shared team use. |
| Integration and operation | Self-hosted installation with documented configuration boundaries. | Supported configuration within the standard operational model. | Organization integrations and a multi-team operating model. |
| Source rights | No source Operate the licensed release. | No source Operate the supported release. | No source Operate across the organization. |
| Updates and support | Self-service installation, documented configuration, and edition update terms. | Upstream releases, supported configuration, and defined support. | Upstream releases, organization support, and integration guidance. |
| Commercial route | Operational license for a focused delivery base. | Operational license for product delivery teams. | Organization deployment license. |
 |  |  | |
|---|---|---|---|
| Organization SourceInternal adaptation | Mission CriticalTailored assurance | Agency OperatorControlled client delivery | |
| Best suited to | Organizations that must inspect, modify, and adapt the operating base internally. | High-consequence systems requiring a tailored evidence and authority model. | Agencies delivering controlled AI-assisted software work for multiple clients. |
| Included Build Profiles | Organization profiles, internal extensions, and the Pipeline Critical Build Profile. | Mission Critical, applicable lower profiles, and the Pipeline Critical Build Profile. | PoC, MVP, SaaS, and client-appropriate profiles within the agreed delivery model. |
| Working delivery base | Organization working base with the code available for controlled internal change. | Tailored control, evidence, recovery, and authority boundaries for the delivery context. | A working delivery base operated by the agency for defined client delivery lines, with client isolation and evidence controls. |
| Integration and operation | Scoped internal implementation and customer-specific integration work. | Joint design and implementation around the actual environment and risk model. | Agency-controlled environment with separated repositories, credentials, prompts, evidence, and client environments. |
| Source rights | Commercial internal-use source rights Includes Pipeline Critical. Inspect, modify, and adapt internally; no resale or public release is implied. | Source rights included in the scoped program Includes Pipeline Critical. Subject to the final commercial agreement. | No source by default Source and white-label rights are separate commercial decisions. |
| Updates and support | Upstream releases, source-aware support, and scoped implementation. | Agreed release, support, assurance, and implementation arrangements. | Partner support is distinct from end-client support; the agency remains first-line for client delivery. |
| Commercial route | Organization license plus source-rights fee. | Design-partner engagement with tailored commercial terms. | Partner operating license; a client needing its own deployment receives its own license. |
Agency Operator
A partner license for delivering controlled work to clients.
Agency Operator runs alongside the deployment editions. It permits an agency to operate Buildfactory in its own controlled environment for a defined portfolio of client delivery lines. It is not a resale, white-label, or unrestricted source license.
AGENCY OPERATOR / CORE RULESPARTNER MODEL
Client isolationRepositories, credentials, prompts, evidence, and environments remain separated by client.
Delivery right, not transfer rightThe agency can use the system to deliver work; a client that needs to operate it receives its own license.
Agency is first-line supportPartner support and end-client support are explicitly separated.
Source and white-label rights are separate negotiationsThey are not implied by the agency operating license.
Upgrade path
Increase the system only when your consequence requires it.
Start with Foundation to establish a controlled delivery base. Add the SaaS profile and broader recovery machinery with Product. Add organization operating controls or source rights when internal ownership and integration require them.
When the process must work across teams.
Move when the challenge is standardization, centralized operation, integrations, and organizational evidence—not simply more model calls.
When internal adaptation becomes essential.
Source rights are for customers that need to inspect, change, and own the operating base inside their environment.
Evaluate the fit
Plan an evaluation →Choose from observed delivery work, not a feature checklist.
Start with a representative repository and an honest view of the evidence, controls, integration work, and ownership you actually need.