MenuClose
Nine engines,
one shared context
One suite from spec and architecture through physical verification and signoff.
The layer that drives every engine below it.
Escanor
Local-first CLI. Drives the whole flow from the customer’s own machine.
FlowBit
Flow management. Owns the flow graph across all nine engines.
Silicrate
PDK and IP management.
Every tool below is written by us. All nine engines are complete end to end.
- Engine 01
Spec & Architecture
Turning a written specification into a structure the rest of the flow can read.
- EasyDesign
- Engine 02
RTL Design
Register maps and IP packaging, generated rather than hand-maintained.
- RegBit
- IPCatBit
RegBit - Register automation. Published earlier as RegMap.
- Engine 03
RTL Quality & Static Signoff
Catching design faults while the RTL is being written, not at signoff.
- LintBit
- CDCBit
- VisSDC
- VisUPF
- DFTBit
LintBit - RTL linting. · CDCBit - Clock-domain crossing analysis. · VisSDC - Timing constraints. · VisUPF - Power intent. Free and open source.
- Engine 04
Functional Verification
Testbenches, simulation and waveform debug in one loop.
- TBGen
- SimBit
- WaveBit
- Engine 05
Synthesis & DFT
From RTL to a netlist, with test structures and power accounted for.
- Stella
- ScanBit
- PowerBit
Stella - RTL synthesis.
- Engine 06
Floorplanning
Placing the design and delivering power to it.
- Tessera
- PDNBit
- GhostCell
- Engine 07
Timing / Parasitic / ECO
Closing timing and carrying late changes without losing the context.
- SAC
- ExtractBit
SAC - Static timing analysis.
- Engine 08
Power Integrity & Reliability
Power integrity, electromigration and thermal, before tapeout.
- PIBit
- EMBit
- ThermalBit
- Engine 09
Physical Verification & Signoff
The last mile of checks before silicon.
- Lexa
The 26 tools named above are the ones we describe publicly; the 50 counted at the top of this page include the supporting binaries each engine ships with. Every one is written and functional. 5 are public and demo-able on your own machine today; the rest release with the design-partner beta.
If a rerun is not bit-identical, the result cannot be trusted at signoff
This came back from engineers more often than any feature request. A team that cannot reproduce a result re-verifies work it has already done, and pays for the same run twice.
Bit-identical reruns
The same input produces the same result, on every machine, every run.
Offline signed licences
No licence server, no daemon, no seat contention.
Nothing leaves the network
Air-gapped teams are fully supported. No telemetry.