Pilot

Request a Red Chili Pilot

We’re opening pilots for RTL and verification teams whose engineers already work with coding agents.

We need repository access inside your network, one engineer as our contact and the list of tasks planned for the period. We scope every pilot together, so tell us about your block.

Your email is required so we can reach you. The rest is optional, but it helps us shape the pilot around your team.

How a pilot works

  1. Step 1

    Pick one block

    A design or verification block your team is working on now, and the coding agent your engineers already use.

  2. Step 2

    Red Chili moves in

    It runs inside your environment, on your machines. It makes no model calls and sends nothing out.

  3. Step 3

    Work as usual

    For a few weeks your engineers and agents take on their planned tasks, each starting from a Red Chili briefing.

  4. Step 4

    See the difference

    You get a report on agent spend per task, changes that pass your checks the first time and time to get productive on the block, compared with how the same work ran before.

Questions teams ask

Does our RTL leave the building?

No. Red Chili runs inside your network, makes no model calls and sends nothing out. Your coding agent keeps using the model your company already approved.

Which coding agents does it work with?

Any coding agent that speaks MCP, which covers the major ones, plus a command line for scripts and CI. Using something else? Tell us and we connect it.

Which languages and flows?

SystemVerilog RTL and verification, with the simulation, lint, synthesis and physical-design flows around them.

What does a pilot cost?

We scope every pilot with you, around one block and the tasks planned for it. Tell us about yours and we come back with a proposal.

How is the value measured?

On your own tasks, before and after: agent spend per task, changes that pass your checks the first time, and how fast engineers and agents get productive on the block.