The next rung

Every era of the chip industry has let more companies build chips, and every time the market got bigger. The barrier left is engineering. Here’s why we think autonomous verification is the next rung.

Stone terraces on a hillside seen from above, each step wider than the one above it, one person walking the widest

Every era of the chip industry has had the same shape. Something that used to take a whole company becomes something you can buy, and the number of companies that can build a chip goes up. The market doesn’t split into smaller pieces when that happens. It grows.

  1. 1950s–70sBuild everythingFairchild, Intel and TI design, tool and fab it all in‑house.
  2. 1980sDesign toolsEDA companies sell the tools, and far more teams can design a chip.
  3. 1987The foundryTSMC makes the fab a service, and fabless companies like NVIDIA follow.
  4. 1990Licensed IPArm licenses its processor designs, and Apple builds its own silicon on them.
  5. NowAutonomous verificationTapeout Labs takes on the engineering, and far more companies can build chips around their own workloads.
Each rung lowered the barrier to building a chip, and the base of chip builders grew wider.

Everyone built everything

The first chip companies, Fairchild, Intel and TI, did everything themselves. They designed the chips, built the tools to design them and ran the fabs to make them. If you wanted to build a chip, you had to build that whole company first.

The tools became a product

In the 1980s, electronic design automation turned those in‑house tools into products. Mentor, Synopsys and Cadence sold simulation, synthesis and layout to anyone, and far more teams could design a chip without writing their own tools.

The fab became a service

In 1987, TSMC opened as a pure‑play foundry. You no longer needed a fab to build a chip, and a new kind of company became possible. NVIDIA was founded fabless in 1993 and built on that model from day one.

The core became a license

Arm, founded in 1990, licensed its processor designs instead of selling chips. Companies could start from a proven core and spend their effort on what made their chip different. Apple’s first in‑house chip, the A4 in 2010, was built on Arm, and so is every A‑series and M‑series chip since.

The barrier left is engineering

Tools, fabs and IP are all things you can buy now. What you still can’t buy is the engineering. AI is making it cheaper to write hardware, but writing RTL is only part of the job. A leading‑edge chip takes hundreds of engineers and years of work, and most of that effort goes into verification, proving the design does what it should before it’s manufactured. That’s why building a chip is still a decision only a small number of companies can make.

Some have made it anyway. The largest cloud companies design their own accelerators and CPUs. GoPro designed its own processor, the GP1, for its cameras. Each of them had to staff a chip team to do it.

The next rung

We’re building the system for autonomous silicon verification. Tapeout’s agents take an SoC from spec through signoff, working from one dependency graph of the design and its runs, and Ledger keeps every result. When the design changes, they only rerun what the change could have affected. Engineers set the direction and keep signoff, and the system carries the rest.

When verification stops needing an army, a small team can build a chip. A chip that once took a hundred engineers can be built by five, and we call that the five‑person chip company.

A bigger market for everyone

Every rung so far has grown the whole industry. More chip designs mean more EDA seats, more wafers through the foundries and more IP licensed. We think the next rung works the same way, and that the most interesting chips of the next decade will come from companies that couldn’t have built one before.

Trust comes first

At DAC and Hot Chips this summer, we heard the same thing again and again, and it came down to proprietary data and trust. One experienced silicon validation leader put it simply. “What can you do that you can trust? That’s the first part.”

We think that’s the right place to start. Today, letting a new tool near a chip program is an institutional event, with IP boundaries, licenses, security review and legal in the way before the tool gets a fair test. We want trying Tapeout to feel like an engineering decision. It runs inside your environment on one bounded piece of a live design, a subsystem or an integration boundary, with nothing in your flow to rip out, and it gives your team a result it can judge quickly. The teams whose job is to find out what works, like advanced development, architecture and prototyping, can start there, and the results make the case for production.

It’s also why Tapeout runs fully air‑gapped on your own machines, why every verdict comes from a tool run or a deterministic check, and why models guide the investigation without ever declaring a result valid on their own.

A new category of chip builders

A hand holding a small bare chip above an open prototype board, a robot arm and camera parts on the bench behind
The team that makes the product, holding its own silicon.

Most companies still shape their products around the chips they can buy, general‑purpose parts built for a much broader market than theirs. We think more companies will build chips around the products they want to make. A robotics company around its perception stack, a medical company around its sensor pipeline, an industrial company around the operation it runs all day. The right chip only has to be exceptional at the thing its maker imagined.

Tapeout Labs exists to expand who can build chips. The five‑person chip company is how far we can see from here. Past that, building a physical product should be open to anyone with an idea. Someday a parent will imagine a toy that teaches their three‑year‑old the alphabet in their grandparents’ language, and build the chip inside it. The only customer will be a three‑year‑old, and that will be enough.

If you’re building toward a chip of your own, we’d like to talk. And if you want to build this with us, tell us what you’ve built.