Summary erxes is a source-available Experience Operating System (XOS) designed to unify marketing, sales, operations, and support functions, aiming to replace multiple existing SaaS tools like HubSpot and Zendesk. It targets SaaS providers, digital marketing agencies, and developers seeking a customizable, self-hosted platform to manage core business operations seamlessly and maintain data privacy.

How It Works The platform employs a modern microservices architecture within an Nx monorepo. The backend utilizes GraphQL Federation and tRPC with Node.js and TypeScript, leveraging MongoDB and Redis. The frontend is built with Module Federation, featuring React, Rspack, and TailwindCSS. This federated approach allows for extensive customization and extensibility through a robust plugin system, enabling developers to build unique business experiences by composing core modules with marketplace or custom plugins.

Quick Start & Requirements

• Prerequisites: Node.js 18+, pnpm ≥ 8, MongoDB 27017, Redis 6379.
• Installation: Clone the repository, install dependencies with pnpm install, configure environment variables via .env.example, and start core services (pnpm dev:core-api) and UI plugins (pnpm dev:uis).
• Resources: Official Documentation, Local Setup Guide, CLAUDE.md, Roadmap, Changelog.

Highlighted Details

• "100% free & sustainable" source-available model.
• "100% customizable" through a plugin-based architecture.
• "100% privacy" due to its self-hosted nature and lack of third-party monitoring.
• "100% in control" by integrating all business channels.
• Built on Nx monorepo, GraphQL Federation, and Module Federation for modularity.
• Extensive plugin marketplace and straightforward custom plugin generation.

Maintenance & Community The project is active with community support channels including Discord, LinkedIn, Facebook, Instagram, and Twitter. A contributing guide is available for developers wishing to participate. Roadmap and changelog are maintained for transparency.

Licensing & Compatibility Described as "source available software." Specific license terms and compatibility for commercial use or closed-source linking should be verified by consulting the project's LICENSE file.

Limitations & Caveats No specific limitations, alpha status, or known bugs are detailed in the provided README. Users should verify system requirements and potential integration complexities for their specific use cases.