Will the new Rust-based Turso engine get a standalone server like sqld?
I’ve been looking into the new Turso engine written in Rust, and I’m really interested in using it for a self-hosted BaaS.
From what I understand, the new engine is primarily an embedded database, while the old libSQL sqld provided a proper standalone server with HTTP access, authentication, replication, and standalone/primary/replica modes.
The new Turso CLI does have a --sync-server, but that seems to be a local server for the Turso sync protocol rather than a full database server comparable to sqld.
So I’m wondering:
Is there a plan to build a standalone server for the new Turso engine?
2
u/hatemjaber 10d ago
I submitted a PR that will allow multiple database on the local sync server and have plans on adding the jwt and other features that exist on libsql because I have similar interests in self-hosting. I was told they don't oppose the contribution and at the same time I received feedback that my solution might not be how they would do it. It's still open and waiting on a senior member to review. There are quite a few things that need to be added to create the control plane and my idea was to build on top of the sync-server they allow you to run local to get closer to a libsql experience.
5
u/crabferris 11d ago
Your read is right. The new engine (the from-scratch Rust rewrite, formerly Limbo) is deliberately embedded-first, and the sync-server is just the endpoint for the sync protocol, not a general purpose DB server the way sqld was.
I haven't seen an open-source standalone server for the new engine yet. The server half right now is the sync protocol plus their hosted cloud, not a self-hostable sqld replacement. Whether one is actually planned is a maintainer question, so I'd ask in the tursodatabase GitHub discussions. That roadmap moves fast and you'll get a real answer there instead of guesses.