Pocketbase is amazing! So far I had a great experience using it as a backend/database for the app I'm building where I'm using React with Vite for the frontend. I'm using it mainly for auth and for keeping track of paid and free accounts. Some things that I found rather useful:
- It's super easy to host. I was initially thinking of using Appwrite or Supabase but found it a tricky to self-host them, especially Supabase. I could spin up Appwrite quickly via CapRover, but found it an overkill for what I needed.
- View collections [1] make it easy to return just a subset of the data that you need. In my case I'm using a view collection as a join for users and paid_users collections, where I just return their paid through date.
- The fact that you can extend it with Go or JS [2] should make it possible to completely skip having a backend, at least if your needs aren't very complex.
I definitely plan to continue using it for some smaller/side projects. Currently I'm thinking of trying to use it as CMS for an Astro blog and in the future as backend for some browser extensions.
I feel like super easy to host needs to be re-emphasized. We're talking about dropping a single binary into your server and you're off to the races. If only more things were so simple.
The key distinction here seems to be that it uses an in-core database (SQLite), whereas a Go project may depend on an out-of-core database like Postgres, which would then also have to be deployed.
For many projects (especially hobby projects where downtime is tolerable), the former is probably quite sufficient.
Not really because then projects started needing multiple containers and orchestration, and might be fussy about the order the different services come up.
I've been developing on PocketBase for 2 months. The system goes into production in 1 to 2 months.
I'm exceptionally happy with it. I'm developing an webapp for a friend's company and wanted a very simple system to hand-off. The whole thing is running with one binary: Pocketbase. It runs a webserver, server-side Javascript (compiled TypeScript) code, and SQLite database. The single process is hosted on Vultr for $12 per month. My frontend is written in SvelteKit (static adapter) + Svelte + TypeScript.
Pocketbase is well done. The author has been exceptionally responsive to my questions. He is fast and clear.
I have had a few minor issues: The documentation has bare spots (but is very good for most things). I had to write my own CSV loader. (I hope to open-source it.) Writing lots of objects through the CRUD interface is slow. (It's possible to write faster using server-side code.) Unit testing for the server-side JavaScript had to be shoehorned in. And I wish Copilot/ChatGPT could answer questions better. But these issues have been minor, given all my work on the project.
It has some quirks. There's no way to set the 404 page on the webserver. And the binary's location in the filesystem matters. It was designed for the author's use and you have to live with these choices.
As I said, I've been happy using it. It fit my needs exactly: simple and I could code everything in one language, TypeScript. Pocketbase is not high-performance, but I didn't need that. I've had a few ideas for side projects and, when I'm done this work, I'll implement one on Pocketbase because it is that easy.
And, as part of my contract, my friend's company will donate to Pocketbase. :)
I've been using Pocketbase in production for a few months now, with alpinejs on the front end.
The development philosophy is on point. It's genuinely pleasant, pragmatic software which serves a real purpose and it improves weekly without feature creep.
I watch the discussions and issues slowly getting more tiresome as it becomes more mainstream and worry that he'll burn out trying to keep up with the level of support he's offered until now.
I would very strongly encourage anyone using this to generate income to support the project on open collective.
I have been following PocketBase since its early day - what I absolutely love about this project is how it actively tries to avoid complexity and focuses on simple yet minimalist approach. Moreover, the ease of deployment by simply uploading a single binary on the server makes it even more attractive.
After they introduced Javascript support in the backend - I feel it became a serious contender to challenge Remix, Next.js etc. frameworks.
I use PocketBase for mostly everything where I need a back end now. I came across a situation where I needed to write a custom SQL join (technically I could have just fetched all the data and done it in Node, I suppose).
I was shocked at how easy it was to write the query even inserting URL parameters and selecting based on the authenticated user only.
Fully recommend for basically everything. Great app. Not sure it would replace Next or Remix, but definitely add to the stack to simplify.
Bits and pieces. A bedtime tracking app for my kid, a microblog, a TikTok clone, a budget app, a text-to-speech app with translation functionality…
Development experience was outstanding. I primarily use SvelteKit and integrate PocketBase for SSR, so I use the SDK almost exclusively and it’s fantastic. Everything just works exactly the way you would expect.
I can’t imagine anything easier to implement, and as yet, I haven’t found any major gaps in what I can do with it, normally with OOB functionality.
Development velocity is very high and the developer is super responsive on GitHub. The documentation is very good and kept up to date pretty well.
My only real concern is that the project has a pretty poor bus factor, otherwise, I’m very impressed.
I was looking for a frontend I could use out of the box on top of a sqlite database to design and store my wine collection (since I removed Vivino and its 800+ "partners" it shares my data with).
Looks like a single executable, the admin interface and the database I can store on my laptop (and add it to my backup) is all I was looking for. Thank you for PocketBase and thank you for sharing it.
It is great to see the number of good opensource projects in this area. Grist and NocoDB deserve mentions, although more targeted towards database management. It is also amazing that they provide so simple ways to get started (single file/electron)
I've skimmed at the docs, and it's not clear to me how it would deal with:
* Something like row-level access control, so that people can only access the data in tables that belong to them (say clients can only view their own purchases, and also not modify them after they checked them out).
* Integration with the rest of the world, e.g. sending email, acting on triggers, etc.
* Something like CSV export/import.
* Internationalization.
Would that all be possible? Straightforward? Do those all require extending (with go or js)?
Re internationalization, I think you're right. I don't have experience building app/websites, a fortiori with internationalization, so I threw this question in with the lot!
The first point (authn) is inherent to the unextended framework via filter rules.
Most of the remainder requires extension other than authz emails, but extension at its simplest just means adding a plain old JavaScript function to run on a record lifecycle event of some kind - typically [before/after] [insert/update/delete] of <record>. Various GO APIs are exposed to the JavaScript runtime for doing filesystem, cryptography, http, email, etc work.
Out of all the PaaS I tried including Supabase and Appwrite, Pocketbase is the best. Great performance, intuitive features, actually self hosted and a joy to deploy.
Have been using pocketbase in production for a mobile app for a couple of month now and so far it was a _very_ pleasent experience. Together with the JS SDK it is now my go to backend framework for everything where I don't need specialized libraries (like ML stuff etc.)
Example has
1. Auth
2. Route rules
3. CRUD actions
4. Realtime events
5. Storage
Needs refactoring but I really enjoyed working with it, I want to add stripe subscriptions to this taking routes rules to it's limits, not sure how yet, will figure it out.
Been using Pocketbase for almost all of my projects lately. Its realtime database is especially nice to introduce multiplayer functionality with relative ease.
It plus SvelteKit has been a dream to get up and running using the JS SDK.
For CRUD apps, sveltekits progressive enhancement and form actions make it quick to to add simple function to the page. You can store the pocketbase instance, pb, in locals and reference it all over the application.
For more multiplayer things, sticking a client-side subscription to a collection allows updates of elements that can be worked with/added/moved around etc.
I've been using Pocketbase for several projects. While it's a delightful experience for solo-dev to quickly finish a project from backend to complicated frontend, I wish it has bulk-insert out of the box.
More than one server. Sqlite should be thread safe and simple services can scale to thousands of parallal users. If you are OK with some downtime every 6 months when server goes down it will scale well. Deploy/ rollback will be an effort.
Gotcha. And that makes sense for the purpose of the project. Should one have multiple instances of sqlite dbs, what strategies exist to keep them synced?
I'm in this situation right now. How would one go about solving this?
To keep this simple, I'm thinking exporting just the necessary data from each db and inserting that to a stats db (having a source column to each table, referring to the original db). Then load the stats db with Metabase or something.
Migrations on the stats db may be a bit of a pain, as well as making sure that all data is exported and imported correctly every time.
I've been using Pocketbase for personal projects on the machine I use to self-host services. It's great. You get CRUD and real-time stuff for free and I didn't really have to spend much time learning to start working with it and having it running in an LXC.
This just looks like the "Event Bus" [1] [2] [3] pattern, this is not the one from the React world if you were thinking about that. Hooks here are just the following, the "Hook" is just a collection of event handlers.
type Handler[T any] func(e T) error
type handlerPair[T any] struct {
id string
handler Handler[T]
}
type Hook[T any] struct {
mux sync.RWMutex
handlers []*handlerPair[T]
}
It's very useful when you want to make an easily extensible library/framework/application, as you can see in pocketbase/core/app.go you can register handlers for various things that can happen.
I like the idea, but after using it, the query apis aren't expressive enough. I wish I could write SQL instead of making 2+ api calls to get the data I want.
It's a binary called "pocketbase" that you can download and run on your machine. When you run it, it starts a localhost web server. That server includes a web based UI tool that lets you create "collections" (effectively database tables) and insert/update/delete data in them.
More importantly, it provides a JSON API (and a client library) for interacting with those collections.
I think it's more like a self-hosted Firebase - you run it on a server (with a disk drive that can persist the data) to get a hosted API for your apps to talk to.
Hmm... kind of. It's pretty substantially different from Firebase which is defacto NoSQL versus Pocketbase which uses SQL.
Given that it's based on SQLite I'd be very interested to know how well this would work as a true backend for a multiuser site that allows users to interact/post/etc.
If you have ever built a web app backend that consists of a database, a REST API for that database, and a web admin interface to the database - well, this gives you all of that for free, just by running an executable.
Ok so essentially an easy to host activeadmin (rails library). I think the single executable that runs on every os makes it very interesting for usecases where data is generated into a static site
Aren't there entire classes of problems that shouldn't exist for SQLite because it's intended to be an embedded database, as opposed to a client/server architecture like Postgres/Supabase?
Beyond the standalone server mode, I'm able to literally import this as a library/framework right into my Go app (https://pocketbase.io/docs/go-overview/). Having a single binary that contains my custom business logic + a very nice DB/Auth/Admin/... is a very compelling option.
PocketBase is trying to be a simple webserver, code-running backend, and database. I believe the author chose SQLite because it is simple. PocketBase isn't trying to have every feature nor be high performance.
I feel like this will be super interesting when pairing with static site generator such as eleventy. Using static site generator is sometimes difficult because of lacking a web backend and ghost is too heavy for me.
Could you explain a bit more this setup? I have been looking for a way to have a tool to fill pages for a static site generator that's local and then just git push in a simplified way.
The idea is to create a website for my mother, without having to deal with hosting at all (static github pages).
Some static site generators have good support for generating pages from a dynamic source, say API, database or anything you can access using programming language.
See eleventy, for instance, has the “Javascript data files” [1], it run some JS code to generate a list of posts, here we can fetch from pocketbase, then, we can generate pages dynamically [2].
Pocketbase in this case just act as a lightweight CMS.
It is simple, so its single program is (1) a webserver, (2) runs server-side code, and (3) hosts a DB. I'm running a $12-per-month server on Vultr and its only service is PocketBase.
You don't need to host the webpages on PocketBase. If you wanted all your webpages to be on Github Pages, you could do that.
You won’t need to really run server all the time, you can run locally and use it as a lightweight CMS, and run only when you need to edit and generating anything. You can choose to only upload the generated HTML files to GitHub.
See my explanation on my reply to the original post.
I like this for testing and quick/simple database, very useful in concept for building a platform for embedded work, where you don’t need to go down the rabbit hole in the whole full stack tech.
How are database migrations handled in this? Ive never understood how BaaSes are to be used when I need to add a new column to my table and do some inserts into it in the same migration
A lot of these tools just abstract away migrations. But I do know some like Supabase let you clone a copy locally and manually perform migrations if you see fit
Can this thing be used for a forum type site + a minimal game feature with around 5k daily users? How could you scale this with a single common database?
I mostly know Python. Is there something similar in Python? Or the backend language is not relevant, because you mostly use this from JavaScript anyway?
I have been building a project https://github.com/claceio/clace which aims to make building hypermedia based web applications easier. Clace is implemented in go, it uses Starlark (python syntax subset) for application configuration. With Clace, the apps are implemented using Starlark and (go) html templates, HTMX is used for web interface, app developer does not need to write any JavaScript.
If anyone is interested in extending I have done some work on it and can confirm it is quite easy. I extended it to be able to use stripe check it out below:
It can be the backend itself if you just need auth (both authentication and authorization) and your SQL tables to be a REST API. This often suits frontend single page applications in JS/TS and Pocketbase also provides a JS SDK to ease this (with realtime updates). It's a similar model to Firebase but without the lock-in.
However if you want to write more logic you can also import Pocketbase as a library and extend it with hooks, custom endpoints etc. all written in Go.
Edit: Added more info about using Pocketbase with a JS SPA frontend.
You would use it instead of things like Supabase and Appwrite. It gives you a server, a db and easy authentication, authorization with real-time queries like firebase.
Maybe it's not for me, I really don't know what that means. If it only describes itself as "a replacement for <name>" I feel like I'm not the target at all.
Depends on what you consider minimal, but I enjoy working with PocketBase and VanJS[1]. However there is no component library built in (if this is what you were asking for).
Alpine is for example, I want to show/hide a menu on mobile. I want to upload files via drag and drop. I want to have a bin icon over an image when I hover with mouse to delete it. I want to double click an input field to edit it. I want to close an overlay when I click outside of it, or when I press “esc”.
Also modals, although you can do them in htmx very nicely too, so that’s borderline.
Anything that involves network, htmx.
Things that are just frontend, Alpine suits better.
_hyperscript is basically the Alpine equivalent.
It's like the difference between Turbo and Stimulus in the Rails world
If you want a front-end for a single-page webapp, I loved Svelte. It puts all the HTML, JavaScript/TypeScript, and CSS together in the same place. The tutorial is delightful.
BUT, if you need a multi-page webapp, SvelteKit is complicated and not well documented.
It's like saying nginx is better than superbase/firebase. Apples to oranges.
You could replicate PocketBase in Readbean, but you would have to implement from scratch:
- resources with CRUD API and real time subscriptions
- admin UI
- authz & authn system
I didn't say it's better. Why are people always misinterperting what they read (it's like you've never had text interpretation classes at school, or logic lessons to undestand how to infer implications from logical statements correctly)?
Please read again: I said it's vastly simpler (which may not be better for you!) and lighter (just measure it). The comparison is apt for me because the description "open-source backend in one file" matches both projects well and it's something I'm interested in, with readbean being far closer to my alley.
Your initial comment presents Redbean as a comparable solution, which it's not; they serve very different use cases.
Redbean requires you to write server code; Pocketbase does not. Redbean does not offer a realtime database, authentication, an admin dashboard, integrated file storage, or an inbuilt API.
I like Redbean, but it's in a completely different "market sector". It's like comparing a kit car to a luxury car: yes, they both technically serve the same purpose, but one requires much less assembly and offers a much more usable experience out of the box.
They are comparable solutions to the problem "Open-source backend in one file".
I don't care at all about "realtime database, authentication" and whatever, I care about what the title of the post says. For that purpose, Redbean is a nice alternative.
> It's like comparing a kit car to a luxury car
If all I need is a bicycle, a kit car is already over the top but will do. A luxury car makes no sense. You're thinking like everyone has the same needs that you have or something.
Ah, I see - my apologies, I think there's an unfortunate misalignment over the word "backend."
When Pocketbase is talking about a backend, they're talking about something like Firebase, which is a complete backend-as-a-service that implements everything you need for a service where the majority of the logic is in the frontend; it's meant to involve as little backend engineering as possible.
You're referring to the more general, standard sense of the word "backend". I agree with the sibling comment that you're not necessarily wrong in offering Redbean as a point of comparison, but the target user of Pocketbase has limited overlap with the targeted user of Redbean; the people looking for a Firebase-like solution would not be served by Redbean, and your initial post could be read as suggesting that they could be.
I do think the use of the word "backend" here is unfortunate, because it's really referring to something much more specific than the conventional use of the term.
I think people are being a bit harsh but your original comment (especially starting with "It seems to me" which makes it sound like a value judgment) was phrased in a way that did sound a lot like you were implying that redbean was better for the same requirements, although you didn't actually explicitly say that.
I think you would have gotten a more positive reaction if you said something like "As an alternative take on the idea of an "open-source backend in one file, redbean is a much simpler, vastly lighter one-file web server + sqlite DB: https://redbean.dev/" to make redbean isn't necessarily intended to be the same type of "open-source backend in one file"
Anyway, redbean does look really neat even if it's not necessarily totally interchangeable with pocketbase
Wanted to say thanks for the comment because TIL redbean, which in turn led me to learn about Justine Tunney, who appears to be a super-human programmer based on what I've read so far. Lots of inspirational discoveries on HN this weekend for me—Thanks ya'll!
Are you a developer? Because it seems to be geared towards developers. It's something like a all-in-one backend that you can use as a starting point and extend if needed.
Personally, I think the website is clear and concise. Doesn't even have any marketing filler which is a huge plus in my corner.
It is a simple program that (1) hosts a webserver, (2) runs server-side code, and (3) hosts a database. It also has built-in support for logging in and permissions to data.
Thus, if you want to write a simple website that needs permissions, storage, and server-side code, it's a great backend solution. The limitation is that it isn't high performance.
It's like a smaller Supabase, which was an open source alternative of Firebase. So basically a database, authentication, file storage, and backend in one solution.
Pro:
- It will be cheaper when scale
- You have full control of the data since selfhosted
- Easier to extend with custom code
Cons:
- you need to take care of all the hosting, backups, etc
- cant scale to infinity like firebase (but on the other hand when you reach that scale youe firebase bill will be huge anyway)
There’s something to be said about drastically reducing your threat surface too. Locking down 1 server is easier than locking down a fleet. You can still have security in depth inside your server.
TypeScript is support on the frontend for oldtimers like me who have used plain JS for far too long and refuse to accept the torture of unnecessarily untyped languages any longer.
Also as already mentioned by others there exist web APIs.
- It's super easy to host. I was initially thinking of using Appwrite or Supabase but found it a tricky to self-host them, especially Supabase. I could spin up Appwrite quickly via CapRover, but found it an overkill for what I needed.
- View collections [1] make it easy to return just a subset of the data that you need. In my case I'm using a view collection as a join for users and paid_users collections, where I just return their paid through date.
- The fact that you can extend it with Go or JS [2] should make it possible to completely skip having a backend, at least if your needs aren't very complex.
I definitely plan to continue using it for some smaller/side projects. Currently I'm thinking of trying to use it as CMS for an Astro blog and in the future as backend for some browser extensions.
[1] - https://pocketbase.io/docs/collections/#view-collection
[2] - https://pocketbase.io/docs/use-as-framework/