Replenysh uses Supabase to implement OTP in less than 24-hours

Summary

Replenysh builds infrastructure connecting brands with local communities to track, monetize, and recover used packaging and materials. The engineering team previously maintained their own backend infrastructure, pairing custom Twilio and password authentication with a Haskell server and a Postgres database on Heroku. Seeking to accelerate development velocity and minimize ongoing DevOps maintenance during a codebase refactor, Replenysh required an alternative backend platform that preserved relational Postgres and Row Level Security. The team selected Supabase over alternatives like Firebase because it provided native Row Level Security alongside built-in authentication tooling. By adopting Supabase Auth, Replenysh successfully implemented an SMS one-time password system in less than 24 hours before deploying their mobile application to production.

Context

Replenysh connects brands with communities to recover materials, requiring reliable mobile-first authentication for global brand users. The team historically managed custom APIs, Twilio OTP, password auth, and a Haskell server with Postgres on Heroku. During a major refactor, they sought alternative hosting to speed up development and reduce DevOps maintenance without losing Postgres and Row Level Security.

Approach / What changed

Replenysh migrated from their Heroku-hosted Haskell and Postgres backend to Supabase. They adopted Supabase Auth to implement SMS one-time password authentication while preserving their relational Postgres database and Row Level Security policies.

Takeaways

• Replenysh completed and pushed live their SMS OTP authentication implementation in less than 24 hours using Supabase Auth.
• Firebase was evaluated for rapid startup, but Replenysh rejected it to maintain a relational database with Postgres Row Level Security.
• Prior to adopting Supabase, Replenysh operated custom OTP and password authentication using Twilio, a Haskell server, and Postgres on Heroku.

Related reading

• Supabase · Jul 28, 2021

  Mobbin uses Supabase to authenticate 200,000 users

  Mobbin originally launched its mobile design search platform using Firebase, quickly growing to hundreds of thousands of registered users. As the platform scaled, the team faced user friction because Firebase Authentication did not merge accounts sharing the same email address across different providers. Furthermore, mutative Firebase Function failures threatened document data integrity, and multi-round-trip document queries drove high monthly costs across five million API requests. To resolve these challenges, Mobbin migrated its backend to Supabase, adopting its GoTrue authentication service and underlying Postgres relational database. This migration resolved authentication conflicts, safeguarded data consistency, and reduced monthly infrastructure expenses since Supabase does not charge on a per-API-request basis.

• Supabase · Oct 14, 2021

  Hacktoberfest Hackathon Winners 2021

  The organizers of the second open-source Hacktoberfest Hackathon announced the top ten projects across five distinct categories, selecting a winner and runner-up for each. Awarded projects include Pickle, a privacy-focused developer analytics service featuring realtime event synchronization, and CourseBuddy, a collaborative study platform for students. Other winning entries encompass the Feedback widget for sentiment collection, a utility management Flutter application, and Spookd, a Halloween-themed game built with Framer and connected to Supabase. Runner-up projects feature tools such as og:supa for generating Open Graph preview images, Relm for community management, Party Parrot as a Service, the TLWR path logger for Flutter, and the uwudaily mood-logging website. All winners receive custom gold medal shirts, runners-up receive silver medal shirts, and every participant receives a limited-edition participation tee.