BaseBuddy

Product Introduction

1. Definition: BaseBuddy is an open-source, self-hosted content management system (CMS) and editorial interface specifically engineered for Supabase and Postgres databases. It operates as a decoupled, headless CMS layer that sits on top of an existing database schema.
2. Core Value Proposition: BaseBuddy exists to solve the developer-content team collaboration gap. It provides a WordPress-like, intuitive editing experience for non-technical users while allowing developers to retain full control over their existing Supabase or PostgreSQL database schema, eliminating the need for complex migrations or a separate, opinionated CMS database.

Main Features

1. Schema Mapping & Reverse-Engineering: BaseBuddy's core technology reads your existing database tables, columns (including types like text, boolean, jsonb), and foreign key relationships directly from your Supabase project or Postgres connection. It then allows administrators to map these database structures to human-friendly field labels and appropriate input widgets (e.g., WYSIWYG editor for text, toggle for boolean, relation picker for foreign keys) without altering the underlying SQL schema.
2. Advanced Content Editor with Markdown/HTML: The editor provides a rich, distraction-free writing environment comparable to modern tools like Notion or WordPress Gutenberg. It features real-time Markdown parsing, raw HTML editing support, keyboard shortcuts for formatting, and slash (/) commands for quickly inserting elements, enhancing content creation speed and flexibility for writers and editors.
3. Integrated Digital Asset Management (DAM): BaseBuddy integrates directly with Supabase Storage for media management. Users can upload, browse, and insert images and files from configured Storage buckets directly within the editor interface. It also supports S3-compatible storage backends, offering flexibility for media hosting outside of Supabase's ecosystem.
4. Configurable Editor Sidebar & Layout: Administrators can curate the editing experience by selecting which mapped fields appear in the persistent sidebar versus the main content area. This allows for project-specific focus, keeping essential metadata (like publish dates, status, SEO fields) accessible while letting the main content area dominate the screen for long-form writing.
5. Role-Based Access Control (RBAC) & Permissions: The system includes granular permission controls. Administrators can define roles (e.g., Editor, Contributor, Admin) with broad permissions and apply user-specific overrides for fine-grained access. This controls who can view, edit, publish, or manage specific tables and content, which is critical for enterprise and team use cases.
6. SEO & Publishing Workflow Tools: BaseBuddy includes dedicated fields and panels for managing SEO metadata (title, description, keywords) and content validation checks. It supports safe publishing workflows, allowing for content review and preview before changes are committed to the live database, reducing the risk of errors.

Problems Solved

1. Pain Point: The friction between developer-preferred database tools (like direct SQL or Prisma) and non-technical content team needs for a simple, safe GUI. Using a traditional headless CMS often requires duplicating data or forcing a new schema, while admin panels like pgAdmin or Supabase's Table Editor are too complex and risky for editors.
2. Target Audience: Full-Stack Developers & CTOs building applications with Supabase/Postgres who need to delegate content updates. Marketing Managers & Content Teams who require a secure, intuitive interface for managing website copy, blog posts, and product data without developer intervention. Agency Teams managing multiple client projects who need a standardized, secure content editing layer across different Supabase backends.
3. Use Cases: Marketing Website Management: Allowing marketing teams to update landing page content, blog posts, and case studies stored in a Supabase database. Product Catalog Updates: Enabling e-commerce managers to edit product details, descriptions, and pricing in a Postgres database without touching the API or admin panel. Internal Knowledge Base: Providing a clean editor for teams to maintain internal documentation where the source of truth is a company Postgres database.

Unique Advantages

1. Differentiation: Unlike traditional CMS platforms (WordPress, Strapi) that impose their own database schema, BaseBuddy adapts to yours. Unlike generic database admin panels (Adminer, Supabase Studio), it provides a curated, content-focused interface with editorial workflows. Compared to other Supabase CMS tools, its deep native integration and focus on mapping existing schemas is a key differentiator.
2. Key Innovation: The "non-invasive mapping engine" is the key innovation. Instead of generating code or requiring schema migrations, BaseBuddy stores a separate mapping configuration that defines how the existing database is presented and edited. This allows it to work with any pre-existing, production Supabase/Postgres database instantly, offering unparalleled flexibility and eliminating lock-in.

Frequently Asked Questions (FAQ)

1. Does BaseBuddy modify my Supabase database schema? No, BaseBuddy is read-only regarding your schema structure. It connects to your Supabase or Postgres database, reads the existing tables and relationships, and stores a separate configuration map that defines the editorial interface. Your core SQL schema remains entirely untouched.
2. Is BaseBuddy a hosted SaaS or self-hosted solution? BaseBuddy is a self-hosted, open-source application. You download and deploy the software on your own infrastructure (e.g., VPS, Docker, Railway), connecting it to your Supabase project. This gives you full control over data, security, and uptime.
3. Can I use BaseBuddy with a non-Supabase Postgres database? Yes. While optimized for Supabase (including integrated Auth and Storage), BaseBuddy can connect to any standard PostgreSQL database version 12 or above using a direct connection string, making it a versatile open-source Postgres CMS.
4. How does BaseBuddy handle user authentication and security? BaseBuddy leverages Supabase Auth for authentication when connected to a Supabase project. For standalone Postgres connections, it uses secure session-based auth. All database queries are parameterized and permissions are enforced via the application's RBAC layer, ensuring users only interact with data they are explicitly allowed to.
5. What is the license for BaseBuddy? BaseBuddy is open-source software licensed under the AGPL-3.0-or-later license. This means you are free to use, modify, and distribute the software, but if you run a modified version as a service over a network, you must make the source code of that version available to its users.