An entire backend in a single Go executable: PocketBase embeds SQLite with realtime subscriptions, authentication and user management, file storage, and an admin dashboard, all behind a REST-ish API. SQLite runs in WAL mode, which outperforms client-server databases for the read-heavy workloads typical of small and mid-sized apps. Authentication supports email/password, one-time passwords, and 15+ OAuth2 providers including Google, Apple, and GitHub, with stateless tokens. Clients subscribe to record changes over server-sent events, and official JavaScript and Dart SDKs cover web, mobile, and Flutter frontends. Collections, rules, and API access permissions are managed visually in the admin UI. When you need custom logic, extend it with JavaScript hooks running in the embedded JS VM of the prebuilt binary, or import PocketBase as a Go library and compile custom business logic into your own single-file backend. File storage attaches uploads to records with thumbnail generation for images and optional S3-compatible external storage. All state lives in one pb_data directory, so backup is a directory copy and upgrade is replacing a binary - one of the lowest-maintenance backends you can run. The contrast with Firebase is the point: where usage-based pricing scales with reads, writes, and bandwidth, PocketBase runs the entire backend at flat hosting cost, and the data is a plain SQLite file you can copy anywhere. MIT-licensed.

The name means steam in Bulgarian, and the job matches: Para is the boiler room that powers your application's backend so you never build one from scratch. You store plain JSON objects through a REST API and get them back persisted, indexed for full-text search, and cached on every write, without designing schemas or gluing three systems together yourself. One server hosts many applications at once, each with its own table, search index, and cache, so a client project, a side app, and an internal tool can share a single deployment without sharing data. Users sign in with social accounts, LDAP, or SAML and receive JSON Web Tokens, while resource permissions decide exactly which objects each client may touch. Queries go beyond key lookups: field, wildcard, geo point, and more-like-this searches all run against the same stored objects. Signed webhooks notify your own endpoints when data changes, and an MCP server lets AI assistants manage configuration, data, and search against the same backend. The admin Web Console handles users, objects, backups, and permissions from the browser, and client libraries cover JavaScript, PHP, Java, C#, Android, and iOS. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.