KiCad.
Through its own interface.

A bounded PCB interface for an engineering tool with its own object model.

  • A separately packaged KiCad integration
  • A curated KiCad 9/10 PCB surface
  • Owner-assigned identity and explicit policy grants

Where the boundary is.

The integration is GPL-3.0-or-later. A deterministic fake IPC test does not establish interoperability with a live KiCad process.

What the evidence says.

The reviewed source documents deterministic IPC and conformance coverage. Fake IPC evidence remains distinct from a real KiCad interoperability certificate; read the integration compatibility notes before using real projects.

This is an editorial summary of a frozen source revision, not a probe of your installation. A successful job does not automatically certify other versions, environments or operations.

Start with the contract.

Read the integration’s own README and security notes before enabling it. Owner-assigned identity, required grants and application dependencies must be configured explicitly. Registration alone does not authorize execution.

Open the KiCad source documentation

For the common model, read drivers and providers and permissions and consent.