BaseBuddy

Most CMS platforms require your content to fit their schema; BaseBuddy inverts that relationship by mapping onto whatever Postgres or Supabase tables you already have. You run one BaseBuddy instance, complete onboarding (via the UI or CLI), map existing tables to editable fields, and start editing — the saved mapping becomes the runtime source of truth, and your content database stays exactly as it was, under your own control.

This matters for teams with content already living in application tables (posts, pages, docs, guides) that don’t want to migrate into a CMS-specific schema just to get a decent editing UI. BaseBuddy provides a TipTap-based, WordPress-like editing experience on top of those existing tables instead.

AGPL-3.0 licensed and self-hosted, BaseBuddy is a young, small project (single-digit stars at time of review) but addresses a specific, well-defined gap between “raw database editing” and “migrate everything into a dedicated CMS.”

What You Get

• A self-hosted editor that maps directly onto existing Postgres or Supabase tables
• A WordPress-like, TipTap-based editing experience without reshaping your database schema
• Table mapping saved as the runtime source of truth, so your content database stays exactly as it is
• UI-based onboarding or CLI setup for connecting BaseBuddy to your existing database

Common Use Cases

• Giving non-technical team members a clean editing UI for content that already lives in application database tables
• Adding CMS-style editing to an existing Postgres/Supabase-backed app without migrating to a dedicated CMS schema
• Editing posts, pages, docs, or guides stored across custom tables instead of a database admin tool like a raw table editor
• Self-hosting content editing infrastructure to keep full control over an existing content database

Under The Hood

Architecture BaseBuddy’s core mechanic is schema mapping rather than schema ownership: instead of defining its own content model and migrating your data into it, it reads your existing Postgres/Supabase table structure and lets you map columns to editable fields, storing that mapping as configuration rather than transforming the underlying data. This means the content database remains fully owned and structured by the application it was built for, with BaseBuddy acting as an editing layer on top.

Tech Stack Next.js and TypeScript, TipTap for the rich-text/WordPress-like editing experience, and native support for both Postgres and Supabase (including Supabase Storage) as the underlying data layer.

Code Quality The project maintains a SECURITY.md, AGENTS.md, and CHANGELOG.md alongside standard docs, indicating structured process discipline for a project of its size; as a young, low-adoption project (single-digit stars), broader community validation is still limited.

What Makes It Unique Most CMS tools require adopting their schema; BaseBuddy’s mapping-first approach specifically targets teams with content already living in arbitrary Postgres/Supabase tables who want an editor without a data migration, a narrower but genuinely useful niche compared to schema-first CMS platforms.

Self-Hosting

Licensing Model AGPL-3.0 licensed — fully open source with no license key.

Self-Hosting Restrictions None found; self-hosting against your own Postgres/Supabase instance is the primary intended use.

License Key Required No.