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.

Takeaways

1. 1

   Replenysh completed and pushed live their SMS OTP authentication implementation in less than 24 hours using Supabase Auth.

2. 2

   Firebase was evaluated for rapid startup, but Replenysh rejected it to maintain a relational database with Postgres Row Level Security.

3. 3

   Prior to adopting Supabase, Replenysh operated custom OTP and password authentication using Twilio, a Haskell server, and Postgres on Heroku.