Relaticle is an open-source, self-hosted CRM designed for AI agent integration, targeting developer-led teams, AI-forward startups, and SMBs. It provides a privacy-first solution with a modern tech stack, enabling seamless connection of various AI models to CRM operations without vendor lock-in.

How It Works

Relaticle features an agent-native infrastructure centered around a production-grade MCP server equipped with 30 tools. This server facilitates full CRM operations by connecting AI agents (like Claude, GPT, or open-source models) via a REST API offering full CRUD capabilities and schema discovery. Its core advantage lies in its highly customizable data model, supporting 22 field types, and robust multi-team isolation through a 5-layer authorization system, ensuring data privacy and team-scoped workspaces.

Quick Start & Requirements

• Primary install: Clone the repository (git clone https://github.com/Relaticle/relaticle.git), navigate into the directory (cd relaticle), and run composer app-install.
• Prerequisites: PHP 8.4+, PostgreSQL 17+, Composer 2, Node.js 20+. Redis is optional for development queues.
• Links: Website, Documentation, MCP Server, Roadmap, Discussions.

Highlighted Details

• Agent-Native Infrastructure: MCP server with 30 tools, REST API with full CRUD, and schema discovery tailored for AI agents.
• Customizable Data Model: 22 field types, including entity relationships, conditional visibility, and per-field encryption, eliminating the need for database migrations.
• Multi-Team Isolation: 5-layer authorization ensures team-scoped data and workspaces.
• Modern Tech Stack: Built with Laravel 12, Filament 5, PHP 8.4, and includes over 1,100 automated tests.

Maintenance & Community

Community engagement is encouraged through GitHub for reporting issues, requesting features, and asking questions. Discord is available for support. The project's GitHub star history is noted as a support metric.

Licensing & Compatibility

Relaticle is licensed under the AGPL-3.0 license. This strong copyleft license requires derivative works to also be open-sourced under the same license, which may impose restrictions on integration with closed-source commercial products.

Limitations & Caveats

The primary adoption consideration is the AGPL-3.0 license, which mandates that any modifications or derivative works distributed must also be made available under the AGPL-3.0. No other explicit limitations or alpha status warnings are present in the provided README.