Replies: 1 comment
-
|
I'm not entirely sure that I understand the purpose of this discussion but I'll keep it open for now in case people want to coordinate and work together on a Python SDK. With that said, I feel that I need to clarify something. First, if you haven't already, please read the warning at the top of the FAQ. If you already read it, then you should know that the only way an SDK will be considered "official" by me is if I decide to take the responsibility to work on it and as mentioned in several other discussions, for now I'm NOT planning doing that until a stable v1.0.0 is released because simply I won't have the time to maintain them. There is nothing wrong if a community maintained Python SDK exist, but you and other people can't force me to take the responsibility to "officially" maintain it. I can abandon the project today if I decided to. My responsibility ends with me just sharing my code and nothing more, so please adjust your expectations. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
tl;dr: Opening a serious discussion about whether PocketBase should have an official Python SDK.
Background & Motivation
I recently built a small Python app and decided to turn it into a micro-SaaS.
It felt like a perfect opportunity to give PocketBase a real shot in production.
Along the way, I ran into some friction points:
At that point, I had two options:
Because I know Go, the app was small, and LLMs can speed up porting, I chose option (2).
But it made me realize that many Python developers won't, and shouldn't have to, make that tradeoff.
Why an Official SDK Matters
Why Now
PocketBase is ideal for micro-SaaS projects: fast, lightweight, and developer-friendly.
But Python dominates the AI and automation space, and the next wave of indie SaaS tools will be Python-based.
A native, well-maintained SDK would unlock huge potential for that audience.
Next Steps
This isn’t a request for the core maintainers to build it, nor a solo offer to do it myself.
It’s a proposal for alignment: to agree that an official Python SDK is worth pursuing, discuss a minimal viable scope, and, if there’s consensus, I’m happy to help find a sponsor and coordinate contributors.
Related Issues
Related Discussions
18 votes ·
Beta Was this translation helpful? Give feedback.
All reactions