Hosted version

[sdnts]

Been seeing some interest from people willing to host a (secured) instance of Studio.

I have two use cases in mind:

1. They want to hide it behind an authenticated endpoint, AKA they handle authentication: This would require them to be able to override all static asset paths from the CLI. Fortunately, this option already exists in StudioServer, so it is (hopefully) only a matter of exposing it to the CLI

2. They expect Studio to handle authentication: This is more complicated and honestly might need some product intervention.

If anyone else reading this can think of other use cases, please leave them down below!

[thebiglabasky]

The main options that we have considered for packaging so far:

• Electron app
• Cloud-based app

What's the use case for a self-hosted Studio?

[sdnts]

Most people I've heard from, want to use Studio as an admin dashboard for their DB, that's what I mean by "hosted version". Not sure if the Cloud version is the same thing or not.

[heymartinadams]

For your consideration, @madebysid: https://tauri.studio/

Built using Rust :) and much smaller, snappier, apparently. https://news.ycombinator.com/item?id=27155831

[martzoukos]

Now that we have released a hosted version of our cloud app, I guess we can close this issue :)

• The link for this is cloud.prisma.io
• A nice blog post that explains what you can do (and what's in it for the future) can be read here: https://www.prisma.io/blog/prisma-online-data-browser-ejgg5c8p3u4x

[JannikZed]

@martzoukos now that this hosted version does no longer exist: any new recommendations? :D

[Kuro091]

Hey I'd love to see some movements from this. Our use case is that

• We need some quick editing/data checking for development work that our testers are looking to do themselves. It'd be great if we can somehow give them accounts to access the studio somehow.
• Clients can edit some contents themselves but don't want to commit to full-fledged CMS solutions out there.

I haven't did much digging regarding the cloud version there but it requires the db to be public ? Which is not ideal

[heymartinadams]

Definitely one of those “value-add” features for us as well. Yes, we can spin up localhost, and, yes, we can access and modify the data that way... but wouldn’t it be so much nicer if we didn’t have to.

Down the road, it would be even cooler if we could have various levels of access built-in: support teams being able to only read or read/write certain tables, for example.