Archgen Labs, home. Contact

The future of compute starts with how we design it.

An AI agent for chip physical design, from a single die to a 3D stack.

Contact us Backed by Y Combinator
Ask the agent
archgen agent/ top_ctrlidle
  • SRAM
  • Core
  • NPU
  • PHY

0/8 blocks checked · pick one

memory

  • nothing stored yet
WNS
–
TNS
–
DRC
–
Congestion
–

Built for physical design.

It reads every run, finds why a block is failing, patches the flow and reruns. What worked carries over to the next block, on one die or across a stack.

RTL ▸ SYNTHESIS ▸ FLOORPLAN ▸ PLACEMENT ▸ CTS ▸ ROUTING ▸ TIMING ▸ DRC ▸ SIGNOFF ▸ 3D STACKING ▸

Chips went to 3D,
EDA should too

Logic, memory and I/O now ship as stacked dies. Most tools still treat each die as a flat chip, so the stack is closed by hand.

Partitioning
Which blocks go on which die, and what every crossing costs.
Cross-die timing
Paths that start on one tier and end on another.
Heat and power
A hot logic die under memory changes what will close.
Bonds and TSVs
The interface between dies is now part of the floorplan.

We’re building Archgen to work on the whole stack as one design.

Drag to turn it · move across to open the stack · up or down to pick a dieDrag to turn it · tap a die to pick itrest

Inside a run

One terminal, one block: what the agent reads, changes and keeps.

A sample session on a demo block.
agent.log — archgen
EXPLORER
top_ctrl
  • rtl
  • flow
  • logs
  • memory
    • block_7.fix
    • block_9.fix
  • reports
    • timing.rpt
    • drc.rpt
RR.PD lead

@archgen why is block_7 failing timing?

↳ Found it: the SRAM macro sits too far from the arbiter. Moving it and rerunning.

MM.Floorplan

@archgen fix the congestion near the SRAM macros

↳ Patched floorplan.tcl. Rerun queued.

KK.Signoff

@archgen triage tonight’s DRC report

↳ Triaged. 3 real violations left for review; the rest share one spacing rule.

AA.Timing

@archgen what did we learn on the last block?

↳ Wider macro halos cleared the congestion. Applied to block_9.

RR.PD lead

@archgen summarise the overnight runs for the team

↳ Posted to #pd-signoff.

SS.Architect

@archgen can this core close at the target clock?

↳ Not at 72% utilization. At 66% it closes with slack to spare.

⎇ main● agent: onlinetop_ctrlLn 9, Col 3UTF-8Log