RT @RodgersMag: Today I'm glad to say that we are opensourcing @selfdb_io . We welcome all of you to try it out .

You heard it first on @hackernews . We are fully open sourcing @selfdb_io . #OpenSource

RT @RodgersMag: SelfDB: Supabase and Firebase burned, We Stayed Online. The Case for Self-Hosted Resilience. Yesterday, on June 12th, many….

RT @RodgersMag: We’re working on the SelfDB Swift package and are excited about building a strong community around it. If you’ve created….

RT @RodgersMag: 🎉 To celebrate #WWDC25, we're giving back to the SWIFT community! 🎉. Have you built a Swift Package? Do you want to make Se….

RT @RodgersMag: @heyandras @heyandras I would like to add @selfdb_io to @coolifyio . would love to discuss with you. see a demo here : htt….

RT @RodgersMag: Watch me built a React Expo app "Open Discussion Board" in 5 minutes using @selfdb_io. ✅ No complex backend setup .✅ No da….

RT @RodgersMag: Deploying @selfdb_io Locally and in Production - Complete Docker Guide. Learn how to deploy SelfD….

I love Docker—but every "cloud" made me pay just to deploy my own stack. Locked-in, rate-limited, or banned. So I built a backend you can run anywhere with Docker, no strings attached. Finally, full control is back in dev hands.

I got my DB paused by supabase with no warning. firebase burned me with surprise bills. I just wanted to build. So I created a no-BS backend you can actually control. If you're tired of cloud chaos, maybe it's for you too.

Hello ios devs. I built to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Maybe it helps others too?

I created selfdb so that you don't have to pay for supabase of firebase. looking for feedback and early user.

the main dashbord

the main dashboard

I built to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Works very good with cascade. Maybe it helps others too?

I built with cursor to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Maybe it helps others too?

I built to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Maybe it helps others too?

I built to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Maybe it helps others too?

I built to solve my own problem. I was juggling multiple side projects, each with its own DB—Supabase, Firebase—but costs scaled fast. I needed a simpler, unified solution. Maybe it helps others too?

what is your go to selfhosted backend? I struggled with supabase selfhosted because it lacked all the paid features. so i vibe coded . need some early testers.