What is PocketBase and why does it use SQLite to create a small backend?

Published on 2026-10-20 by frfrand

PocketBase explicado desde cero: SQLite, autenticación, API en tiempo real, límites y casos de uso.

PocketBase is a lightweight backend that combines an SQLite database, API, authentication, and real-time functions into an application you can run yourself. It stands out because with just a few steps you can have something that normally requires configuring several pieces.

But "small" does not mean "suitable for any project." It is worth understanding its advantages and its limits before falling in love with the idea.

What makes it special?

In many projects, a developer sets up a database, an API server, authentication, and perhaps a service to synchronize changes. PocketBase attempts to offer an integrated set for certain types of applications.

It uses SQLite as the database engine. This means that data is stored in local files managed by that engine, with transaction mechanisms and concurrency control.

SQLite is a serious and widely used technology; it is not a "toy database." However, its characteristics and way of operating are not identical to a PostgreSQL deployed as an independent service.

An example: a small internal application

Imagine that a team of five people wants to save ideas, assign tasks, and attach documents. It needs users, permissions, and records that update from several devices.

With PocketBase you can model collections, configure rules, and develop a frontend that uses its interfaces. For this type of application, it can be a quick way to experiment.

Even so, access rules need to be checked. If the frontend hides a private task but the API returns it to anyone, the application still has a serious security problem.

What does "in real time" mean?

Some systems allow a connected client to receive notifications when a relevant change occurs. This is useful for a task board or a screen that displays new notifications.

It does not mean that your entire application synchronizes correctly without effort. You have to manage disconnections, possible simultaneous changes, and what information each user should receive.

A real-time update does not replace a transaction that protects data against incompatible operations.

When is SQLite convenient and when is it not?

SQLite simplifies many scenarios because you do not need to manage a separate database server. It is great for local tools, small applications, and projects with suitable access patterns.

But if you need a distributed write architecture, complex replicas, or loads that do not fit its access model, it is reasonable to consider PostgreSQL or another solution.

Do not make the decision based solely on the number of users. It matters especially what operations they perform, how often, and what recovery guarantees you need.

What about backups?

As part of the storage depends on files, it is essential to know which directories contain the data, what happens during the copy, and how to perform consistent restorations.

Copying files manually while a database is writing is not automatically a safe strategy. Use the backup mechanisms recommended by the project and test a real restoration.

If you host PocketBase on a server, you also need to think about disk persistence. Losing a temporary container should not mean losing your users' accounts and documents.

Is it recommended for production?

It depends on the state and guarantees of the version you use, the criticality of the business, and how much maintenance you are willing to assume. PocketBase's own documentation warns about its evolution and the compatibility of versions prior to its final stabilization.

For a prototype or internal tool, the compromise may be reasonable. For a critical payment or medical history system, continuity, audit, and support requirements may lead you to another architecture.

How would it be used with ArduMaker?

You can evaluate running the binary and storing its data persistently on a VPS managed from ArduMaker, reviewing compatibility and version requirements. You will also have to configure HTTPS, permissions, backups, and process monitoring.

In short: PocketBase lets you get started quickly with an integrated SQLite-based backend. It's attractive when you want simplicity, but initial ease never replaces thinking about data, security, and recovery.

Sources: PocketBase Documentation · SQLite Documentation.