Adopter quickstart

Hosted CI proof path

Public waitlist preview for adopting Imladri with Hosted CI Proof: initialize the adapter, wrap one risky capability, run the local scanner, and review the proof artifacts before a private design-partner workspace is opened.

Join waitlist View pilot packet Read integration docs

Certification status

Certified

Live hosted CI proof passed for GitLab and Vercel, with each run producing an Imladri-native proof artifact.

2/2 hosted CI vendor lanes passed: GitLab and Vercel.

Runtimeci

Public modeWaitlist preview

One-command starter

imladri init --ci-provider gitlab

Install

node cli/imladri.mjs scan init-ci --provider gitlab
node cli/imladri.mjs scan init-ci --provider vercel

Minimal wrapper

imladri scan init-ci --provider gitlab --output .gitlab-ci-imladri.yml
imladri scan --path . --config .imladri-scan.json --format json --output imladri-boundary.json --fail-on new

Local proof artifacts

imladri scan init-ci --provider gitlab --output .gitlab-ci-imladri.yml
imladri scan init-ci --provider vercel --output scripts/imladri-vercel-scan.sh
imladri scan --path . --fail-on new
imladri proof export --format json --output imladri-proof.json

CI scanner

imladri scan init-ci --provider gitlab --output .gitlab-ci-imladri.yml

CI is only the runner. GitLab and Vercel are the current live hosted CI proof lanes; the evidence stays Imladri-native.

What this proves

Boundary wrapped

Hosted CI Proof strict tools route through Imladri preflight before the tool body runs.

Evidence generated

The local scan and SDK certification commands create artifacts for design-partner review.

No account required

This public preview uses local artifacts. Private proof workspaces open only during design-partner onboarding.

Pilot notes

Use the private pilot workspace as the evidence store; CI only runs the scanner.

← Back to all adopters