GitHub Actions and CI routing
Put CO2 Router in front of build and test execution to decide whether jobs run now, reroute to a cleaner region, or delay under policy.
Design Partner Program
3 to 5
active partners max
90 days
pilot term
1 workflow
scoped lane per partner
1 paid
phase-one conversion target
Pilot rail
Pre-execution environmental authorization, not another sustainability dashboard.
The pilot is built to secure real partners, real governed workloads, real proof, and paid conversion. The win condition is narrow and operational: three accepted partners, first value fast, one paid conversion, and one usable proof asset.
Month 0
Qualification and setup
Confirm fit, lock scope, sign the design partner agreement, define success metrics, and schedule kickoff.
Month 1
Activation
Onboard technically, connect the first workflow, run the first real policy decision, and capture first value as soon as live impact appears.
Month 2
Iteration
Expand only within the agreed scope, refine policies and proof surfaces, and log operational feedback against live usage.
Month 3
Graduation
Review outcomes before term end, present the paid continuation plan, and either convert, extend with a strict reason, or close cleanly.
Best-Fit ICP
Narrow fit wins this phase.
Infra, platform, SRE, or data teams with meaningful cloud, CI, or scheduled compute.
Operators under pressure around emissions, workload placement, compliance, or policy enforcement.
Teams with an internal champion and a commercial path if value is proven quickly.
Disqualifiers
Anything vague gets declined.
Vague curiosity with no practical workflow to test in the next few weeks.
Requests for open-ended consulting or a custom product branch for one company.
Teams without a champion, without a path to commercial approval, or looking for indefinite free access.
Entry wedge
Start with one workflow lane and make it operational fast.
Scheduled and batch compute
Govern recurring jobs, model refreshes, ETL pipelines, and non-urgent workloads with real environmental authorization before launch.
High-compute policy gates
Apply binding checks to expensive or high-impact jobs where carbon, water, placement, or traceability policy must be satisfied before execution.
What partners get
Early access to CO2 Router in one real limited-scope workflow.
Hands-on integration support and direct founder access.
Influence over roadmap inside the scoped pilot lane.
Preferred founding pricing if the pilot converts.
What we ask
A 3-month pilot term with one clearly scoped workflow or workload family.
Biweekly feedback sessions plus async communication by email or portal.
Practical integration cooperation and honest feedback on value, friction, and missing pieces.
Permission for anonymized results if the pilot succeeds. Named reference only with explicit approval.
Commercial rule
No unlimited free access and no hidden pricing transition later.
No vague "let's explore" pilots and no scope drift outside the single workflow lane.
No more than 3 to 5 active partners at once.
Every pilot starts with an explicit paid continuation path from day one.
Success Measures
The program only counts if it converts into evidence and revenue.
Accepted design partners
Onboarding completion rate
Time to first value
Live workloads or policies governed
Biweekly call completion rate
Partner-sourced revenue and paid conversion timing
Expansion to additional workflows
Case study, quote, or anonymized proof asset created
Phase-One Lock
Three accepted partners. First value fast. One paid conversion. One proof asset.
This is not a broad beta and not a generalized sustainability waitlist. The category wedge stays narrow until the operator motion is repeatable.
The graduation call happens before pilot end and leads to one of three outcomes: converted, strict extension with reason, or a clean close with feedback captured.