Compatibility is a feature.

PiG exists to expand the Pi ecosystem, not fragment it.

Pi remains the reference.

PiG aims to faithfully carry Pi’s behavior, architecture, and user experience into the Go ecosystem. Where practical, PiG follows upstream behavior and minimizes divergence.

Divergence is the exception.

When differences are necessary because of the Go runtime, platform requirements, or reliability concerns, they are documented explicitly.

When compatibility is possible,
compatibility wins.

Meet upstream Pi

Built on the work of Pi.

PiG would not exist without the work of the Pi maintainers and contributors.

Their vision, architecture, and commitment to open source created the foundation that PiG builds upon.

Thank you.