Overview
What NOME Build Cloud is, what it runs, and how it differs from a hosted CI bill you can't tune.
What it is
NOME Build Cloud is a private AI build cloud. It runs continuous integration and deployment for your repositories on runners you own or NOME hosts, with a warm BuildKit cache, AI pull-request review, test sharding, image signing, SBOM and provenance, and deploy gates with rollback plans.
The model is simple: bring your own GitHub or GitLab project and your own pipeline YAML, run on your hosts or NOME cloud, no lock-in. The YAML is portable and the runners are yours.
What you bring
You bring a repository (GitHub or GitLab), a pipeline definition (standard YAML), and at least one runner — an owner-edge machine you register, or a NOME-managed cloud runner. NOME provides the cache, the AI review, the scheduling, the signing, and the gate.
What runs where
Builds and tests run on the runner you select per job. Owner-edge runners are your machines; NOME cloud runners are managed, ephemeral, and isolated per job. AI review runs through NOME's canonical reasoning path. Deploys run on protected, deploy-scoped runners only — never on a build/test runner.
Why it exists
Cloud CI got expensive, and AI made pull requests bigger — more generated code, slower builds, noisier reviews, and riskier deploys. NOME Build Cloud answers that by keeping the cache warm, sharding tests, reviewing diffs with AI, signing what ships, and putting a human at the production gate. You spend less because the cache reuses work and your own hardware runs free.
Where to go next
Read Architecture for the stage-by-stage pipeline, Owner-edge runner to register a host, and GitHub or GitLab to connect a repository.
Ready to try it?
Open NOME