Supabase

“A supervisor can do their visit virtually. They don't have to drive to the house, they don't have to be present. They can monitor everybody's charting and the care the patient is receiving because it's all in Supabase, reliably and in real-time.”

“The fact that Supabase has a HIPAA-compliant aspect makes it so you can be audited. If you're an agency using this, you have complete audit logs of everybody logging in, logging out, who's charting what. It makes it really easy to monitor the database without seeing things I shouldn't necessarily see.”

“I'm not a full-time software engineer with a big team behind me. I'm someone who saw a problem in home care every single day and wanted to fix it. Supabase made the backend feel possible. It gave me the tools to build something real without getting buried in complexity, and it gave me the confidence that I could protect the information this app was built around.”

“A lot of nurses, when they go into a home, they're going into a situation that they've never been in. They've never met the family. They don't know how old they are, what issues they have. This app is supposed to be an easy solution so that when a nurse walks into a home, they can go straight to giving someone the best care they need and deserve.”

“As a solo developer, it seems daunting at first. You never know how something is going to come about. It might happen faster than you want, but just go with it. Don't be afraid to make something. And Supabase makes it easy to build quickly and ship.”

“Every time a fundamentally new technology appears, Supabase ships the integration the same week. Almost nobody talks about this, and it might be the most underrated thing about them. A company building on Supabase inherits that speed.”

“We've been through some heavy procurement and security reviews, including companies that verify identity for a living. The database layer has never been a question. Not negotiated, not remediated. No questions, every time.”

“We were a bit nervous, and then we realized Google auth was already built into Supabase. It took a couple of minutes to configure. We shipped it almost immediately, and the prospect was impressed with how fast we moved.”

“If we ever had to leave Supabase, that's what I'd miss first: never having to be our own database administrators.”

“pgvector played a real role in the decision, and it keeps earning it. We're happy with the performance. Our retrieval augmented localization runs on Postgres, period.”

“SOC 2 isn't a growth milestone anymore. It's table stakes. If you don't have it, you aren't taken seriously. GDPR, SOC 2 Type II, where data lives, which regions: the architecture was shaped around those requirements from day one. As a localization infrastructure company, we treat security seriously.”

“We'd known Supabase since it launched. We'd tried it and knew: next company, this is what we build on. It's relational, it's managed, and we never think about upgrading Postgres versions ourselves. It was an obvious choice.”

“We had all this data and we couldn't touch it the way we wanted. You can do the basics, but every serious question we wanted to ask of our own data ran into the limits of the store we picked on day one. The workarounds we built were incompatible with how we want infrastructure to work.”

“We were getting so many feature requests that we had to stop and reconsider what the technology actually was. What our users were describing wasn't a translation tool. It was a platform they could engineer on.”

“Buy the encapsulation, and spend your resources only on your own category. Supabase encapsulates the database layer so completely that we get to spend every engineering hour on localization engineering infrastructure, which is the only place our customers can tell the difference. Our users put it in a way I can't improve on: Stripe for payments, Supabase for databases, Lingo.dev for localization.”

“Don't try to build everything yourself, even though you can build a lot with agents today. There are cool solutions out there, like Supabase. Use them, and focus on building your product instead.”

“Without Supabase, we'd have needed at least two engineers to get the same functionality. That's time we'd rather spend building what we sell to customers.”

“When we started working with larger enterprise customers, especially banks, we needed certifications to show we had a strong security posture. Supabase already had a lot of that in place, which made it much easier for us to get certified.”

“There was a lot of experimentation and pivoting in that first year and a half. Supabase let us try things and iterate fast, and it scaled with us the whole way, through the pivots and after we finally committed to a direction.”

“Supabase is compelling to us because it's a complete solution. You get features you'd normally lack in a simple Postgres setup, and when you're a lean team that wants to focus on building instead of infrastructure ops, those extra features matter to us.”

“You're building a game, you hope it will be successful and grow, but the truth is most games won't. Supabase's pricing is really accessible, and it feels like you're intentionally trying to support smaller developers with that kind of structure.”

“If we were to write all of this authentication, cloud saves, and remote config ourselves, the stuff we use Supabase for, I think it's realistic to say we wouldn't have all of those features built out for users. We've got limited resources so Supabase has really helped us be way ahead from when we started.”

“We can now roll decks out remotely. We don't have to update the game at all. It was always a big source of stress that's now gone.”

“That requires some sort of record of those things on all the devices that can then be married up and turned into one single source of truth. We were able to do that through the Supabase database tables.”

“Supabase having REST endpoints is massive. There are some tools where they're SDK only, and that's problematic when you're cross-platform, because you're suddenly managing two, three, four SDKs, and they're not always kept in sync. Whereas REST endpoints with our Lua code base means we just write a very lightweight wrapper and we're done. It's very easy for us to expand to other platforms.”