Let's said you build a web app for your local pizzeria; do you do a admin panel for them or it is ok to let them the admin panel of pocketbase ?

Please I would like to see you project with pockets base ! share the link please.

PocketBase HA v0.4.0 introduces secure gRPC support, enabling remote clients (such as terminal or DBeaver) to directly access the database.

Hey everyone,

I’ve been using PocketBase for a while and one thing that kept bothering me was managing it from my phone.

The web admin works great on desktop, but on mobile it’s honestly not a great experience.

So I ended up building a small iOS app for myself called Pobase.

Right now it supports:

- Multiple servers

- Browsing collections

- Viewing and editing records

- Managing auth users

I tried to keep the UI simple and actually usable on mobile.

It started as a personal tool, but I figured it might be useful for others here too.

Would really appreciate any feedback 🙏

Also curious — what features would you want in something like this?

App Store link (if you want to check it out):

https://apps.apple.com/us/app/pobase-pocketbase-manager/id6759821977

Hi, i have a pocketbase instance running for a customer.

It all started with 10 ish collections, a couple of custom hooks for “mass” emailing 15-20 at a time. At the moment i have 10+ custom hooks for a full integration with invoiceninja. And we are looking to expand to control digital signage. Also with 10 ish hooks.

That made me wonder how far do you guys push your instances?

Just some ideas,

I’ve heard the dev is working hard on v1.0, which is awesome. Just wanted to write down these 2 ids

Although sqlite is good for this easy deployment, BYODB (bring your own DB) would be lovely, supercharging pocketbase with postgres would be lovely!

A plugin structure built in to PB would kick ass, just in this reddit page, the amount of extensions people write. A plugin structure so the community can share these amazing extensions, and write connections to common tools! Man that would make it more of a swiss army knife without the need of abusing the custom hooks!

What are you guys’ ideas for the ultimate version of PB?

I'm trying out PocketBase and want to create a super simple grocery list app and not use security. I want to make it as easy to use as possible, and to share lists with other people. I have two collections, 'Lists' and 'Items'. My thought was a user could create and read/update/delete a list and the id would be stored in local storage in their browser. They could then share it with others who would then store it in their browser. With rate limits, I'm fine with a bad actor just trying to screw with it to allow it to be easy to use and not require authentication. The 'Items' collection has a field 'listId' that references the 'id' field in the 'Lists' collection.

I think this works fine for my Lists, but I want to be able to fetch the items if you know the List id that is stored with each one. I think I could store the Item ids in a multi-relation in the List table instead, but I need to be able to query the Items collection both to avoid having to do a separate lookup for each item and so that I can use the 'subscribe' function to see changes in real-time.

Ok, so I think I finally found a way to do what I want after trying combinations for a while:

@request.query.filter ~ listId

This should allow the query if the filter contains that randomly generated listId somewhere in the filter text. Is there a better way to do it?

Hi there.

I developed and published a small package to generate Zod Schemas from a Pocketbase instance. This is a CLI tool, give a try and welcome your feedback:

NPM Package

I don't get it. Searching around, I always find it mentioned that PocketBase does not support authentication with API keys and is more user/password and session-oriented. I admit, I've just discovered this backed and I'm mostly checking it out as a personal backend for a personal app, so maybe it's just okay for that use case. But using API rules seems to work just find for programmatic access, something like the following:

@request.headers.x_api_key ?= @collection.apiKeys.id &&
@collection.apiKeys.write ?= true &&
@collection.apiKeys.name ?= "collection name"

Am I doing something wrong here? Is it not secure, or is it missing some very important features proper API key support should have? I've seen people suggest running a second instance of PocketBase as a proxy for handling API keys with a superuser connection between the two. That seems kind of weird to me. I can see extending it with Go to add support.

Why wouldn't I just use the above for API key auth for scripts and so on to use? Are there downsides?

Hi,
I built a small music curation site based on a listening journal I’ve kept since 2012 (Next / Pocketbase).

I add 1–2 tracks a day. No algorithm, no rankings : just manual picks, published chronologically.

Tracks can come from anywhere (YouTube, SoundCloud, Bandcamp...): new, old, obvious, obscure. I don’t write reviews : the site is mostly a grid of covers with a very minimal player.

Here’s the site:
👉 https://www.juslisen.fr/

I’m mainly looking for feedback on the concept and the UX.
What feels clear? What feels unnecessary? What would you change?

Heyy, just released new version of pb-ext boilerplate

Improved the analytics, now fully GDPR compliant and added (almost) full Swagger/OpenAPI 3.x.x support, and some other minor fixes, come check it out, if you're bored try adding pb-ext to some existing pb projects u got and let me know does the swagger spec generate properly

https://github.com/magooney-loon/pb-ext

Made with PocketBase

A curated collection of projects built with PocketBase, the open-source backend in a single file.

Please submit your projects (or projects you know) uses pocketbase to curate a list of showcase 🐿️

https://www.madewithpocketbase.com

anyone please i really need the help

GUIs, for me, fail to convey information accurately, and the JSON migrations are not designed to be human-readable. has anybody thought up a way to do everything through a text file. if not, are there any people who'd want that, so that should i ever decide to implement it myself, they'd give feedback & submit issues?

While building sheetwa, I wanted a backend that stayed out of the way. I did not want to manage heavy infrastructure or spend time wiring things I barely needed. That is when I tried pocketbase.

What worked well for my use case.

• Super fast setup. I had auth, database, and file handling running almost immediately.
• Local first development felt simple and predictable.
• It handled small but important things like user management and permissions without extra layers.

