https://www.prisma.io/ logo
Join Slack
Powered by
Hello, not as much a question as it is curiosity. ...
# orm-help
m
Hello, not as much a question as it is curiosity. Did Prisma go from being $45 a month to $15 a month? Is there any difference in features being offered for that price?
👍 1
🤔 1
m
Whhhaaaaat!? Now its cheaper in the cloud than doing it myself on AWS!? DOH!
w
Daaaamn 😨
l
I have similar questions. Is the $15/month for teams > 3? It appears that Prisma Cloud no longer hosts the Prisma runtime??
t
Thats what i've also noticed, so you would need to connect your server in any case?
l
@taikn I think so. Before Prisma Cloud connected to your database and was the server. That doesn't appear to be true anymore, but I could be very wrong.
t
😑
p
I’m also wondering (and a bit confused to be honest) about this.
t
ok and then there is a serverless hosting for $99
l
Yeah, good spot. I suspect that's the "old" Prisma cloud?
t
probably
n
thanks for your questions, I'll collect them and answer tomorrow 🙂
🙌 5
Did Prisma go from being $45 a month to $15 a month
No. We added the Prisma Cloud Connect feature, that let's you use Prisma Cloud (the dashboard, databrowser, workspaces...) with your own Prisma server. We plan to add many more features to Prisma Cloud over the coming months. Using Prisma Cloud is free for up to 3 users, but starting 4 users it is $15 per user per month. Additionally, we are currently finalizing a new offering called "Serverless Hosting" which is the improved version from the $45 Prisma server hosting we offered before. There will be a wide range of setup options, and different sets of features, and this plan starts at $99+. If you are interested in that, please reach out to 
<mailto:sales@prisma.io|sales@prisma.io>
to learn more. If you signed up to Prisma Cloud before May 15th, you still have access to the Prisma servers hosted by us. If you have any questions about that, please reach out to 
<mailto:sales@prisma.io|sales@prisma.io>
as well. Hope that covers your questions 🙂
p
Thank you @nilan, so then the classic Prisma Server hosting is (will be) phased out?
l
What's the server less hosting's included database?
n
@picosam, If by classic Prisma Server hosting you refer to the offer before May 15th, correct, new users have no access to that. @lawjolla, we are looking to support any DB that Prisma can connect to. What DB would you be interested in?
l
Probably Aurora but I'm still researching as launch grows near(er). 🙂
👍 1
p
Same here
_…except that my researching is already done 😛_
parrotwave6 1
n
sounds good! when launch comes nearer, feel free to reach out with a mail so we can discuss your options 🙂
💯 1
p
Nilan, the cloud pricing is per-service?
n
per workspace
a workspace can have many services
p
For instance, ideally I would deploy a Prisma Service (or am I talking about a Server?!) for staging and one for Production
(Local deployment would be on my local machine docker)
n
You can deploy two services to one server, or one service to one server each. You can then connect the one or two servers to the same workspace.
p
Ok, I guess what I cannot see right now is how do I deploy a Prisma Server
That would then be the Serverless Hosting offer?
n
You can deploy that wherever you can deploy Docker (like Digital Ocean, AWS EC2, AWS Fargate, Kubernetes...). Or you reach out to learn more about the Serverless Hosting offer 🙂
correct!
p
Ok, but sorry, what happens right now when I use 
prisma deploy
with an endpoint like 
<https://us1.prisma.sh/public-scarlethowler-440/>
?
Doesn’t that deploy to a Prisma Server that’s owned by you folks?
w
To a public shared server though, with limited performances
n
We call that "demo server" now, not public server 🙂
👍 1
p
Right, that’s fine for staging!
n
but yep, it's a shared server with rate limiting and other limits
ah perfect
p
@nilan apart from the naming, would you say that’s ok for a private staging server accessed by a couple of developers less than 100 times a day?!
n
one aspect is that the demo server is continuously upgraded so you might run into unexpected situations with that
👍 1
p
By “private” I meant that the data is inaccessible by those who do not know the prisma secret
n
if you have an account and deploy to the demo server, only your account (+ team members) can access it. that's why we moved away from calling it "public"
👍 1
your current endpoint is not linked to an account though (you can tell because the "workspace segment" starts with "public-), so anyone knowing your endpoint can deploy a new secret to the endpoint and read/write all your data
😨 2
😂 1
p
Oh!!
n
🙂
p
LOL
Well, how do I create a “private” endpoint on your “shared” server?
n
- you are currently logged in in your CLI - (optional): run 
prisma init
- you remove the 
endpoint
property from 
prisma.yml
(if any) - you run 
prisma deploy
you can double check with 
prisma info
the endpoint will contain your private workspace name 🙂
p
❯ Demo server                Hosted demo environment incl. database (requires login)
Cool, so I can pick this option and that would deploy to the shared server
💥 1
💯 1
@nilan sorry, another question: does my 
slug
need to remain a secret (or otherwise anyone could, just like for the public server, overwrite my deployment if they know it)?
l
For my own two cents aside, I like the $99 plan more than the $45. Adding the database is a big improvement. AWS ✌️
🤝 1
n
@picosam, no only workspace members can deploy there, and you should have a service secret setup so queries are only possible with that secret
👍 1
2 Views
Open in Slack
PreviousNext
Powered by