ERPNext is a comprehensive open-source ERP (Enterprise Resource Planning) system built on the Frappe Framework. It provides a full suite of business management modules including Accounting, CRM, Buying, Selling, Stock/Inventory, Manufacturing, Projects, Assets, Quality Management, Support, and more. The system uses a metadata-driven architecture where DocTypes (document types) define data models, business logic, and UI behavior. The codebase follows a modular structure with each business domain in its own directory (accounts, buying, selling, stock, manufacturing, projects, etc.). It includes a modern React/TypeScript banking module built with Vite for bank reconciliation and statement importing. The system supports multi-company, multi-currency, multi-language deployments with extensive regional/localization support for tax compliance across many countries. It has a robust patch/migration system for database schema evolution and a comprehensive test suite.
Monica is an open source personal relationship management system (PRM) built with Laravel and Vue.js that functions as a 'CRM for your friends and family'. The system features comprehensive contact management, relationship tracking, activity logging (notes, calls, tasks), life event tracking, document management, and journaling capabilities. It implements a modular domain-driven architecture with clear separation between backend services, view helpers for data preparation, and frontend components. The application includes CardDAV synchronization for external contact sync, multi-vault/user support, notification systems (email/Telegram), reporting features, and extensive internationalization (27+ languages). Built with modern Laravel practices including service contracts, queueable jobs, event-driven architecture, and comprehensive testing.
Mautic is an open-source marketing automation platform built on Symfony (PHP). It provides a comprehensive suite for managing contacts (leads), creating and executing marketing campaigns, sending emails, building forms and landing pages, tracking user interactions, and integrating with third-party CRMs and services. The architecture is a modular monolith with bundles and plugins, a REST API, and a CLI console. Key data flows include contact tracking via tracking pixels and form submissions, campaign execution with scheduled events, email sending with bounce/feedback processing, and integration sync with external systems. External dependencies include MySQL/MariaDB, optional Redis/Memcached caching, a mailer transport, and various third-party APIs for IP geolocation, data enrichment, and social media. The codebase is actively maintained with extensive test coverage, modern PHP practices, and a plugin ecosystem.
Twenty is a production-grade, open-source CRM delivered as a large Nx monorepo. The system is a full-stack TypeScript application: a NestJS backend (twenty-server) exposing GraphQL/REST APIs, a React frontend (twenty-front) with Jotai-based state management, a shared UI component library (twenty-ui), and shared TypeScript packages (twenty-shared). It provides multi-tenant workspaces, object-record CRUD with custom data models, role-based permissions, AI chat/agent capabilities (model tiers, tool calls, streaming), analytics via ClickHouse, and a CLI scaffolding tool (create-twenty-app) for bootstrapping custom apps. The architecture is modular with NestJS ConfigurableModuleBuilder patterns, event-driven design using Zod-validated schemas, and component-scoped state via atom families and component instance contexts.
ZaloCRM is a production-grade, multi-tenant customer relationship management system deeply integrated with the Vietnamese Zalo messaging platform. It serves real-estate sales teams by unifying contact management, real-time chat, lead scoring/automation, appointment scheduling, media library, RBAC, privacy controls, and third-party integrations (Facebook Lead Ads, Telegram bridge, Google Sheets). The system is deployed as a Node.js/Fastify monolith with PostgreSQL (Prisma ORM), Redis (BullMQ queues, rate limiting), MinIO/S3-compatible storage, and Socket.IO for real-time events. It relies on the unofficial Zalo SDK (zca-js) for messaging operations and supports multiple AI providers (Anthropic, Gemini, OpenAI) for reply drafting, sentiment analysis, and appointment parsing. The architecture follows an open-core model: the Community edition ships with extension stubs (`_ee-stubs`) that are replaced in the Enterprise edition. Key entry points include auth routes (JWT with rotating refresh tokens), Zalo account management (QR login, reconnect), friend sync (cron-driven diff-then-emit), and a rich chat operations module (reactions, edits, forwards). Background jobs handle lead pool assignment, care session monitoring, scoring decay, and engagement pattern classification. The system maintains strong data invariants through Prisma extensions (tenant context, RLS preparation, safe-contact-write) and a custom privacy layer that redacts private-nick messages based on viewer role. Data flows center on the Zalo account pool: inbound messages are ingested via socket listeners or friend sync, routed to conversations via a global-aware resolver, and triggers automation hooks (care sessions, auto-tags, sequence advancement). Analytics are derived from daily engagement materialization and scoring engine (4 dimensions with weights). External dependencies are managed via Redis-backed rate limiters, while storage operations are abstracted behind a `StorageDriver` interface with local/R2 implementations. The codebase is actively maintained with daily commits, extensive Prisma migrations, and a comprehensive test suite covering privacy invariants, merge policies, and regression scenarios.
ruoyi-vue-pro (芋道) is a large-scale, multi-module enterprise rapid development platform built on Spring Boot 2.7, MyBatis-Plus, and Vue 3. It provides a comprehensive backend infrastructure for building business applications such as ERP, CRM, HRM, MES, WMS, OA, BPM (Flowable), IoT, AI, IM, Pay, Mall, and more. The codebase is structured around a reusable framework layer (`yudao-framework`) with many Spring Boot starters for security, data permission, multi-tenancy, WebSocket, Excel, monitoring, and protection (rate limiting, idempotency). Business modules follow a consistent layered pattern (DO → Mapper → Service → Controller → VO) with MapStruct converters. The system supports MySQL, PostgreSQL, Oracle, SQL Server, and Dameng databases, and integrates with Redis, RabbitMQ, Kafka, RocketMQ for messaging. It includes a code generator, a workflow designer, and AI chat/image/mind-map capabilities. The architecture is modular and well-organized, though the sheer number of modules (20+) introduces some duplication and complexity. Overall, it is a mature, actively maintained project with strong adherence to common enterprise patterns.
Akaunting is a self-hosted accounting and invoicing platform for small businesses and freelancers. It manages invoices, bills, banking transactions, transfers, reconciliations, multi-currency, multi-tax, recurring documents, and financial reports. It includes a customer portal for invoice viewing and payment, and supports multi-company, multi-user with role-based permissions. The system is highly internationalized with 40+ language locales. The architecture is built on a custom PHP framework (Illuminate) that extends Laravel conventions. It uses an event-driven architecture with domain events, listeners, and a job queue for async processing. The frontend combines Blade templates, Vue.js components, and Livewire for interactivity. Multi-tenancy is achieved through company scoping via a global query scope. The system is extensible via a module system with an app store, and includes a CLI for maintenance tasks. Key entry points include the installation wizard (controllers under Install/), authentication flows, and core CRUD controllers for sales, purchases, banking, and settings. Data flows typically involve controllers dispatching jobs that emit events, which listeners handle to update related entities, send notifications, or trigger side effects. Reports use a filter/group/rows event system for extensibility. Import/export is handled via Excel with multi-sheet support. External dependencies include PHP 8.1+, Node 18-20, and a database (MariaDB, MySQL, PostgreSQL, SQLite). It uses Laravel Mix for asset compilation, integrates with payment gateways, email services, and error trackers (Sentry, Bugsnag), and relies on a module marketplace at api.akaunting.com.
Macro is a large open-source monorepo (AGPLv3) for an all-in-one collaborative productivity platform that unifies email, messaging, documents, tasks, CRM, AI agents, and more. The backend consists of 42+ Rust microservices following a consistent hexagonal architecture (domain/inbound/outbound), with PostgreSQL, OpenSearch, Redis, S3, Kafka/SQS/EventBridge for data storage and event-driven processing. The frontend is a SolidJS single-page application with a heavily customized Lexical editor, block-based content system, real-time collaboration via CRDT (Loro), and Tauri-based desktop/iOS apps. AI is a first-class feature with agent harnesses, MCP integration, and an AI editing worker. Infrastructure is managed via Pulumi and Docker Compose for local development. The codebase demonstrates high engineering craftsmanship with consistent patterns, extensive testing, and comprehensive observability, though the sheer scale and volume of generated code introduce some maintenance overhead.
IDURAR is a free, open-source ERP and CRM application built on the MERN stack (MongoDB, Express.js, React.js, Node.js) with Ant Design and Redux. It provides modules for invoice management, payment processing, quote generation, customer relationship management, inventory tracking, and financial reporting. The system features multi-language support (44 languages), PDF generation for business documents, role-based access control, and a responsive user interface. The architecture separates concerns with a RESTful API backend and a modular frontend utilizing React, Redux for state management, and Ant Design for UI components.
This repository is a Claude Code skill bundle for Generative Engine Optimization (GEO) and SEO auditing, distributed as an installable plugin. The core deliverable is a composite GEO Score (0-100) computed from six weighted categories: AI citability, brand authority, content E-E-A-T, technical health, structured data, and platform optimization. Users invoke slash commands such as /geo audit, /geo quick, /geo citability, /geo llmstxt, and /geo report, which orchestrate a set of skill definitions, agent prompts, and Python helper scripts to crawl external websites, analyze AI crawler accessibility, extract JSON-LD, generate llms.txt files, score content passages, and produce client-ready reports and proposals. It also includes a small Flask + HTMX CRM webapp for managing prospects and a white-label configuration system for agencies. The architecture is primarily a composition of markdown-based skills and agents with Python scripts as deterministic helpers. The main entry points are geo/SKILL.md (orchestrator), the scripts under scripts/, and the webapp at scripts/webapp/app.py. The system behaves as a productized agency service: it runs audits against arbitrary client domains, produces quantitative scores, generates branded PDF reports, pricing proposals, and monthly delta comparisons. Some research-oriented artifacts exist - cited market studies, scoring methodology documentation, and heuristic rubrics - but the dominant character is an application toolkit for practitioners rather than a data pipeline. Strengths include a clear JSON-to-stdout contract between scripts and skills, deterministic scoring modules such as citability_scorer.py and llmstxt_generator.py, reusable JSON-LD schema templates, and a sensible separation between deterministic checks and LLM-judged scoring. Weaknesses include documentation drift (inconsistent skill counts and command references), duplicated scoring rubrics in agent vs skill versions, a legacy ReportLab PDF pipeline documented alongside the newer pandoc/Chrome approach, and only narrow test coverage focused on fetch_page.py.
Totum is a self-hosted, low-code/no-code application framework built on PHP 8.3 and PostgreSQL. It functions as a dynamic database and spreadsheet hybrid, allowing users to define data structures (tables, fields) via JSON configuration and implement business logic using a proprietary DSL ('Totum-code'). The system features a modular architecture with a CLI management tool (`bin/totum`), a web-based UI (`http/index.php`), and extensive role-based access control (RBAC). It supports multi-tenancy via schema mapping, external service integration (PDF, Excel, AI), and automated installation via Ansible playbooks for Ubuntu environments. The core logic relies heavily on traits for shared functionality and abstract base classes for table and field handling, creating a flexible but complex codebase. The application is designed for rapid business application construction (CRM, ERP, custom tools) without requiring traditional coding. It stores schema definitions and field configurations in PostgreSQL JSONB columns, enabling runtime structure modification. The calculation engine (`Calculate.php`) parses and executes custom code strings for data validation, formatting, and cross-table logic. While the architecture is robust for its intended purpose, it exhibits signs of technical debt including monolithic frontend JavaScript (`main.js`), hardcoded paths in installation scripts, and reliance on legacy libraries (Chart.js v2, jQuery). The codebase demonstrates significant craftsmanship in its dynamic table engine and calculation DSL, but maintenance requires careful handling of the custom parsing logic and schema migrations.
This is the umbrella monorepo for Evo CRM Community, an open-source AI-powered customer support platform. The repository itself does not contain application source code; it orchestrates seven independent microservices (auth, CRM, frontend, AI processor, core service, bot runtime, and event flow) via Git submodules and Docker Compose/Swarm configurations. The primary function of this repo is to provide a single entry point for cloning, building, seeding, and deploying the full stack. It includes a nginx API gateway for path-based routing to backend services, CI/CD workflows for building and publishing Docker images, migration version collision guards, and extensive release documentation. The actual business logic, AI agent execution, conversation management, and user interface reside in the submodules.
Samarium is a modular, all-in-one business management system (ERP/CMS) built with Laravel 11 and Livewire 3. It provides a comprehensive admin dashboard for small to medium businesses, covering sales invoicing, purchase orders, expense tracking, inventory management, accounting (double-entry ledger, trial balance, income statement), customer/vendor relationship management, and a full content management system (webpages, posts, galleries, navigation menus, themes). It also includes e-commerce capabilities (product catalog, shopping cart, online orders), appointment booking, team management, calendar with Nepali date support, and additional modules like vacancies, testimonials, newsletters, and document/URL link management. The system is configurable via a module toggle in config/app.php and supports both a dashboard interface and a public-facing website. The architecture follows a standard Laravel MVC pattern with Livewire components handling all interactive UI. Each business domain has its own set of Livewire components (e.g., SaleInvoiceEditor, ProductDisplay) that use a shared ModesTrait for state management. A service layer provides pagination and CRUD logic, though many service methods are incomplete. The frontend uses Bootstrap 4, Font Awesome, and Chart.js for reporting. The system is Dockerized for easy deployment and includes seeders for demo data. While the codebase is functional and covers a wide feature set, it exhibits several quality issues: mixed namespaces (some models under App\, others under App\Models\), hardcoded values (VAT 13%, Nepali month arrays), incomplete features (many TODO comments, empty service methods), and code duplication (multiple similar Livewire components for editing fields). The Nepali calendar support is a distinctive feature but requires manual maintenance of hardcoded date ranges. Overall, Samarium is a solid, feature-rich ERP for its target audience but would benefit from refactoring and stricter coding standards.