Operate a supported release.
Run the licensed edition, configure documented boundaries, retain your version, and receive updates/support according to the agreement.
Installed in your environment
Adopt the factory as an engineering system—not as a black box.
Buildfactory is self-hosted and integrated around your repositories, tools, environments, provider choices, and engineering authority. Source availability depends on the edition you select.
Commercial rights
Operational deployment and source ownership are separate decisions.
Foundation, Product, and Organization deliver a runnable operational edition without source. Organization Source and Mission Critical add commercial internal-use source rights because those customers need to inspect, modify, and own the operating base inside their environment.
Adapt the base internally.
Inspect, modify, and integrate the source under a commercial internal-use license. Redistribution, resale, and public release are not implied.
Deliver for clients without transferring the factory.
Operate defined client delivery lines from an agency-controlled environment. A client that needs its own operating deployment receives its own license.
Licensing claims on this site describe the intended commercial model, not the final legal agreement.
Actual rights, restrictions, affiliate scope, client deployment, update coverage, and support terms must be set out in the signed license.
Integration surface
Keep the tools your teams already depend on.
Buildfactory coordinates existing engineering systems instead of replacing your repository, runtime, scheduler, CLI, or provider. Configuration and adapters make the factory fit the environment.
Git + worktreesIsolated task ownership and change history
Gitea + repositoriesSource, issues, review, and local hosting
DockerRepeatable containers and test environments
ProxmoxStronger isolated execution and infrastructure
DaguWorkflow scheduling and execution
RundeckOperational jobs and controlled runbooks
Coding CLIsOpenAI, Anthropic, Cursor, OpenCode, and supported tools
Model providersHosted, routed, and local inference choices
Technical evaluation
Start with one representative delivery line.
The evaluation is a working fit assessment, not a staged demo. Use a real repository and a bounded project slice to observe controls, evidence, failure recovery, integration work, and likely commercial fit.
EVALUATION OUTPUTDECISION PACKAGE
Current-state mapHow your teams currently use AI and what factory work they are already building internally.
Controlled representative runOne real slice processed through the selected workers, gates, review, repair, and evidence flow.
Fit and gap reportWhat works now, what needs adaptation, and what should not be promised yet.
Edition recommendationA decision on the profile, integration, rights, and support level appropriate to the work.