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

Update apps/www/_blog/2023-02-16-case-study-happyteams.mdx

Browse Source 
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
Coppleandgithub-actions[bot] authored and GitHub committed 2023-02-16 20:22:05 +01:00
1 parent 9e65f48acf
commit b049d52a56
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/www/_blog/2023-02-16-case-study-happyteams.mdx
+1 -1
View File
@@ -35,7 +35,7 @@ There were four main factors that led HappyTeams to switch from Heroku Postgres
4. **Lower costs**. Moving to Supabase reduced HappyTeams's costs: The base plan comes with everything they need to scale the product.
<Quote img="michael-dever-happyteams.jpg" caption="Michael Dever - CTO of HappyTeams">
Great documentation, great product, great pricing. It sells itself, really.
Great documentation, great product, great pricing. It sells itself, really.
</Quote>
## Supabase provides a fast and reliable production database