Repo Compare › Backend-as-a-service

Supabase vs Appwrite vs PocketBase

A side-by-side look at how actively Supabase, Appwrite and PocketBase are developed on GitHub — popularity, contributor base, commit activity and how quickly issues and pull requests move.

What the numbers say

• Supabase is the most-starred of the 3, with 111k stars — about 1.9× Appwrite's 58k.
• Over the 52 weeks to the snapshot, Appwrite recorded the most commits (14k), against 534 for PocketBase.
• Supabase has closed or merged the most pull requests in its lifetime: 24k.
• Relative to its popularity, PocketBase carries the lightest open-issue load: 0.3 open issues per 1,000 stars, versus 6.0 for Appwrite.

Head-to-head

Snapshot taken 30 September 2026. Refresh with live data

The wide bar is that repository’s share of the largest value in its own row — half the length means half the number. The thin gauge beneath it is the same row rescaled from its smallest value to its largest, which makes a close gap such as 61k against 59k visible; on that gauge the row’s lowest value always sits at zero however big it is, so read it as a spread and never as a quantity. Bars compare repositories with each other and never one metric against another. Colour identifies the repository, matching the dot beside its name. On the two issue rows a longer bar means more open work, which is usually the opposite of better. The highlighted cell is the highest value in a row. “Active / Slowing / Dormant” is a simple heuristic from how recently code was pushed and open issues per star — a starting point, not a verdict. Stars measure popularity, not quality.

Open these in the live comparer →

Related comparisons

• ClickHouse vs TimescaleDB vs QuestDB
• Prisma vs Drizzle ORM vs TypeORM
• Kubernetes vs Nomad vs K3s