11–20 of 51 posts
That said, in comparison to other similar software:
- For standalone use: there's a lot of similar software like budibase, baserow, nocodb, etc. which is heavier weight (distributed as a docker container) but more featureful
- For use with a custom frontend: I'm not sure I would pick it when it's AGPL, since PocketBase is roughly comparable as a single-file sqlite-based backend and it's MIT license.
I'm trying to understand what am I looking at. MS Access like db+ui in browser, with homemade engine and no sql support? What are guarantees here, concurenncy, isolation, single user? Not much on the main page.
Undb handles reference for you, which is always most hard/difficult part to handle in most lowcode system, so it's not just a database frontend. It's like MS access when you link reference in the access ui, but undb can also handle lookup & rollup in browser
I've been in the midst of developing my own frontend (SPA/PWA) data storage solution, using IndexedDB (and the Dexie library), so I've been watching all of the recent announcements about the wasm-sqlite implementations and wondering if I should probably just switch over to that. If, for nothing else, for the exportable .sqlite file that would be available without having to do a custom "Database Export".
With that in mind, I'd be much more interested in a clean library that abstracts sqlite data access, but stores it in the same format. That way, I could implement the library in my frontend app to store data, and then use the sqlite files that can be exported to load into your Undb app to inspect them (I'm thinking for, say, error debugging or whatever). Similar to how I might pull a client's db backup and load it into Microsoft's SSMS management app.
But hey, maybe that's in the roadmap! And, even if not, it's still a great utility all on its own. And it seems to be a solidly made and well-styled app. Very interested to see if other people have some obvious use cases for this.
NocoDB is neat, but looks like it's a single vendor-driven project that could go open core or die altogether if funding dries up.
Baserow also looks good, but already appears to be open core and another single-vendor project.
Undb might be a more community driven project over time. Hard to say - it looks like there's 6 contributors currently and there's not much info I could find by way of governance or company info to determine where they want to go.
Single-vendor open core (SVOC) can move quickly but it tends to degrade and disappoint over time. I would love to see a project of this sort that's actually trying to be truly community driven.
That's probably unrealistic, but I don't know if there's a ton of value in an open core solution over just using Airtable or Notion if some of the best bits are closed anyway and the fully closed alternatives are more polished and straightforward.
This looks pretty neat and I might try it out for personal stuff. That said, in comparison to other similar software: - For standalone use: there's a lot of similar software like budibase, baserow, nocodb, etc. which is heavier weight (distributed as a docker container) but more featureful - For use with a custom frontend: I'm not sure I would pick it when it's AGPL, since PocketBase is roughly comparable as a single…
This is awesome. Reminds me of Access. So many people need this that don’t know they need it
Earlier quoted context omitted.
Undb handles reference for you, which is always most hard/difficult part to handle in most lowcode system, so it's not just a database frontend. It's like MS access when you link reference in the access ui, but undb can also handle lookup & rollup in browser
GP didn't ask about references. They asked what the tool actually was, and asked about the types of guarantees it provides compared to a known RDBMS.
This looks pretty neat and I might try it out for personal stuff. That said, in comparison to other similar software: - For standalone use: there's a lot of similar software like budibase, baserow, nocodb, etc. which is heavier weight (distributed as a docker container) but more featureful - For use with a custom frontend: I'm not sure I would pick it when it's AGPL, since PocketBase is roughly comparable as a single…
thanks for you feedback, there is more feature on our roadmap and it will always be local friendly and easy to host. I'll consider to switch undb to MIT someday.