If you run an agency and want a CRM you actually own - self-hosted, on your own server, with the data in a database you control - the shortlist almost always narrows to Perfex CRM vs RISE CRM. Both are PHP applications built on CodeIgniter, both cover the agency basics, and both get compared endlessly in forums, usually by someone with a stake in one side winning.
Full disclosure: we are Themesic Interactive, and we build and sell extension modules for both platforms, including the two REST API products used as evidence below. We get paid whichever CRM you choose, which is exactly why we can skip the winner-takes-all framing. There is no winner here. There is a better fit for how your agency works, and the goal of this post is to help you figure out which one that is.
Perfex CRM vs RISE CRM: two different philosophies
Perfex CRM is a client-work CRM. Its center of gravity is the commercial relationship: leads, proposals, estimates, invoices, subscriptions, contracts, support tickets. It also has the larger third-party module ecosystem of the two, so when Perfex does not do something out of the box, there is usually a module that adds it. That ecosystem matters more than it sounds, because Perfex does not ship a full REST API of its own - connectivity is one of the gaps modules fill.
RISE CRM leans team-and-project. It still handles clients, invoices and estimates, but it also covers internal operations: attendance, leave applications, teams, announcements, personal to-do lists. You can read this philosophy straight off the API surfaces of our two products: our RISE plugin exposes Attendance, Leave Applications, Teams, Announcements and ToDo endpoints because RISE itself ships those features, while our Perfex module's endpoint list has no equivalents. If you want one tool that faces clients and doubles as a lightweight team hub, that is RISE's pitch.
A workable mental model: Perfex keeps asking "what is happening with this client?" while RISE keeps asking "what is this team working on, and for whom?"
Where they overlap
The overlap is what puts them on the same shortlist at all. Both are self-hosted CodeIgniter applications running on modern PHP, and both cover clients, projects, tasks, invoices, estimates, tickets and a knowledge base. For an agency leaving spreadsheets or escaping per-seat SaaS pricing, either is a defensible choice on fundamentals. The real separation happens at the edges: module ecosystem, internal operations, and how each platform connects to the rest of your stack. That last part is where we spend our days, so let us get concrete.
The automation story on Perfex
Since Perfex has no full native REST API, automation runs through a module. Ours is the REST API module for Perfex CRM, currently at version 3.1.0, with 2,941 sales on CodeCanyon and rated 4.91/5 from 44 verified CodeCanyon reviews. What it gives you today:
- A documented surface of 74 paths and 144 operations, described by an OpenAPI spec served at GET /api/openapi, importable into Postman or Insomnia.
- Webhooks covering 124 events across 22 event groups, HMAC-signed and delivered asynchronously with retries, so external systems hear about CRM changes without polling.
- A native MCP server at POST /api/mcp (JSON-RPC 2.0) exposing 148 tools to AI agents such as Claude, ChatGPT, Cursor and the n8n AI agent. The tool list is permission-filtered: an agent only sees what its API token is allowed to touch.
- A batch endpoint (POST /api/batch) running up to 50 operations per request, plus native polling endpoints for Zapier, Make and n8n. Authentication is a token sent in the authtoken header, created from the API Management screen in the Perfex admin area.
- For n8n specifically, a community node, @themesic/n8n-nodes-perfex-crm, covering 20+ resources with 130+ operations plus a polling trigger, so workflows do not need hand-rolled HTTP nodes.
The automation story on RISE
Our REST API plugin for RISE CRM, currently at version 2.1.0, plays the same role on the other platform:
- 322 documented endpoints across 54 groups, with copy-ready code examples in cURL, PHP, Python and JavaScript.
- Machine-readable tooling: an OpenAPI 3.0 spec at /api/openapi.json, a Postman collection at /api/postman.json, Swagger UI at /api/swagger and an interactive playground at /api/playground.
- An MCP server at /api/mcp (JSON-RPC 2.0) publishing over 200 permission-filtered tools across more than 40 resources. It is opt-in: disabled by default, enabled from the admin-only API settings screen.
- Webhooks with HMAC-SHA256 signed delivery, per-webhook delivery logs and queued delivery with retries, plus polling triggers for n8n, Zapier and Make, and a batch endpoint for bulk work.
- An n8n community node here as well, n8n-nodes-rise-crm on npm, plus a public code-examples repository at github.com/themesic/rise-rest-api-examples carrying the Postman collection and the OpenAPI specification.
One practical note: because RISE runs on CodeIgniter, some server configurations need /index.php/ inside API endpoint URLs. The documentation covers it, but budget ten minutes for that the first time you integrate.
Side by side:
| Perfex module (v3.1.0) | RISE plugin (v2.1.0) | |
|---|---|---|
| Documented API surface | 74 paths, 144 operations | 322 endpoints, 54 groups |
| MCP for AI agents | 148 permission-filtered tools | 200+ tools, 40+ resources, off by default |
| Webhooks | 124 events, 22 groups, HMAC-signed, async retries | Event catalog, HMAC-SHA256, queued with retries |
| Batch requests | Up to 50 operations per call | Supported |
| No-code platforms | Zapier, Make, n8n | n8n, Zapier, Make |
| n8n community node | 20+ resources, 130+ operations, trigger | n8n-nodes-rise-crm |
How to decide
Choose Perfex CRM when the commercial paper trail is your backbone - proposals, estimates, invoices, subscriptions, contracts - and you want the bigger catalog of ready-made modules behind you. Its automation layer also has the longer track record in its changelog: our Perfex module first shipped webhooks in version 2.1.1 and MCP in 3.0.1, and both have been refined through the current 3.1.0 release.
Choose RISE CRM when you want client work and internal operations in one place - attendance, leave, teams and announcements alongside projects and invoices - and a single API that reaches all of it. Be aware that the deep automation surface (MCP, webhooks, batch, reporting endpoints) all arrived with the plugin's 2.1.0 release in July 2026 - earlier releases focused on endpoint coverage - so plan a little extra testing time for those newer pieces.
And an honest word about when to buy neither API product: if your whole workflow lives inside the CRM's own interface and no external system needs the data, an API module is shelfware. Both products also assume you are comfortable with REST - our own documentation for each says plainly that if you are not, you should bring in a developer. Finally, no API layer changes a platform's philosophy: if RISE's project-first model fits your agency better, the size of Perfex's module catalog will not fix the mismatch, and vice versa.
Links
- REST API module for Perfex CRM
- REST API plugin for RISE CRM
- All our Perfex CRM modules
- All our RISE CRM plugins
Running a specific stack and unsure which way to jump? Describe it in the comments and we will give you a straight answer.
Top comments (0)