I've been fascinated with the ability to create a database per-tenant since I first discovered Turso, even before I joined the team. Soon after I joined I wanted to see if it was possible to push the boundaries of that to "per user". Turso introduced earlier this year a product called "Multi-DB Schemas" which lets you create a database using another databases schema. With this feature, the idea of creating a database per-user isn't so difficult. Almost all of my demos using Turso use this feature, so I decided to put together a repo containing the code to get started! "Multi-DB Schemas" are still in beta, so let us know what you think, and what we can do to improve.

Awesome work, @notrab! The concept of a database per user is truly innovative, and leveraging Multi-DB Schemas makes it even better. I can already see how this will simplify many developers' workflows. Looking forward to exploring the repo and testing it out, especially the demos you've put together. Any plans for a following AMA to discuss best practices? Keep it up!

Great product! Been using it for well over a year now, rock solid! Congratulations on the launch @notrab

Congrats on the launch of the Turso Per User Starter, @notrab! This is a game-changer for multi-tenant applications, especially with the per-user database capability. I'm excited to see how this will enhance scalability and UX. Looking forward to exploring your repo and trying it out! Keep pushing the boundaries!

This looks great, @notrab I love how much you and the Turso team are constantly innovating. I mean the isolation this provides alone is amazing. I can't wait to check it out!

Great Product! Now, this is even more amazing! All the Best for the Product Hunt Launch!

Per User Database Starter is a game changer for developers needing to manage user-specific data! 📊🗂️ Its efficient and scalable approach simplifies handling individual user data, making it perfect for building personalized applications. Excited to see how this tool will streamline development and improve user experience! 🚀👏

Amazing work, @notrab! The concept of having a database per user with the help of Turso’s Multi-DB Schemas is quite innovative. The Next.js boilerplate looks super useful for developers. Are there any specific security considerations we should keep in mind while implementing this?

Congrats! The flexibility of creating a database per user is incredibly powerful for developers. @notrab

Great job, kudos to the team behind!

Hey Jamie, The Per User Database Starter sounds like a powerful tool for building multi-tenant applications. How does it handle scaling as the number of users increases? Congrats on the launch!

This sounds incredibly innovative! 🚀 The idea of a database per user using Turso's Multi-DB Schemas is fascinating and opens up so many possibilities for customization and security. 🛠️ Quick question: Are there any specific use cases or industries you’ve found where this "per user" database model shines the most? Would love to hear more insights and check out the repo! 👏 @notrab

Cool concept @notrab Good luck with launch today!

This looks like a super useful tool for anyone creating multi-tenant apps, love how you pushed the multi-db concept from per-tenant to per-user, definitely helpful in making database management easier, curious where you see this going in the future, like maybe integrating with other types of databases or adding more customization options, have you looked at similar tools like Supabase or Firebase to see what features they offer?

Found this new Next.js boilerplate because a friend mentioned it, gotta say I'm not sold yet, having a database per user might be overkill and could get messy, is it scalable enough for larger projects? And what about security?

Wow, I've always thought making a database per-user was next-level stuff, really digging the potential here, seems super useful for anyone diving into multi-tenant apps, keep pushing the boundaries and can't wait to see how this evolves 💡

So you're saying we should test this "per-user" database thing? Seems cool but honestly the "Multi-DB Schemas" being in beta makes me cautious, any plans on stabilizing that soon or adding more features to it?

I stumbled upon this from a friend and while it's an interesting concept, I'm not sure if creating a database per user is the best way to go, isn't it a bit overkill for smaller apps, also curious, has there been any major security concerns around this method also maybe look into better integration options?

Curious to know, can this setup handle very datasets efficiently?

Cool idea. Would love to give this a try in the future.