On demand, not on order
A board you can start using now, instead of waiting for stock, budget approval, or your turn with the shared one.
Product
Real FPGA boards, by the hour.
Spin up a board, flash your build, and run your tests against real silicon. When you're done, tear it down and pay only for the hours you used.
Why it exists
A design is not done when the testbench passes. It is done when it runs on real hardware — and getting real hardware is usually the slow part.
Dev boards are expensive, out of stock, or in use by someone else. The board you need for this project is never the one you already have, so hardware becomes a procurement problem that interrupts engineering. Forge is the answer we built for ourselves: rent the board by the hour, the way you rent compute.
The same thread runs through everything we build: the agent that writes the code, the board it runs on, the libraries it pulls in. Forge is the board.
How it works
Pick the board your project needs and bring it up. It is yours alone for as long as you need it.
Program the board with your bitstream the way you would at your desk. Your toolchain and your workflow stay exactly as they are.
Run your test suite and keep the results. When you are done, the board goes back to the pool and the meter stops.
What's inside
A board you can start using now, instead of waiting for stock, budget approval, or your turn with the shared one.
Timing, I/O, and board-level quirks only show up on a real FPGA. Running your tests on one catches what the testbench never will.
Bring a board up from a script and put it back when the run finishes, so hardware sits inside your test loop instead of beside it.
Pay for the hours a board runs, not for the board itself. Hardware becomes an operating cost instead of capital sitting in a drawer.
Also from Lilith Semi
Chock, Harbor, and Forge — one for the agent that writes your code, one for the libraries it builds with, one for the board it runs on.
A security-first harness for AI agents. The sandbox is built into the harness rather than wrapped around it with bwrap. Agents work in a locked-down copy of your project, under a policy that governs what they may read, run, and change, and their work comes back as a commit you choose to keep.
Learn moreA hardware component library in Dart for ROHD — Rapid Open Hardware Development. Reusable, tested hardware building blocks you depend on like any other software package.
Learn moreTell us which boards you need and what you're testing. We will come back with questions and next steps.