TrailBase, a self-hosted database platform, has released version 0.12.0 with significant changes to its API filtering system. The update brings both technical improvements and community discussion about what it means to be a Firebase alternative.
Major API Overhaul Creates Breaking Changes
The latest release completely restructures how developers filter data through the API. The old simple format has been replaced with a more complex but powerful system that supports nested expressions. This means existing applications will need updates to work with the new version.
The change affects how developers write queries. Previously, excluding values used a straightforward approach, but now requires a more detailed syntax following standard query string conventions. While this adds complexity, it enables more sophisticated filtering operations that weren't possible before.
Query string conventions: Standard ways of formatting web addresses to pass data between applications
API Filter Format Changes:
- Old format:
col[ne]=val - New format:
filter[col][$ne]=val - Example complex query:
?filter[$or][0][col][$gt]=v_max&filter[$or][1][col][$lt]=v_min
Community Questions Firebase Alternative Positioning
The release has sparked broader discussion about how TrailBase and similar tools position themselves in the market. Some community members argue that calling something a Firebase alternative should mean it offers the same real-time features that made Firebase popular in the first place.
I'm irked how Firebase alternative has come to mean hosted database with an API layer. I mean, the key pitch of Firebase has always been that it's a realtime database.
However, others point out that Firebase itself has evolved far beyond its original real-time database roots. After Google's acquisition, Firebase became a comprehensive platform for building applications without traditional backend development. This broader interpretation makes the alternative label more reasonable.
Technical Improvements and New Features
Beyond the API changes, version 0.12.0 adds several practical improvements. The platform now includes a Swift client library, expanding support for iOS development. The admin dashboard shows version information and links to release notes, making it easier for administrators to track updates.
The development team has also updated underlying dependencies, which typically improves security and performance even if users don't see immediate changes.
New Features in v0.12.0:
- Nested, complex filter expressions
- Swift language client implementation
- Release version display in admin dashboard
- Updated dependencies
- All existing clients updated for new syntax
Positioning Against Established Players
TrailBase continues to differentiate itself from larger competitors like Supabase through its single-executable architecture. This design choice makes it easier to self-host and typically uses fewer server resources. The platform appeals particularly to organizations prioritizing data ownership and reduced dependence on public cloud services.
The project acknowledges inspiration from both PocketBase and Supabase, showing how the database-as-a-service space continues to evolve with different approaches to similar problems. Each platform makes different trade-offs between ease of use, features, and deployment flexibility.
While the API changes in v0.12.0 create short-term challenges for existing users, they lay groundwork for more sophisticated applications. The community discussion around Firebase alternatives also highlights how rapidly this space is developing, with different tools serving different needs within the broader category of backend-as-a-service platforms.
Reference: v0.12.0