commaai/openpilot

Choose FrogPilot if you want a more customizable, community-driven openpilot fork and are comfortable with significant divergence from upstream. Choose upstream if you want the newest fixes, cleaner maintenance, and the lowest-risk path.

Choose this fork if you want a customized, Toyota-centric openpilot with extra tuning and configuration controls and you do not need comma 3X. Choose upstream if you want broader hardware support, newer fixes, and a more standard deployment path.

Choose this fork only if you specifically need its custom vehicle support or legacy behavior. For most adopters, upstream openpilot is the safer and more maintainable choice.

Choose this fork if you want a focused openpilot derivative centered on ALC/ACC and can live with reduced breadth and heavier divergence. Choose upstream if you want the widest car support, fastest feature flow, and the least integration risk.

Choose this fork only if you need its custom branch behavior or vehicle-specific modifications. If you want current upstream fixes, active maintenance, and lower integration risk, upstream is the better default.

Prefer this fork only if you specifically want its custom tuning and legacy behavior. If you care about current car support, active maintenance, or upstream safety and tooling improvements, upstream openpilot is the better choice.

Choose this fork if you want a specialized, deeply modified openpilot branch and are willing to manage divergence. Prefer upstream if you want the newest supported behavior, easier maintenance, and clearer compatibility.

Choose this fork if you drive Subaru and want a community branch with Subaru-focused support; choose upstream if you want the latest broadly maintained openpilot features and fixes.

Choose this fork if you need a customized openpilot derivative with its own deployment and UI/tooling stack. Choose upstream if you want the broadest support, the fastest flow of new fixes, and the least merge risk.