Autobuild · A Research Project from Obvious
Ship your roadmap in days not months.
Learn about the emergent set of tools and methods behind the exponential reduction in effort and cost of generating quality software driving the Obvious engineering team.
Frontier Series
Join us in person at any of these upcoming locations for a 2 day hackathon focused on delivering 12 weeks of roadmap.
Learn more
How it works
Autobuild takes a specification, decomposes it into a dependency DAG, and runs parallel agents that build, test, and merge PRs autonomously. Agents get agentic code review, security review, and full CI on every PR. Humans review at the release-branch level: whole capabilities, not individual commits.
Internally, this produces around 100 PRs per day per engineer. A single build that would have taken 12 weeks landed in under 36 hours at roughly $1,600–$2,000 of inference. We want to see if those numbers hold on codebases we didn't write.
Outcomes
01
Shipped code
Merged, tested code representing a significant chunk of your roadmap. How much depends on codebase complexity and CI speed, but internally we've seen 12-week equivalents land in under 36 hours.
02
A tuned system
Autobuild configured for your codebase, CI, and architecture. Tuned based on what we learn during the week. Whether you keep running it after is your call.
03
Operational data
Concrete observations on where autonomous building works, where it doesn't, and what it takes to sustain. Your engineers come back with firsthand experience operating in this mode.
Is this right for me?
Autobuild is a home for big ambitions. We've had seed-stage teams shipping features they'd been putting off for months, and Series B companies reallocating headcount budget toward inference. The common thread is engineers who are ready to work in a fundamentally different mode.
What others are saying
“Six months of engineering work — our hardest project — done in 48 hours.”
— Ishmael, CTO · Paragon
“We ran it all night long. It did consume some credits — but it also went through six weeks of work.”
— Will, CEO · CoreGrid
“Half of our originally estimated three month outlook for the project. In 24 hours.”
— Natalia, Engineering Manager · Paragon
“Everything's changed. The calculus of how I think about engineering and product is fundamentally different than it was three or four days ago.”
— Ishmael, CTO · Paragon
“That last piece — making the product exist in the world — is almost just an errand at the end.”
— Lior, Founder
“We don't have to prioritize anymore. We can do all of the things.”
— Natalia, Engineering Manager · Paragon
“AutoBuild takes away the babysitting of agents.”
— Diptano, Founder · Tensor Lake
“I'd rather them wait for the AI than the CI.”
— Pierre, Staff Engineer · Frontz
Frontier Build
Build a quarter of roadmap in 5 days.
A 2-day remote + 3-day in-person intensive with the engineers who built Autobuild. 6 companies per session.
ATL
C1Atlanta, Georgia
33.7490° N, 84.3880° W
April 8–9, 2026
CompleteATL
C2Atlanta, Georgia
33.7490° N, 84.3880° W
April 15–16, 2026
CompleteSFO
C3San Francisco, California
37.7749° N, 122.4194° W
April 22–23, 2026
CompleteNYC
C4New York, New York
40.7128° N, 74.0060° W
May 6–7, 2026
SFO
San Francisco, California
37.7749° N, 122.4194° W
Announcing soon
ATL
Atlanta, Georgia
33.7490° N, 84.3880° W
Announcing soon
MIA
Miami, Florida
25.7617° N, 80.1918° W
Announcing soon
YYZ
Toronto, Ontario
43.6510° N, 79.3470° W
Announcing soon
DEN
Denver, Colorado
39.7392° N, 104.9903° W
Announcing soon
AUS
Austin, Texas
30.2672° N, 97.7431° W
Announcing soon
ORD
Chicago, Illinois
41.8781° N, 87.6298° W
Announcing soon
SEA
Seattle, Washington
47.6062° N, 122.3321° W
Announcing soon
To get started, send us three things.
Names and roles of your 2 engineers attending Days 3–4 (in person) and Day 5 (remote)
Brief description of your stack (language, framework, CI system, hosting)
The roadmap target you want to aim at: what would be worth 12 weeks to ship in a week?
We'll send setup instructions and schedule the Day 1–2 remote sessions from there.