Workloads and budget
Model layers or tensor shapes, plus your area, power, latency and process targets. That is the whole input.
in: ONNX / MLIR shapes, PPA budgetTechnology
The engineering behind AI-powered chip design exploration.
Architecture, compiler mapping and physical implementation are searched together, every candidate is measured at increasing fidelity on real EDA flows, and every result, good or failed, teaches the engine where to look next.
01 Position
It sits between your workload and your design flow, and decides what is worth building. Your architects, compiler engineers and EDA tools stay in charge of building it.
02 The loop
You bring workloads and constraints. The engine proposes candidates, compiles your models onto each, measures them at increasing fidelity, and learns from every result, good or failed.
Model layers or tensor shapes, plus your area, power, latency and process targets. That is the whole input.
in: ONNX / MLIR shapes, PPA budgetThe planner proposes hardware and finds the best compiler mapping for each candidate, across more than a million combinations.
array · dataflow · precision · memory · tiling · loop orderAnalytical estimates, RTL simulation, synthesis, then place-and-route on your flow, cheapest first. Every result is checked, every failure kept.
milliseconds · seconds · minutes · hoursA Pareto front of designs, each with RTL parameters, its compiler mapping and the evidence behind it. Then the loop learns and runs again.
out: designs, mappings, run historyAdaptive EDA budgeting
Each tier costs orders of magnitude more than the one before it. Instead of a fixed filter, the planner chooses where to spend: a candidate moves on only when it is likely to improve your trade-off, and every result updates that judgement.
Illustrative. The actual split is decided per project, from your budget and what the engine learns.
03 Design intelligence
A generic optimizer learns which settings scored well. The engine works across the layers of the stack, runs controlled experiments on its own generators, and keeps every result. Choose a layer to see what it reasons about.
Sizing starts from the work, not from last year's chip. Shapes and data reuse decide how large the array should be, how much on-chip memory pays for itself, and which dataflow keeps the multipliers busy.
Each design is judged by how well your workloads really run on it, not by its peak numbers. The compiler path is generated per candidate and verified bit-exact on that candidate's RTL.
A large scratchpad is worth its area only if the compiler can use it, and a mapping is only possible if the hardware has room for it. Choosing both together avoids paying for silicon the software never touches.
Failures are not discarded. They teach the engine where not to spend the next expensive run, and the next project starts from that experience.
04 The platform
Built on standard tools your teams already know: MLIR for the compiler, open or commercial EDA for measurement.
Array shape, dataflow, precision, memory hierarchy, banking and implementation settings, each judged by how well your workloads map onto it.
Tiling, loop order and memory allocation chosen per architecture, lowered from standard MLIR to the accelerator's own command stream, verified bit-exact on its RTL.
From millisecond estimates to routed layouts, on-prem or in your cloud account, against open tools or your existing synthesis and place-and-route scripts.
Models where designs fail and why, from timing margins to routing, and chooses the run most likely to move your Pareto front. It improves with every design history it sees.
05 Engine architecture
The planner proposes, two generators make it real, the evaluation fabric measures it, and design intelligence turns every result into the next decision.
06 Integrations
Open tools run in the technical preview today. Commercial flows are connected through your existing scripts during a design-partner engagement, on your machines.
07 Where it is going
Each step widens what the engine can design while keeping the same promise: every recommendation measured, every mapping verified.
Measured on our technical preview: generated RTL in Verilator, OpenROAD-flow-scripts on the ASAP7 predictive 7 nm kit.
Explore every buildable architecture, follow one compile from MLIR to the command stream, and check the estimate against RTL simulation. Or bring your workload and talk to us.
hello@zenedgex.in