dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 17:35:10 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update happyteams.mdx

Browse Source 
Added CTA.
This commit is contained in:
Ramiro Nuñez Dosio authored and GitHub committed 2023-08-15 13:03:52 +01:00
1 parent 3cdad1e07b
commit b0a77ccfcf
1 file changed
+6 -4
Download Patch File Download Diff File Expand all files Collapse all files
apps/www/_customers/happyteams.mdx
+6 -4
View File
@@ -2,7 +2,7 @@
name: HappyTeams
title: HappyTeams unlocks better performance and reduces cost with Supabase.
# Use meta_title to add a custom meta title. Otherwise it defaults to '{name} | Supabase Customer Stories':
# meta_title:
# meta_title: HappyTeams unlocks better performance and reduces cost with Supabase.
description: How a bootstrapped startup migrated from Heroku to Supabase in 30 minutes and never looked back.
# Use meta_description to add a custom meta description. Otherwise it defaults to {description}:
meta_description: How a bootstrapped startup migrated from Heroku to Supabase in 30 minutes and never looked back.
@@ -32,11 +32,11 @@ about: HappyTeams is a purpose-built solution that empowers management to unlock
> Finding a painless and hands-free database experience to support growth
[HappyTeams](https://happyteams.io/) is a growing startup with an ambitious vision. The company is bootstrapped, so technical resources are scarce. Devs need to do more with less. This means staying laser-focused on delivering features, rather than database timeouts or performance issues.
HappyTeams is a growing startup with an ambitious vision. The company is bootstrapped, so technical resources are scarce. Devs need to do more with less. This means staying laser-focused on delivering features, rather than database timeouts or performance issues.
The company launched its app on Heroku Postgres. But one year in, they were experiencing scaling issues. They needed to handle thousands of users while also shipping new features and building out integrations. Issues with database slowness and concurrent connections were holding them back.
Michael Dever, the founder and CTO of HappyTeams, realized it was time for a change. A large overhaul of the app in early 2022 presented the opportunity to do so: "When you're in that first sprint of building a product, you're kind of locked with that first database decision you make. When we did a rebuild, it was time to look at something like Supabase."
Michael Dever, founder and CTO of HappyTeams, realized it was time for a change. A large overhaul of the app in early 2022 presented the opportunity to do so: "When you're in that first sprint of building a product, you're kind of locked with that first database decision you make. When we did a rebuild, it was time to look at something like Supabase."
![HappyTeams Home Page](/images/blog/2023-02-16-case-study-happyteams/happyteams-home-page.png)
@@ -58,7 +58,7 @@ There were four main factors that led HappyTeams to switch from Heroku Postgres
## Supabase provides a fast and reliable production database
After a 30 minute migration, HappyTeams can iterate quickly, add new features, and improve their product based on customer feedback
After a 30-minute migration, HappyTeams can iterate quickly, add new features, and improve their product based on customer feedback
Once they made the decision, migrating from Heroku to Supabase was simple. HappyTeams completed their database migration in less than an hour using pg_dump and pg_restore.
@@ -74,3 +74,5 @@ Thanks to Supabase's ease of use and reliability, HappyTeams can iterate quickly
When we needed to add a comments feature to our app, we could get it done in just two days.
Supabase is really like a dream come true for a developer.
</Quote>
Supabase is one of the best free alternatives to Heroku Postgres. Migrate your Heroku Postgres database to Supabase with this [guide](https://supabase.com/docs/guides/resources/migrating-to-supabase/heroku).