Pilot Program

Start with one repo and one governed merge path.

Certus pilots are intentionally narrow. The goal is to protect one real pull request lane, verify policy and evidence behavior, and decide rollout based on review pressure instead of product theater. CLI distribution, dashboard sync, and repository access are enabled for approved pilot organizations.

Suggested 14-day lane

1

Scope one repo

Start with one protected repository, one reviewer group, and one framework priority set.

2

Install the merge gate

Install the managed GitHub App from the dashboard, set repo policy, and make the Certus check a required status.

3

Review evidence on real PRs

Run failing and passing pull requests through the same path your reviewers already use.

4

Decide rollout

Use blocked PRs, evidence packs, and reviewer feedback to decide whether to widen coverage.

What you need ready

  • One repository with an active pull request flow
  • A reviewer or approver who will inspect the evidence output
  • A small framework set to prioritize first
  • A declared test command when the repo has an executable suite

Working surfaces

Docs

Hosted GitHub install path, CLI flow, and policy configuration

Repositories

Connect the first repo and watch compliance posture

Merge Gate

Set thresholds, frameworks, and blocking behavior

Evidence

Inspect the signed pack and reviewer export path

Pilot success looks like this

Protected PR

One real PR is blocked or cleared by the configured merge gate.

Reviewer output

Reviewers can explain the evidence pack without leaving the PR path.

Rollout decision

You know whether to widen to more repos, frameworks, or teams.

Pilot scheduling

If you want rollout help, framework prioritization, or merge-gate setup on a real repository, use the scheduling link and run the conversation live in one lane.

Schedule pilot review

Access and rollout model

Pilot workspace

Certus issues an org workspace, API key, and private package access for the pilot team.

Selected repositories

Repository sync is enabled only through the managed GitHub App installation approved for the pilot scope.

Commercial rollout

Wider repository coverage, retention, team access, and deployment options are activated after the pilot decision.