Pilot cohort — limited seats

Be one of the first teams to have CVEs remediated before the world knows.

ZeroPatch is opening a six-week design-partner cohort for teams that want pre-disclosure patches on their own dependency graph. You bring a real production stack; we bring the AI patch loop, weekly demos, and direct roadmap access. Six seats. Six weeks. No-cost pilot.

Six-week pilotSix partner seatsNo-cost pilot

Inside the cohort

  • Pull requests opened on your real repositories, not a sandbox
  • Weekly demo of the loop running on your dependency graph
  • Direct line to the engineering team — no ticketing layer
  • Roadmap input that lands in the next sprint, not a backlog

What the cohort gets

The same loop your team would build, with a head start.

Pilot partners get the full ZeroPatch remediation loop on their real graph, plus the working sessions, benchmarks, and roadmap access that come with a small founding cohort.

Pull requests on your real graph

The agent opens scoped PRs against the actual repositories and manifests in your stack — not a sandboxed demo. You review what it would change before anything ships.

Same-day patch loop

When a CVE drops on a dependency you run, the agent drafts a remediation within hours, not the weeks a vendor patch usually takes. You stay ahead of disclosure.

Multi-layer coverage

Operating system, runtime, and library vulnerabilities — all addressed by the same loop. No separate tooling per layer, no extra vendors to onboard.

Direct roadmap input

Weekly office hours with the engineering team. Feature requests from pilot partners land on the next sprint, not in a backlog. You shape what ships next.

The pilot period

Six weeks, four milestones, no surprises.

The pilot is a working loop, not a sandbox. Each week has a concrete output and a concrete decision; you can pull out cleanly at the end with no obligation.

  1. Week 0

    Kickoff + onboarding

    60-minute call with your team, the agent gets scoped repo access, the dashboard goes live for your environment. We agree the kill-switch protocol.

  2. Weeks 1–4

    Weekly demo patch loop

    Every Monday we send the week’s candidate patches as draft PRs. You review in your normal process; we iterate on false-positive filters and patch shape.

  3. Week 5

    Mid-point retrospective

    Speed-run review of what landed, what the agent over- or under-patched, what changed in your triage time. We tighten the loop based on real numbers.

  4. Week 6

    Go / no-go decision

    Pilot partners who want to continue convert into a paid seat at the agreed floor. No-pressure exit if it didn’t fit — we keep the data and write up the lessons.

Who it's for

Teams who already feel the pain the loop solves.

The cohort is built for teams that own a real production dependency graph and a real remediation SLA — not for one-off evaluation environments.

Platform / infrastructure leads

Running a Linux fleet or a Kubernetes estate across 100+ production nodes — the kind of team that owns the dependency upgrade queue and would rather not own it.

Security teams who measure in hours

Your remediation SLA is hours, not weeks. You already do pre-disclosure work and want a tooling layer that scales the same loop beyond what your team can manually triage.

Engineering leaders at scale-ups

You ship to prod every day, your dependency graph changes faster than your security review, and you’d like a partner that drafts the patch so your team only has to bless it.

Compliance + production-readiness owners

SOC 2, ISO 27001, or internal audit cycles that penalize late CVEs. A pilot seat gives you audit-trail-quality patch provenance without adding headcount.

Apply for the pilot cohort

Drop your work email. We'll send the kickoff packet and schedule the onboarding call once we confirm a seat for your team.

By signing up you agree to receive pilot-related emails. Unsubscribe anytime.