Documentation

Practical product docs for setting up, mapping, editing, and operating BaseBuddy.

Docs/BaseBuddy vs Supamode

BaseBuddy vs Supamode

Compare BaseBuddy and Supamode for Supabase CMS projects, existing schemas, self-hosting, permissions, and editor workflows.

Short version

Supamode is a Supabase-focused CMS/admin interface that adapts to Supabase database schemas and provides dashboards, permissions, and a self-hosted interface.

BaseBuddy is also Supabase-focused, but it is narrower and open source. It is built around saved mappings, editor workflows, dirty-field saves, media/files, SEO, and content-team permissions.

Similar goal, different product shape

Both products are trying to make Supabase content easier for non-technical users. The difference is how much surface area you want.

QuestionBaseBuddySupamode
Primary jobWordPress-like editor for mapped Supabase/Postgres contentSupabase CMS/admin interface with dashboards and smart forms
License/modelOpen-source AGPL app repoCommercial lifetime-license product from Makerkit
Runtime modelSaved mapping is the editor runtime truthAdapts to database schema and uses its own app layer
Best fitExisting content schemas that need editorial workflowsTeams wanting a broader Supabase admin/CMS interface
Editorial focusPosts, rich text, media/files, SEO, taxonomy, publishing, permissionsData navigation, generated forms, dashboards, permissions, audit logs

Choose BaseBuddy when

  • You want an open-source Supabase CMS you can inspect, self-host, and contribute to.
  • You care most about content editing workflows, not general dashboards.
  • You want to map an existing posts/articles/docs model into a focused editor.
  • You want clear safety rules: opening content does not mutate it, normal save writes dirty fields only, and publish actions are explicit.

Choose Supamode when

  • You want a broader Supabase admin interface with dashboards and generated forms.
  • A paid lifetime-license product fits your budget and support expectations.
  • You want a product closely tied to the Makerkit ecosystem or Supamode's feature set.

The main difference

Supamode is broader. BaseBuddy is more focused on open-source content editing for existing Supabase/Postgres schemas.

For the BaseBuddy side, Supabase CMS, Projects and mappings, and Publishing workflows show the narrower editorial model.

You can read more about Supamode in the Supamode docs and the Makerkit Supabase CMS page.