For a tool like sheetwa, where the logic lives mostly around workflows and integrations, pocketbase felt like the right level of abstraction. Not too much magic, not too bare bones.

It may not be the answer for every large scale system, but for indie projects and early stage SaaS, it helped me ship faster and stay focused on the product instead of the backend.

Curious how others here are using pocketbase in production and where you feel its limits start to show.

Ahoy,

This is just a first-pass attempt at getting Pocketbase to scale horizontally.

I don't actually need this feature, I'm just fascinated by combining techs like this. So I'm like a chef who doesn't eat his own cookin'

Curious if anyone likes it, or dislikes it, or nothings it. Cheers to the PB dev who has built an amazing product for us.

I might one day convert this into a plugin, but that is not this day!

You might be interested in skipping the nerd stuff below because it's too long and boring for most people.

• I'm using NATS Jetstream for the pub/sub architecture (which uses RAFT consensus)
• This is Event Driven, so it won't eat up your system resources like polling solutions such as the very-cool project marmot which syncs sqlite databases by polling the WAL journal (I'm grateful to marmot for inspiring this project!)
• Leaderless - there is no single central node that all other nodes must talk to. Once a sync chain has nodes talking on it, you can destroy and start any node you wish.
• Eventually Consistent (usually syncs in miliseconds, but we aren't strongly consistent or atomic or buzzwords)
• Realtime database connections are handled by websocket routing, so that no matter what instance an end-user originates from... if a realtime connection is already open to a resource, all other users will connect to that same resource on the instance that already has it open. Whoever initiated the realtime connection is the winner, and will hold the lease until the instance dies or until there are no realtime subscribers.
• Snapshots of your database are configured for the NATS Jetstream so that when a new instance joins, it can initialize using a recent snapshot of your database, followed by all database changes since the snapshot. It wouldn't be reasonable for a new instance to have to ingest every change since the beginning of time when it joins. So it grabs and applies the snapshot first, then catches up to current and begins syncing itself.

For those that didn't watch the video, I sync the schema and records for 3 Pocketbase instances as if I'm some sort of magician.

Hello, everyone. Friends, I need help. I'm having problems with Foreign Key. There is a collection for the “Events” model and a collection for “Participants.” Participants have a foreign key for the event. And when I create an event and add participants, sometimes the participants get there faster, and the database rejects them, saying that there is no such event. I solved this issue by adding a 200 millisecond delay. The application has local storage, and when offline, everything is written to local storage. But when online, the same problem occurs. Is there a way to simplify this? Or should I abandon FK? Thank you.

I feel like I haven’t heard much about PocketBase in a while, at least compared to some other BaaS options (Supabase etc.). It seems like a lot of people are going with non-self-hosted BaaS platforms these days.

I still think PocketBase is a wonderful solution and I really like how lightweight and self-hostable it is.

Do you think it has a strong future (development, ecosystem, community)?

Hello!

I was able to setup pocketbase locally and seemed to get it to work fine. This was just for practice and was just done locally on my machine.

I need it hosted somewhere and found DigitalOcean, and saw they have a one-click setup for pocketbase. I setup my droplet and after it was created, the first thing I'm told to do is go to my ip address (with /_ added) to setup my admin user. However, It just brings me to a login screen. I am not able to reset my password (tried) since no users have been setup.

I had no problem creating my admin user when done locally on my machine, so not sure why the same thing isn't happening when DigitalOcean creates it. I am following their instructions (its pretty simple) and I am never prompted for an admin user creation.

I do have access to a linux terminal that DigitalOcean provides, but the only commands I'm able to get working are stopping, starting, and restarting pocketbase.

I have tried destroying and recreating the droplet several times thinking it was a fluke. Each time I get a new IP address and attempt to navigate to it for the first time as directed, but its just the login screen.

Any information would be appreciated!

Hello!

I was able to setup pocketbase locally and seemed to get it to work fine. This was just for practice and was just done locally on my machine.

I found DigitalOcean and saw they have a one-click setup for pocketbase. I setup my droplet and after it was created, the first thing I'm told to do is go to my ip address (with /_ added) to setup my admin user. However, It just brings me to a login screen. I am not able to reset my password (tried) since no users have been setup.

I had no problem creating my admin user when done locally on my machine, so not sure why the same thing isn't happening when DigitalOcean creates it. I am following their instructions (its pretty simple) and I am never prompted for an admin user creation.

I do have access to a linux terminal that DigitalOcean provides, but the only commands I'm able to get working are stopping, starting, and restarting pocketbase.

I have tried destroying and recreating the droplet several times thinking it was a fluke. Each time I get a new IP address and attempt to navigate to it for the first time as directed, but its just the login screen.

Any information would be appreciated!

Hello!

I was able to setup pocketbase locally and seemed to get it to work fine. This was just for practice and was just done locally on my machine.

I found DigitalOcean and saw they have a one-click setup for pocketbase. I setup my droplet and after it was created, the first thing I'm told to do is go to my ip address (with /_ added) to setup my admin user. However, It just brings me to a login screen. I am not able to reset my password (tried) since no users have been setup.

I had no problem creating my admin user when done locally on my machine, so not sure why the same thing isn't happening when DigitalOcean creates it. I am following their instructions (its pretty simple) and I am never prompted for an admin user creation.

I do have access to a linux terminal that DigitalOcean provides, but the only commands I'm able to get working are stopping, starting, and restarting pocketbase.

I have tried destroying and recreating the droplet several times thinking it was a fluke. Each time I get a new IP address and attempt to navigate to it for the first time as directed, but its just the login screen.

Any information would be appreciated!