[micw]

> We will absolutely be supporting KiCad

I wonder why there's no standard API for autorouting so that a particular EDA must be supported. I'd love to see autorouter as a standardized HTTP endpoint so that I can run one locally or even buy Autorouter-As-A-Service. E.g. I'd happily pay for TopoR¹ as a service for some projects while others are fine with classic rouing.

¹) https://de.wikipedia.org/wiki/TopoR

[seveibar]

Software innovation in EDA seems pretty slow and is more IP-sensitive, so there hasn't been a huge proliferation of cloud services. We're trying to bring some up some standards that make EDA more web-friendly, like the Circuit JSON[1] format and the Simple Route JSON format[2], but it'll still be years before the tools support web-first standards (kind of reminds me of png vs webp)

[1] https://github.com/tscircuit/circuit-json

[2] https://docs.tscircuit.com/advanced/simple-route-json

[buescher]

The de facto standard external autorouter workflow is through specctra files.

[micw]

At lease easyeda has support for http based autorouter endpoints. They seem to wrap a version of freerouting in this protocol