Since PlanetScale removed their free tier, I was hoping to alternatives to their service. I tried quite a few but they’re all producing errors during deployment that I cannot fix or find solutions to. Anyone else currently facing the same problem or have experience using different mysql service providers? Thank you
2 Likes
Hello,
I understand the inconvenience caused by PlanetScale removing their free tier. Here are some alternatives that you might consider for your NextJS project:
Supabase: It’s a popular alternative that offers a Postgres SQL database with a generous free tier and is compatible with Prisma.
Neon.tech: This is a Postgres database that can be configured to work with Prisma. It’s been recommended for its ease of use.
Turso: While it’s not a MySQL provider (it’s libSQL), users have reported positive experiences after switching from PlanetScale.
Xata: They offer a free tier with 15 GB of storage and have documentation for integrating with Prisma.
AWS SQL Database: Some users have moved to AWS’s SQL database, which also has a free tier available.
I hope the information may helps you.
Best regards,
Yvonne Rhodes
Has anyone succeeded in converting to any of these? I’ve tried, and failed. Im a noob to backend too so my instincts suck.
TLDR: in order to use the postges dbs, do we need to convert the project to using postgres instead of mysql?
My specific context: (can you tell me what im doing wrong?)
I’m new to backend development and attempted using vercels postrgess database storage instead of planet scale, and was trying to follow along with this tutorial. I tried using this database without converting the prisma datasource provider from mysql to postgres. I thought they would be interchangable based on how people talked about them, but maybe thats not how it works with prisma.
I’ve gotten just about to the very end and am hitting this error whenever building in vercel:
Environment variable not found: POSTGRES_URL_NON_POOLING.- a variable thats provided by vercel on product connection to the vercel database. So it’s there, but when I reference it in my prisma.schema datasource db object, and vercel builds, the value isn’t found. It’s like the project isnt connected to the database, even though I can confirm its there through vercel.
My guess is I need to do the conversion to postrgres for the entire project, but that’s just a shot in the dark. Anyone have any wisdom on the subject?
You guys can use Railway,
It has a free trial plan that doesn’t require a credit card, all you need is login using your email or github account
1 Like
Thank you very much! Railway works for me 
I use the database connection URL provided by Railway to replace the original database URL in the .env file and it works for me.
2 Likes