Today we are making the @orioledb Patent freely available to the Postgres community
Oriole is a storage extension for Postgres which uses Postgres' pluggable storage system. It's a drop-in replacement for Postgres' existing storage engine (Heap).
Our north star is to upstream Oriole to be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres (if the community want it!)
We announced the acquisition of Oriole over a year ago. Since then, we have been working on cleaning up the legal structure and finalizing the asset transfers.
We have wrapped up all legal activities, and we fully own US Patent 10,325,030 (“Durable multiversion B+-tree”).
@supabase is making this Patent explicitly available to all Oriole users (including proprietary forks) in accordance with the open source license.
Oriole benchmarks show that it is around 5.5x faster than the default storage engine (Heap):
@supabase Series D, led by @Accel
A huge thank you to our community. Some of you who have been supporting from the start - maintaining open source code, organizing meetups, supporting in our Discord and subreddit
Nothing changes from here - we're doubling down on developers
Dropped today: our official @Supabase UI Library 🚢
It leverages the @shadcn "registry" feature and is compatible with Next.js, React, and Tanstack
Includes:
◆ Login components
◆ Dropzone for storage
◆ Realtime cursors/avatars/chat
◆ And (one I love): AI Prompts
Full details about the features and how it's built:
https://t.co/f99AVg8i4v
And the docs:
https://t.co/owgZPaUiei
This is the first release of Launch Week 14. We have something coming on Thursday which will make this an important tool in your postgres toolbelt
The reality of building web apps in 2025 is that it's a bit like assembling IKEA furniture. There's no "full-stack" product with batteries included, you have to piece together and configure many individual services:
- frontend / backend (e.g. React, Next.js, APIs)
- hosting (cdn, https, domains, autoscaling)
- database
- authentication (custom, social logins)
- blob storage (file uploads, urls, cdn-backed)
- email
- payments
- background jobs
- analytics
- monitoring
- dev tools (CI/CD, staging)
- secrets
- ...
I'm relatively new to modern web dev and find the above a bit overwhelming, e.g. I'm embarrassed to share it took me ~3 hours the other day to create and configure a supabase with a vercel app and resolve a few errors. The second you stray just slightly from the "getting started" tutorial in the docs you're suddenly in the wilderness. It's not even code, it's... configurations, plumbing, orchestration, workflows, best practices. A lot of glory will go to whoever figures out how to make it accessible and "just work" out of the box, for both humans and, increasingly and especially, AIs.
@freak4pc@supabase hi 👋
there is a doc about limitations with realtime postgres changes feature
tldr: a couple thousands msg/sec throughput with rls, and ~10x more without rls and filters (approx calc at the bottom). at that point u'd need to switch to broadcast
https://t.co/I5CmC5cfRZ
Introducing the Supabase Book by @activenode
He's spent a year writing it and it's one of the most comprehensive resources on the internet. He'll teach you @supabase by building a Multi-Tenant platform
↓ read about it here
https://t.co/uR0R5BJYue
wanna use @supabase but continue using your existing auth? introducing the best of both worlds:
bring over your auth from Auth0, Firebase, or AWS Cognito and it’ll just work with your Supabase project’s Data API, Storage, Realtime, and Functions.
#supabase#launchweek 12
Snaplet is now Open Source:
https://t.co/Iq4INiQ5WP
Last month, @_snaplet shut down. But that's not the end of the story. Some of the team joined @supabase, and we asked @appfactory if he'd like to open source the tech they built.
Today they released 3 new projects: ↓🧵
it looks like someone beat us to our own @ProductHunt launch, so f*ck it - we're doing it live
↓↓ if you're a PH user, jump and give it a 🔺
https://t.co/qtaukNZHtj