Our first public demo is at SEMICON India in New Delhi, from 17 to 19 September. SEMICON India is on right now, and we are at startup pod 6 until 19 September. Met us at SEMICON India? Pick up where we left off. Meet us at pod 6 Email us

Close your blockin fewer iterations.

PD-FORGE links every report from every stage, run and tool to the same nets, cells and paths. When a violation shows up at signoff, it traces it back to the stage that caused it.

Request early access See how it works

In closed testing. Production in Q4 2026.

violation at signoff

    Searched–
    Kept in the cone–
    Root cause–
    Tool back-ends
    26
    Synopsys, Cadence, Siemens and open-source tools
    Stages linked
    6
    synthesis to signoff, with every run kept
    Vendor messages
    97
    mapped to one set of check names
    how it works

    Every stage and run, linked at the net and path level

    Today your QoR sits in separate reports for each tool, stage and run. PD-FORGE ties it all to the same nets, cells, clocks and paths, and learns from every run. It is the physical design counterpart of the SoC mental map behind DV-FORGE.

    synthesisGenus, DC floorplanInnovus, ICC2 placementInnovus, FC CTSInnovus, Aprisa routeICC2, OpenROAD signoffPrimeTime, Calibre Closure map every stage and run, linked at the net, cell and path level timing paths nets cells clocks congestion DRC past runs fixes Correlate QoRacross runs and tools Root-causefrom violation to nets and cells Run assistflags a bad run before route
    1. Every tool, every stageGenus, DC, Innovus, ICC2, Fusion Compiler, PrimeTime, Calibre and more
    2. Closure mapevery stage and run, linked at the net, cell and path level
    3. Correlate QoR, root-cause, run assistacross runs and tools, violation to nets and cells, bad runs flagged before route
    Learns from every runEvery run, knob change and fix is kept, so a new hotspot is matched against the ones you have already closed.
    Knows stage-to-stage effectsIt knows how clock buffers placed at CTS show up as detours at route, so a violation is narrowed to the few objects behind it.
    Cross-vendorAn Innovus warning and an ICC2 warning map to the same check, and every number links back to its report line.
    root cause

    Fails at signoff.Caused at CTS.

    Violations show up late but start early. PD-FORGE narrows gigabytes of reports to the violation’s cone and traces it back through past stages, deterministically, before an LLM is asked anything. It is the cone-of-influence idea behind DV-FORGE, applied to physical design.

    Everything your tools writetiming, congestion, DRC and QoR reports and logs, from every stage of every run38 GB
    Correlated inside PD-FORGEevery number tied to its net, cell, clock, path, stage and run, the same way every time1.2M nets
    The violation’s coneits fan-in logic, placed cells, clock branches, the gcells its nets cross, and the same objects in past runs14 rows
    Context for the LLMsmall and clean, so it explains the root cause instead of guessing1.9k tokens

    Not a flow wrapper. Not a log summary.

    The same failing path, as three kinds of tool would report it.

    Flow wrapperruns your scripts, shows a dashboard

    what you getrun_23 finished.
    WNS −0.41 ns, TNS −11.2 ns.
    9 DRC violations.

    Tells you it failed.

    LLM log summaryfeeds your logs to a chat model

    what you getTiming failed on some paths, likely due to congestion. Consider increasing routing effort.

    Guesses from a log too big to read.

    PD-FORGEcorrelates every stage, traces the cone

    what you getRoot cause at CTS: 11 clock buffers in gcell (41,17) made 2 nets detour 1.34× at route. Seen in run 22, fixed there by a CTS blockage.
    Innovus cts/place.rpt:88PrimeTime timing.rpt:48

    Tells you why, where, and what fixed it before.

    in practice

    Less report hunting, more closing

    The same correlation answers everyday QoR questions across runs and tools, and watches your runs so you do not have to babysit them.

    example data
    asked

    Without PD-FORGE:

    example run
    block_top, dense strategyDC, Innovus, PrimeTime, Calibre
        closure loop

        One closure iteration, before and after

        TodayWith PD-FORGE
        Where did WNS go?
        Open timing reports stage by stage and compare by hand
        The stage where slack degraded, and the nets behind it
        Why did this net detour?
        Grep a route log that is gigabytes long
        The gcell, and the CTS step that crowded it
        Have we closed this hotspot before?
        Ask around, then dig through old run directories
        The matching past runs, and the fix that worked
        Is this run worth taking past CTS?
        Find out at route, hours later
        A warning at CTS, with a suggested fix
        What does this ECO touch?
        Rerun the full flow to be safe
        Rerun only the stages the ECO touches

        Fewer iterations, fewer repeated mistakes, signoff sooner.

        your tools

        Cross-vendor from day one

        Synopsys, Cadence, Siemens and open-source flows in one place. PD-FORGE drives your tools and replaces none of them.

        26
        tool back-ends
        857
        flow steps
        97
        vendor messages, one check name each
        855
        stats, each with a unit

        Implementation

        Fusion Compiler
        Innovus
        IC Compiler II
        Aprisa
        OpenROAD

        Timing

        PrimeTime
        Tempus
        PrimeClosure
        OpenSTA

        Synthesis, DFT, LEC

        Design Compiler
        Genus
        Tessent
        Conformal
        Yosys

        Signoff

        Calibre
        Pegasus
        IC Validator
        StarRC, Quantus
        RedHawk-SC

        who we are

        Developed with academia and industry

        Swadeza collaborates with professors at BIT Patna and with Signitude, a fabless semiconductor company.

        1. nowClosed testing
        Birla Institute of Technology logoacademic collaborationBIT PatnaProfessors of the Birla Institute of Technology, Patna campus Signitude logoindustry collaborationSignitudeFabless semiconductor company

        Also from Swadeza: DV-FORGE, the same approach for verification, which signed off OpenTitan Earlgrey, a taped-out root-of-trust SoC, in 30 days, most of it in regression.

        Early access, on-premises

        PD-FORGE is in closed testing, with production in Q4 2026. Talk to us about early access, a deployment or a collaboration.

        Request early access info@swadeza.com
        See PD-FORGE run live at SEMICON India, startup pod 6, in Yashobhoomi, New Delhi, from 17 to 19 September. Plan your visit
        PD-FORGE is running live at SEMICON India right now, at startup pod 6 in Yashobhoomi until 19 September. Find the pod
        Met us at SEMICON India? Pick up where we left off.