Discofork
Repository brief

pocketbase/pocketbase

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:49:55.941Z
3mo ago

pocketbase/pocketbase

PocketBase is a popular open source Go backend project that packages an embedded SQLite database, realtime subscriptions, built-in file and user management, an admin dashboard UI, and a REST-ish API into a single portable app or library. It is actively maintained, not archived, and has strong adoption signals with 57,226 stars and 3,233 forks.

GitHub
Loading tags...
Stars57,226
Forks3,233
Default branchmaster
Last pushed2026-03-30T05:51:18Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if PostgreSQL support is the requirement and you are willing to accept ongoing merge and compatibility work. Stick with upstream if you want the broadest PocketBase compatibility and the lowest maintenance burden.

Choose this fork if PostgreSQL compatibility is the primary requirement and you are willing to absorb significant upstream lag and maintenance risk. Stick with upstream PocketBase if you want the most portable, actively current SQLite-based experience.

Prefer this fork only if its local customizations are specifically what you need and you are willing to own the maintenance burden. If you want the latest PocketBase features, fixes, and lower upgrade risk, upstream is the better default.

Choose this fork only if PostgreSQL support is the main requirement and you are prepared to maintain a stale, heavily diverged codebase. If you want current PocketBase features, fixes, and lower maintenance risk, upstream is the better default.

Prefer upstream unless you need this fork’s specific 2022-era operational tweaks and are comfortable owning a heavily stale codebase. This fork is a better fit for legacy customization than for new projects or anyone wanting current PocketBase behavior.

Prefer this fork only if its specific local fixes and workflow changes matter more than staying current with upstream. If you want an actively maintained baseline with fewer compatibility risks, upstream is the safer choice.

Choose this fork only if you specifically need its custom behavior and are prepared to maintain a stale, highly divergent codebase. If you want a broadly compatible PocketBase base with active upstream fixes, upstream is the safer choice.

Choose this fork only if its storage and behavior changes are specifically useful and you are prepared to own divergence. If you want the safest path, the upstream project is the better default because this fork is stale and significantly behind.

Prefer this fork only if you need its custom behavior and are willing to own the maintenance burden. If you want current PocketBase with minimal risk, upstream is the better default because this fork is stale and materially divergent.

Choose this fork only if its local patches are specifically required. For most adopters, upstream PocketBase is the safer default because this fork is stale, substantially behind, and likely missing many newer fixes and maintenance improvements.

pocketbase/pocketbase · Discofork