Approved starting points
Create reusable Linux variants and recipes for common roles while preserving an explicit path back to the source configuration.

Platform engineering
Turn an approved Linux baseline into versioned, bootable artifacts that teams can inspect and test before they reach a fleet. OpenFactory handles the complete system image, not a shell layered onto a developer laptop.
Platform teams can standardize the operating system, services, users, packages, desktop behavior, and validation checks as one reviewable artifact. Teams consume the resulting image instead of rebuilding a workstation or edge node from a long runbook.
Create reusable Linux variants and recipes for common roles while preserving an explicit path back to the source configuration.
Boot the produced image and test its terminal, desktop, services, network behavior, or application UI against the running VM.
Keep projects, builds, variants, tests, and sharing scoped to the appropriate organization and role-aware workflows.
Retain and download the built artifact. Customer-controlled delivery boundaries are assessed through the enterprise pilot.
The operating model stays simple: define the baseline, build the machine, prove the behavior, then promote the exact artifact.
Capture packages, services, users, configuration, target format, and acceptance checks in a versioned recipe.
Produce the ISO or disk image and start the resulting artifact in an isolated VM.
Inspect results, record evidence, and move the approved artifact toward the target fleet or appliance workflow.
No. OpenFactory builds and validates complete bootable Linux systems. It does not activate a package environment inside the host shell.
Yes. Teams can begin with an existing variant or recipe, fork it, and add the packages, services, or checks required for a specific machine role.
Those deployment boundaries are available as a scoped enterprise pilot. The pilot validates the workload and integrations before a production commitment.
A representative machine is enough to test recipe ownership, build behavior, artifact validation, and the evidence your platform process needs.