Introducing Evergreen

“How many PRs should the average engineer at Carta ship per day?”

I asked this question at an engineering all-hands in May. After almost a year of running the engineering team, they’ve become used to my provocative questions that seemingly only have wrong answers (my rite as a CEO). After some trepidation, the general consensus was that a baseline should be 1-2 a day. Our best engineers were at maybe 10.

We were five months into using AI coding assistants. How we worked had changed - engineers were writing code faster and manual work like PR reviews had been automated - but the number of PRs shipped was only growing incrementally.

When I dug in, I realized it was because work was siloed. No one else could see it, replay it, or build on it, and when someone closed their laptop, their agent stopped mid-task. How fast we could build was still limited to one person, one chat window, one laptop.

So we built our own model-agnostic collaborative coding platform. Teammates and agents work in shared sessions that run in the cloud, and agents push the PRs on their own. We call it Evergreen.

It’s completely changed how work gets done. In January, we shipped about 1,300 PRs a week. Last week, it was almost 20,000. We ship 15x more, more than 6x faster, with an 80% lower revert rate.

Our 250+ engineers adopted it first. When we saw what it did, we opened it to all of Carta, and more than 80% of the company now uses it.

Here are two examples of how we use Evergreen

Shared sessions: Think about your last P0. Someone starts debugging, and everyone else jumps on a Zoom to watch them share their screen. Now, a Datadog alert starts an Evergreen session on its own. Everyone who’s needed joins the shared session, watches the agent work, and tells it where to look next. Nobody waits on a screen share.

Finishing the job: For years we struggled to keep up with removing old feature flags. In the past month, an Evergreen automation has removed almost 1,600 of them, each one checked, reviewed, and merged. Most tools stop when the code is written. Evergreen’s agent keeps going until the change is live.

Why we’re releasing it

Our engineers love Evergreen so much they asked me if they could use it outside of Carta. That was my light bulb moment: this could add so much value for other companies.

Every company I talk to has the same problem I had. Engineers are the constraint, and they’re being asked to do more every quarter. Evergreen fixed this for us, and I think it’ll fix it for you.

It runs on Claude, Codex, Grok, and Muse, and works with the plugins and MCP servers you already use. It also has the controls your security team will ask about: isolated sessions, scoped access, audit logs, and spending caps.

I’d love for you to try it. It takes ten minutes to get a first session running, and there’s a 7-day free trial. I can’t wait to see what your team builds.

Henry WardCEO and Co-Founder, Carta