-
-
Notifications
You must be signed in to change notification settings - Fork 584
Description
What problem did you meet?
The growing ecosystem of Backend-as-a-Service (BaaS) platforms, such as:
- Supabase
- Convex
- Pocketbase
- Appwrite
- Nhost
...and even solutions usually classified as Headless CMS or Data platforms such as:
- Directus
- Strapi
...typically includes their own authentication solutions. This makes it less obvious (or sometimes challenging) to integrate an external identity provider like Logto alongside these platforms.
While Supabase is partially covered via a blog tutorial, there is no official support, guidance, or dedicated UI options for any of these other platforms. This limits the ability to seamlessly adopt Logto in projects that rely on BaaS stacks, which are increasingly popular in modern development workflows.
Describe what you'd like Logto to have
It would be great to see official support, documentation, and potential SDKs or UI options for integrating Logto with these platforms: Supabase, Convex, Pocketbase, Appwrite, Nhost, Directus, Strapi, etc.
This could involve pre-built integrations, authentication bridges, or dedicated guides to facilitate adopting Logto as an identity provider in BaaS-driven applications.
Priority suggestion
As a starting point, the following platforms would be ideal to prioritise:
- Supabase: Already partially explored through your blog and widely used for Postgres-backed applications.
- Convex: Rapidly growing, with focus on real-time and reactive applications. The only true Infrastructure as Code platform.
- Pocketbase: Lightweight, embedded, and increasingly popular for simpler BaaS use cases.