<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prisma on Gaurav.dev</title><link>/tags/prisma/</link><description>Recent content in Prisma on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/prisma/index.xml" rel="self" type="application/rss+xml"/><item><title>Supabase and Prisma: Useful Shortcuts, Different Responsibilities</title><link>/posts/supabase-prisma-managed-backend/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>/posts/supabase-prisma-managed-backend/</guid><description>&lt;p&gt;Supabase and Prisma frequently appear in modern TypeScript stacks, but they solve different problems. Supabase is a managed backend platform centred on PostgreSQL, authentication, storage, realtime capabilities, and server-side functions. Prisma is an ORM and database toolkit that gives application code a typed data client and migration workflow. They can complement each other, but neither removes the need to design the database.&lt;/p&gt;&#10;&lt;h2 id="what-supabase-accelerates"&gt;What Supabase accelerates&lt;/h2&gt;&#10;&lt;p&gt;Supabase can eliminate weeks of commodity platform work. A team can provision PostgreSQL, authenticate users, store files, subscribe to changes, and expose controlled data access quickly. This is valuable for prototypes, internal products, SaaS applications, and teams that want managed operations without giving up relational data.&lt;/p&gt;</description></item></channel></rss>