Your clients already pay for Claude Code and Codex. Set up Pangea for their teams, run it for them, and build a recurring business on top.
Every engineering lead wants Claude Code, Codex or Cursor across the team, and every security lead wants to know who approved what. Few know how to get both.
You already understand their stack, their repos and their rules. That is the hard part of any rollout.
Shared sessions, approvals, an audit trail, cloud computers and nine agents, ready for a whole team.
One rollout turns into ongoing work: new bots, new skills, new teams, month after month.
How the program is meant to work. The details are set with the first cohort.
01Sign up for the first cohort of Pangea partners.
02Workspaces, roles, approvals, cloud computers, connectors and skills, hands on.
03Find the teams ready for agents and price the rollout your way.
04Put the agents to work and keep improving them with the team.
05Keep your services revenue, plus a recurring share of the plans you bring.
Charge your clients to set up the workspace, connect GitHub, Slack and their cloud accounts, write the first skills and bring every engineer in. You set the price.

Offer a monthly retainer for new bots and schedules, permission reviews, audit exports and onboarding new people. The work keeps coming because the team keeps growing.

A monthly share of the Pangea plans of the clients you bring, for as long as they stay active. Terms are set with the first cohort.

Being built with the first cohort.
Your services, plus a share of the plans you bring, every month they stay.
Learn the setup end to end, from the first workspace to approvals and the audit trail.
Templates like Release Helper and Docs Writer, and skills to adapt for each client.
Show Pangea working on a real repository before the client signs anything.
A shared channel with the people who build Pangea, for the questions that block a rollout.
The relationship stays yours. Pangea does not sell around you.
Setting up agents once is easy. Keeping them running for many clients is not. On Pangea Cloud, the infrastructure is ours.
Where you add the most value.
The operational work, on Pangea Cloud.
Everything a client team needs to put coding agents to real work, in one workspace.
Teammates join a running session, see the same tool calls and steer the work together.
Claude Code, Codex, Cursor, Antigravity, Grok, DeepSeek Harness, OpenCode, Hermes Agent and Pi, each on the plan or key the client already has.
Risky steps wait for a person, and every prompt, tool call and approval is exportable.
Agents keep working on a cloud computer with the laptop closed, or on a server the client controls.
Schedules, webhooks and Slack messages start the next turn, and the agent reports back.
What one agent learns, the next remembers, and every agent shares the same skills and tools.
If your clients write software, the program is for you.
Everyone who joins before the program opens gets:
The program is being shaped with the first partners, so some answers are still short.
Nothing to join the list. The program terms are set with the first cohort.
You charge your clients for rollouts and ongoing management at your own prices, and you get a recurring share of the Pangea plans of the clients you bring.
It is set before the program opens. Founding partners get terms that later partners will not.
You need to be at home with GitHub, a terminal and the client's tools. Pangea is for engineering teams, so most rollouts touch repositories and cloud accounts.
It helps. The first cohort favors partners who already serve engineering teams.
Not at the start. The program begins with the clients you bring, and the relationship stays yours.
After Pangea's early access for teams, which opens Thursday, November 19. We will email the first cohort directly.
The first cohort is small and opens one partner at a time.
Join the list