
Current product workflow
Review the recipe, build a bootable artifact, inspect its checksum and inventory, and evaluate the tests that actually ran.
OpenFactory is a Linux image builder for teams that want operating systems to be specified, reviewed, built, and tested as identifiable artifacts instead of assembled by hand on each machine. Build completion, test success, security review, and deployment approval remain separate.
Most image work starts as scattered requirements: install Docker, enable SSH, pin a service, add a non-root operator, harden the system, expose metrics, and check whether the service listens after boot. OpenFactory turns supported requirements into a reviewable build path. Inspect the generated recipe because a valid recipe can still misinterpret or omit user intent.
A Linux image pipeline should make change visible. Recipes, prompts, package lists, service declarations, and test scenarios become the review surface. When the image changes, the build reruns and the same assertions report whether the named checks still pass. Their scope and logs must be reviewed; they do not prove every behavior or control.
For application repositories, connect that flow to bootable ISO builds from GitHub. To evaluate a larger operating model, take the artifact and evidence into a fleet-readiness pilot.
A Linux image builder assembles an operating-system artifact from declared packages, users, services, and configuration. Its output and guarantees vary by tool. OpenFactory currently focuses on eligible bootable artifacts with build records and selected validation evidence.
A golden image is a versioned base artifact that an organization has reviewed for a defined target and use. Calling an image golden should require an immutable identifier, recorded inputs, acceptance evidence, an owner, and an approved release state; the label alone is not a security or compliance property.
OpenFactory recipes and APIs can participate in a controlled pipeline, but teams must keep credentials server-side, review generated changes, prevent duplicate state-changing requests, verify the artifact checksum, and gate promotion on explicit tests. Production deployment remains a separate integration boundary.
Build a bootable Linux ISO from a prompt, repository, or recipe.
Package a repository and its install docs into an OpenFactory image.
Test the artifact handoff into customer-controlled rollout and recovery.
Compare RHEL image workflows with OpenFactory's multi-use image path.
Decide what belongs in an installer, a reusable image, or cloud-init.
Use OpenFactory to turn the same requirements into a bootable, testable Linux system.