Yesterday we let the cat slip out of the bag that we had recently acquired the talent behind LibSQL Studio and have helped take on the responsibility of maintaining that repo. Although some of you caught on even before that...
So you might be asking yourself, why did Outerbase acquire LibSQL Studio? Don't they already have a database GUI that supports LibSQL?
Well, there are a few reasons:
The engineer behind it is an absolute genius.
The product is phenomenal, with many features we want to (and already have been) adding into Outerbase.
We want to strengthen our open-source and local dev stories.
Meet Visal .In
Visal .In is the mastermind behind LibSQL studio. This isn't his first DB GUI rodeo either - he has also built QueryM, a cross-platform Postgres & MySQL GUI (sounds familiar, right?). When we came across his work, we knew we had to reach out. We were so impressed by everything he was building, mostly solo. Thankfully, we convinced him to join the team, and he's been an amazing addition to our already stacked roster. Here's what Visal had to say about joining Outerbase.
I've always aspired to build the best database tool. After speaking with the Outerbase team, I realized our visions align, and I believe that working with them will help me achieve my goal faster.
Outerbase Improvements
Invisal has hit the ground running at Outerbase. You may have noticed a shiny new query editor featuring built-in AI queries. That was all Visal. We were missing some core features that users expect from a query editor, and he knew exactly how to build them.
This is just the beginning. Our goal is to bring much of what LibSQL studio users know and love into Outerbase, including the ability to connect to local databases, .db files, CSVs, and more. It's been amazing to work with Visal in the few weeks we've been jamming together, and I can't wait to see what we ship next.
Future of LibSQL Studio & Outerbase
Now you might be asking, "What about my beloved LibSQL studio? Are you going to ruin it? Backburner it? Something worse?!" The answer is a resounding "No!" We're actively working on taking the best of both worlds and bringing them together. This means LibSQL studio will benefit from our entire team working on it and will continue to remain open-source and available to all. In fact, we're so excited about this that we're going to use LibSQL studio to help tell our Local Dev story. More on that soon!
In the meantime please star LibSQL Studio on Github and join our Community Discord to learn about all future updates!
