Oct 13—15 · 2026
Brooklyn Navy Yard · NYC
A conference · year three
No keynotes. Just code.
Three days of practical systems engineering from the people who actually ship the platform. No keynote theater, no vendor puffery — just the talks you'd want to read the source for.
240 builders. 3 tracks. 0 filler sessions.
Scroll · schedule is the proof
// 01 — Theme
Two years of talks became a corpus. This year we compile it — the patterns, the failures, the load-bearing primitives — into something you can run in production on Monday.
Two years in, we stopped counting talks and started reading transcripts. The throughline wasn't a framework or a hype cycle — it was compilation: the unglamorous work of taking intent, resolving dependencies, and shipping something that runs without surprises. That's the lens for 2026.
Every talk ships with a repo, a config, or a postmortem. If it can't survive a code review, it doesn't make the schedule.
We track what compounds: scheduling, storage, observability, the cost of a cold start. Trends come and go; tradeoffs don't.
Speakers paste code, not stock photos. Q&A runs as long as the talk. The hallway track is a scheduled, indexed resource.
"I came in skeptical and left with three things I changed in our scheduler on Monday morning. That has never happened to me at a conference."
// 02 — Speakers
Six of the forty-two confirmed speakers. Each picked because their work survives contact with production. Hover a card for the talk hook.
// No speakers in this track yet — check the full program.
Principal Engineer · Nebula Compute · fleet scheduling
"The scheduler is the product." What five years of multi-tenant fleet data taught us about fairness, preemption, and saying no to features.
Inference Lead · Tessellate
KV-cache eviction at p99 — 40k req/s, field report.
Build Systems · Northbound CI
Your build cache hates you — a 14-min restore, debugged.
Edge Runtime · Stratus
Islands without the island tax — streaming partial hydration.
Supply-Chain Security · Redshift Foundry
Supply-chain as a compile pass — provenance in CI.
Storage · ApertureDB
Why we rewrote our WAL — and the seven prod bugs we found.
+ 36 more practitioners across three days
// 03 — Schedule
Three days. Three parallel tracks — Compile, Runtime, Edge — plotted on a vertical clock. Sized to duration. Read it like a pipeline.
Times in ET · Subject to refinement · All sessions recorded & transcribed
// 04 — Venue
A former ship-fitting hall, retrofitted. 40ft ceilings, real power drops, fiber on two diverse paths. The room is built for long attention spans and long days.
Runbook
Childcare on request · Nursing room on site
// 05 — Sponsors
Sponsors keep tickets cheap and the CFP open. In return we ask for engineers at the booth, not sales decks.
Tier · Backstage
Tier · Runtime
Tier · Edge
// 06 — Tickets
All tiers include the same content, recordings, and the hallway track. You're paying for access logistics, not a paywall.
Community
$0
Waitlisted · need-based
Pro
$899
Per builder · early bird
Team
$2,400
3 seats · $800/each
All prices in USD · No processing fee · Diversity scholarships cover 40 seats
// 07 — Traction
Numbers from BUILD/2024 and BUILD/2025 combined. We publish the raw survey data with the recordings.
4,200
Attendees · 3 yrs
96
Talks shipped
38
Countries
4.8/5
Satisfaction · n=2,140
Every prior talk is in the archive, repos linked. Browse the archive →
CFP · open through Aug 1
Submissions are blind-reviewed by a rotating panel of staff-plus engineers. We tell you the rubric up front; you'll get written feedback either way. 312 / 360 reviewed so far.