Kompozy on Supabase: persistence and auth
Every Kompozy workspace, persona, generated post, and media asset lives in Supabase. Row-level security isolates workspaces.
Last verified · 2026-10-23 · by Moe Ameen
Published 2026-04-24 · Updated
Short answer
Kompozy runs on Supabase for sign-in, its Postgres database, and file storage. Every workspace, persona, generated post, and media file lives there. Row-level security policies limit every read and write to the signed-in user, so one account can't see another's content. Generated media goes into a private storage bucket and is shared through signed URLs that last 10 years.
Key takeaways
- Supabase runs Kompozy's auth, database, and file storage.
- Row-level security limits every table to the signed-in user's own data.
- Generated images and videos sit in a private bucket that you reach only through signed URLs.
- Those signed URLs last 10 years, so media on published posts doesn't vanish an hour later.
How does Kompozy use Supabase?
- Auth via Supabase Auth
- Row-level security per workspace
- Generated media in private storage bucket
- 10-year signed URLs
What does this look like in Kompozy?
A real five-slide carousel generated in the Kompozy workspace. Generated files like these slides are what Kompozy keeps in private storage.
Who is this for, and who should skip it?
Best for:
- Buyers who want to know where Kompozy keeps their content before they sign up
- Security reviewers checking how one workspace is kept apart from another
Not ideal for:
- Anyone hoping to plug in their own Supabase project. This page describes Kompozy's own infrastructure, not something you connect
- Teams that require data to stay on their own servers
Frequently asked questions
What does Kompozy use Supabase for?
Authentication, the Postgres database, and storage for generated media.
Can other Kompozy users see my content?
No. Every table has row-level security policies that limit reads and writes to the signed-in user's own data.
Where are my generated images and videos stored?
In a private Supabase storage bucket. Kompozy uploads each file there as soon as generation finishes.
How long do media links last?
Kompozy signs media URLs with a 10-year lifetime. Before that change, raw AI provider links expired within the hour and posts lost their images.
Do I need my own Supabase account?
No. Supabase is what Kompozy runs on, and there is nothing for you to set up.
How do we know this?
On 2026-10-23 we checked each claim on this page against Kompozy's security page, its changelog, and its integrations page, and confirmed the 10-year signed URL setting in Kompozy's media storage code.
Sources
- Kompozy — Security (Supabase, row-level security, signed URLs, Stripe card data) (read 2026-10-23)
- Kompozy — Changelog (2026-04-24: private storage with 10-year signed URLs) (read 2026-10-23)
- Kompozy — Integrations (Blotato, Mailchimp, Stripe, Supabase) (read 2026-10-23)
- AI Content Repurposing — The complete methodology for turning one source into 25-35 pieces of native-format content across every platform — without producing AI slop.
- Autonomous Content Creation — Most "autonomous" AI content is slop.
- AI Brand Voice & Persona — Without a Persona Brief, every AI output averages to the LLM default voice.