Born live. Built with the product itself.
Overclock didn't come out of a pitch deck. It was born in a livestream series — when coordinating several AI agents by hand got too expensive and too slow — and it gets better every day using Overclock itself, in front of everyone.
Why Overclock exists
The story is recorded, stream by stream. On day 9 of the series, Overclock shows up as an embryo: the interface meant to carry an agent operation out of the computer. On day 13, the cost of frontier models jumped 35% overnight — and instead of paying the bill, the stack that became the product was born: an expensive model orchestrating, a cheap model executing, shipped live with the bug fixed on screen.
The rest came from the community. The livestream audience asked for access, the product opened up, and every version since has been built, tested, and broken live — with bugs reported by the members themselves going straight into the next night's queue.
“Tinha audiência certa vendendo produto errado. E aí a gente criou o Overclock pensando na gurizada — daí a gurizada começou a pedir para eu lançar para eles. Lancei e o negócio estourou.” — said live, on day 26
(EN: “We had the right audience selling the wrong product. So we built Overclock thinking about the crew — and then the crew started asking me to launch it for them. I launched it, and it took off.”)
We don't throw a prompt at a model. We build the harness.
That's how we think about it: the same model delivers more or less depending on how it's used. That's why every task on Overclock ships with the harness already built — right agent, right model, right effort, right skill.
The harness was born inside the livestreams, out of necessity: orchestrating different models — each one in the right spot — was the only way to ship fast without burning tokens. It became the design doctrine for the whole product. See the harness in detail →
What changes versus working with AI by hand
| Criteria | With Overclock | By hand |
|---|---|---|
| Coordination | A maestro splits the request, holds each agent accountable, and merges the results. | You decide, review, and chain every step by hand, window by window. |
| Visibility | Every agent in a visible pane, with live status on the same grid. | Loose conversations; nowhere shows the whole picture. |
| Cost (tokens) | Token and cost per pane and per squad, in real time, on screen. | Cost shows up later, on the provider's invoice. |
Brazil's vibe coding ecosystem
Overclock's Discord is free and community-run: it's where the streams continue, bugs turn into a fix queue, and people just starting out get help from people already shipping. Informal channel — moderated, with its own terms — and never a place to paste an API key, a password, or client data.
All of this is documented, stream by stream
50 days of the series live — from day 1 with R$0 to day 52 with R$229,403 — with what got built, the key moment, and the lesson from each night.