CSBuddyPro is an open-source, self-hostable Customer Success Operating System designed for SaaS teams. It is evolving into a modular platform inspired by Odoo-style extensibility: core product + installable modules + optional plugins.
Placeholder: add product screenshots in
docs/assets/.
- Account and lifecycle management
- Health scoring and automation playbooks
- Onboarding, QBR, and renewals workflows
- Plugin-ready integrations (Slack, HubSpot, Zapier, Webhooks)
- Docker-first deployment for local and production environments
/frontend -> frontend boundary (React app)
/backend -> backend runtime boundary (Express API)
/docker -> shared runtime/container assets
/docs -> setup, architecture, API, deployment docs
/modules -> domain modules (installable)
/plugins -> integration plugins (toggleable)
The platform uses registry-based extension manifests:
modules/registry.jsonplugins/registry.json- dynamic loader:
src/platform/extensionRegistry.ts
git clone <your-fork-url>
cd csbuddypro
cp .env.example .env
docker compose up --buildApp: http://localhost:8080
API: http://localhost:10000
- Uses one command startup:
docker compose up - Includes isolated services (
frontend,backend,db) - Persistent volumes:
postgres_data,backend_uploads - Restart policy:
unless-stopped
See docs/docker-setup.md.
cp .env.example .env
npm ci
npm run devSee docs/local-development.md.
Structured dropdown values are managed centrally from /settings/master-data and exposed through /api/master-data/*. See docs/master-data-management.md.
The Admin Panel is the central configuration hub for users, lifecycle/health/workflow settings, dropdowns, Knowledge Base structure, integrations, portal configuration, and AI settings. See docs/admin-portal-api-transformation.md.
Lifecycle, health, onboarding, and renewal statuses are centralized through /api/status-framework with defaults and Field Config overrides. See docs/status-framework.md.
Modules live in /modules/* and include metadata, versioning, permissions, migrations, backend/frontend contract placeholders.
See docs/module-development.md. Phase 2/3 scaffolds are also documented in docs/api-management.md and docs/knowledge-base-modernization.md.
Plugins live in /plugins/* and can be enabled/disabled independently via registry + environment flags.
See docs/plugin-development.md.
- Docker / VPS / Coolify:
docs/deployment.md - Render:
render.yamlanddocs/deploy-render.md - Railway:
railway.jsonanddocs/deploy-railway.md
Read CONTRIBUTING.md and docs/contribution-guide.md before opening a PR.
See ROADMAP.md for phased delivery (core stabilization, marketplace, automation/AI, enterprise scale).
Licensed under GNU Affero General Public License v3.0 (AGPL-3.0-or-later).
If you run a modified network-hosted version, you must provide source code of modifications to users as required by AGPL.