Weave Code
Laravel Crm Laravel Package
krayin/laravel-crm
Krayin is an open-source Laravel CRM for small and medium businesses, offering lead and contact management, sales pipelines, email and activity tracking, workflow automation, dashboards, and a customizable admin panel built on Laravel and Vue.js.
Krayin CRM is Free & Open Source CRM Built with Laravel for Customer, Lead, and Sales Management.
Frequently asked questions about Laravel Crm
- How do I install krayin/laravel-crm with Composer?
- Install Krayin by creating a new project from the krayin/laravel-crm package with Composer, then running the web installer or the documented artisan setup commands to configure your database and admin user. You will need a Laravel-ready environment with PHP, a supported database driver, and a web server pointing at the public directory. Run the migrations and seeders as part of setup so the CRM, roles, and default configuration are in place before you log in.
- Which Laravel and PHP versions does Krayin CRM support?
- Krayin is built on Laravel and Vue.js and tracks the framework versions declared in its composer.json for each release. Before upgrading, check the package constraints against your application's Laravel and PHP versions rather than assuming compatibility. If you run MariaDB, custom queue or cache drivers, or non-Latin locales, verify those against the release notes as well, since earlier versions added specific requirements around MariaDB validation, PDF export dependencies, and CJK font rendering.
- Is Krayin CRM free and open source, and can I self-host it?
- Yes. Krayin is a free, open-source Laravel CRM aimed at small and mid-sized businesses, and it is designed to be self-hosted so you keep full control of your customer data. Because it is a standard Laravel application, you can deploy it on your own servers, container platforms, or managed Laravel hosting. There are no per-seat licensing fees, but you are responsible for hosting, backups, security patching, and upgrades.
- How do I upgrade Krayin from v2.2.6 to v2.2.7?
- Treat v2.2.7 as a cumulative patch upgrade over v2.2.6: update your Composer constraint, pull the new release, run the new migrations, and review any published configuration changes. The release includes a security improvement, so expedite adoption instead of bundling it into a routine maintenance window. Notifications are the most integration-sensitive addition and may require queue and channel configuration, so plan regression testing around notifications, mega search, quotes in Quick Add, dashboard data filters, and the lead/product and person form fixes.
- Do Krayin notifications require queue workers and channel credentials?
- Notifications are the most infrastructure-sensitive part of v2.2.7 because they introduce event and delivery-channel responsibilities beyond the core CRM. Depending on which channels you enable, expect new migrations, queue worker configuration, and transport credentials such as mail or broadcast settings. Check whether notifications are opt-in or default-on for your users and review retention and user-preference handling before enabling them in production.
- How does mega search work and does it need an external search engine?
- Mega search adds a global search surface and per-section record counts across the CRM. Confirm in your environment whether it relies on database queries, indexing jobs, or additional schema before assuming no external search engine is needed. Because search results cross record types, test it with restricted user roles to verify that permissions and tenant boundaries are enforced correctly in every result set. Also benchmark per-section record counts on realistic data volumes, since they can add queries per search.
- Does Krayin CRM provide a REST API for integrations?
- Krayin ships with a REST API and a modular architecture intended for integrations with external systems. You authenticate against the API using the credentials and token mechanism documented for your release, then work with endpoints for leads, contacts, organizations, and related records. Because permissions are enforced through role-based access control, create a dedicated API user with the minimum scopes your integration needs rather than reusing an admin account.
- How do I create a custom module or extend Krayin's admin panel?
- Krayin is built on Laravel and Vue.js with a modular package structure, so custom functionality is typically added as a package registered with the application rather than by editing core files. Follow the existing module conventions for routes, migrations, models, repositories, and Vue components so your customizations survive upgrades. Keep custom code in version control and re-run your test suite after each Krayin release, since new features such as notifications, mega search, and dashboard filters add architectural touchpoints your module may interact with.
- What security issue does the Krayin v2.2.7 security improvement address?
- The v2.2.7 release includes a security improvement, but the release notes excerpt does not identify the specific issue or reference a CVE. Treat it as an urgent patch pending confirmation of the affected surface, and check the repository changelog and issue tracker for details. Until you know the scope, prioritize the upgrade and audit any exposed admin routes, API tokens, and file or export endpoints in the meantime.
- What are the alternatives to Krayin for a Laravel-based CRM?
- Krayin's main differentiator is that it is a native Laravel and Vue.js CRM you can self-host and extend with custom modules, unlike SaaS CRMs with per-seat pricing. If you need a broader plugin ecosystem or a different data model, evaluate general open-source CRMs and compare them on extensibility with your Laravel codebase, API quality, and upgrade cadence. For teams already standardized on Laravel, staying with Krayin usually means less integration work because authentication, queues, and deployment follow the same patterns as the rest of your stack.
Weaver
How can I help you explore Laravel packages today?