Alternatives
Products that do what Tinbase – OSS Supabase-compatible back end in TypeScript does
- 1KB
2020 · kretes.dev
- 2NR
2020 · github.com
- 3CA
2017 · codewich.com
- 4ST
2016 · github.com
- 5AT
2019 · blog.hediet.de
- 6RT
2018 · github.com
- 7IM
Jul 2026 · github.com
- 8RL
Hey folks! There has been a lot of talk recently about the reliability of Supabase and migrating away to other database providers (or even hosting Postgres yourself). I'm a big proponent of writing actual backend code rather than locking yourself into frameworks like Supabase. If you already built all your client-side code around it though, then migrating is not a trivial task. Replacebase is designed to help with that. It's a Typescript library that you can plug into actual backend code that exposes a Supabase-compatible API so that you don't have to make significant changes to your…
Feb 2026 · github.com
- 9IO
Jul 2026 · github.com
- 10TC
2020 · github.com
- 11CA
2018 · github.com
- 12NB
2016 · github.com
- 13BI
2020 · bedrock.io
- 14PA
2021 · planettypescript.com
- 15MO
2019 · github.com
- 16TN
2020 · github.com
- 17NG
2021 · github.com
- 18PA
2022 · pothos-graphql.dev
- 19SD
2023 · github.com
- 20B2
2023 · bytebase.com
- 21D1
2015 · blog.duoco.de
- 22NO
I built a full backend-as-a-service platform — solo, in TypeScript — to fix what I hated about Supabase and Appwrite. The Problem - Supabase: Too rigid. One schema model. No flexibility. - Appwrite: Too loose. No RLS. Security is manual. The Solution: 3 Schema Types | Type | Use Case | Security | |------------|-----------------------------------|----------| | `Document` | Rapid prototyping (Appwrite-style) | Manual | | `Managed` | Secure apps (auto RLS + permissions) | *Secure by default* | | `Unmanaged`| Full SQL power (raw Postgres) | None | ### Killer Features - *APIs better than…
Oct 2025
- 23TL
Oct 2025 · tinqerjs.org
- 24TN
2019 · typescene.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →