why? We were hacking on a blog engine for Preswald, where each post embeds live, interactive product demos. We needed tight control over layout, logic, and storage, so tools like Substack or Webflow were too rigid. We started hardcoding Markdown and media into the codebase. That… didn’t scale.
Supabase Storage gave us a clean separation of content and code – but there was no easy way to browse, edit, or publish that content unless you lived in the Supabase dashboard or were writing API scripts.
So we built a lightweight CMS layer on top of Supabase: drag-and-drop uploads, folder navigation, public/private bucket support, and a "Publish" button that triggers a re-deploy or static regen in your app.
Features:
- File/folder UI for Supabase Storage (drag & drop, real-time updates via subscriptions) - Built-in Supabase auth for simple admin login - Supports public/private buckets out of the box - Custom "Publish" actions (SSR revalidation, webhook triggers, etc.) - Super simple to fork and customize – it's just a Next.js app with Supabase client hooks
You can spin up your own instance with:
npx create-supawald my-app
Or check out the code here: github.com/structuredlabs/supawald
If you're using Supabase for content or assets (blog posts, PDFs, docs, media, app configs, etc.) and want a dead-simple way to manage it – Supawald might save you a weekend.
Would love feedback and PRs!
No comments yet.
