Organizations

Ona

Sells Ona, a platform of background coding agents and automations (a page read on ona.com).

Website
ona.com

Profile from ona.com, checked November 4, 2026.

Explore with your AI assistant

Opens a new chat with a prompt that points the assistant to this archive. What it writes is its own, not the archive's: check any quotation on its passage page before you rely on it. Or add the archive to your assistant as a connector: https://the-ai-record.com/mcp (how).

Ona sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. Its passages stay in the archive and carry this flag.

7 passages

We already had Ona's code review automation running on every PR. The agent reviewed diffs, ran the code in a full environment, cross-referenced tickets, and left inline comments with an 88% acceptance rate and a 50% reduction in time spent on pull requests.

OnaPublished by the organization itself (post), no named author

Post: How auto-approving low-risk PRs with AI cut our lead time by 74%, Ona blog, April 9, 2026, at The experiment.

  • 88% review comment acceptance rate, before auto-approval, 2026. AI assists a person
  • 50% time spent on pull requests reduction, before auto-approval, 2026. AI assists a person

Checked against the source [ Grade B ] Said in the last year Sells AI tools Passage page

The team was roughly the same size throughout (39 unique contributors before, 43 after), but each developer went from merging 34 PRs per month to 96: a 2.9x increase in individual throughput with no headcount change.

OnaPublished by the organization itself (post), no named author

Post: How auto-approving low-risk PRs with AI cut our lead time by 74%, Ona blog, April 9, 2026, at The results.

  • 34 prs prs merged per developer per month before, 4 weeks to 2026-03-13. A person approves
  • 96 prs prs merged per developer per month after, 4 weeks from 2026-03-13. A person approves

Checked against the source [ Grade B ] Said in the last year Sells AI tools Passage page

Our engineers waited a median of 2 hours 49 minutes for their first PR approval. Four weeks after we let an AI agent approve low-risk PRs, that dropped to 3.8 minutes, lead time fell 74%, and deploys tripled, all with the same size team.

OnaPublished by the organization itself (post), no named author

Post: How auto-approving low-risk PRs with AI cut our lead time by 74%, Ona blog, April 9, 2026, at Opening.

  • 169 minutes median time to first pr approval before, before 2026-03-13
  • 3.8 minutes median time to first pr approval after, four weeks after the AI agent began approving low-risk PRs. A person approves
  • -74% lead time change, four weeks after vs before. A person approves

Checked against the source [ Grade B ] Said in the last year Sells AI tools Passage page

Our team averages 10.8 PRs per engineer per week, 2.5x the 90th percentile according to DX benchmarks. But every one of those PRs still needed a human to look at it, and the review queue became the constraint.

OnaPublished by the organization itself (post), no named author

Post: How auto-approving low-risk PRs with AI cut our lead time by 74%, Ona blog, April 9, 2026, at The problem: the review queue.

  • 10.8 prs prs per engineer per week, 2026. Level not stated

Checked against the source [ Grade B ] Said in the last year Sells AI tools Passage page

Stripe's Minions merges over a thousand agent-authored PRs per week. Ramp's background agent accounts for 57% of their merged PRs. The insight both share is that they invested heavily in standardizing their development environments long before agents.

OnaPublished by the organization itself (post), no named author

Post: The primitives of a self-driving codebase (Ona webinar page), Ona events page (Ona sells background coding agents); date is the webinar start date in the page data, February 26, 2026, at Webinar description.

  • 57% agent pr share, not stated. A person approves

Checked against the source [ Grade B ] Said in the last year Sells AI tools Passage page