EspoCRM

Last reviewed Sep 13, 2026 · 862 words

EspoCRM is the CRM I point at any business with 2 to 30 sales or support people who want Salesforce's shape without Salesforce's invoice. It runs comfortably in 1 GB of RAM, the interface loads in under a second on a cheap VPS, and the free AGPL edition covers contacts, leads, opportunities, cases, email, calendar and a decent workflow engine. The catch is a hard line between the free core and the paid extensions, and you should know exactly where that line sits before you build a process around it.

Fast is the whole pitch, and it holds up

EspoCRM has been shipping since 2014 and it is a single-page app over a PHP backend, so every click after the first page load is an API call, not a full page render. On a 2 vCPU VPS with MariaDB on the same box, list views with 50,000 records return in a few hundred milliseconds. That matters more than it sounds: the reason sales teams stop updating CRMs is friction, and a CRM that feels like a spreadsheet gets used. SuiteCRM, the other large open-source option, is heavier on every axis. Its per-page rendering is noticeably slower and it wants more RAM.

The paid line: reports, BPM and Outlook sync are not free

The core is complete for pipeline management. What costs money are the extensions sold by the EspoCRM company, at last check a few hundred dollars each, one-time, with a year of updates: the Advanced Pack (report builder, business process management, per-user workflow limits lifted), the Sales Pack (quotes, sales orders, invoices, product catalogue), plus Google and Outlook calendar and contact sync. Basic Workflows are free; the visual BPM flowchart is not. Email via IMAP and SMTP is free and works well, including per-user personal mailboxes and shared group mailboxes.

If your process depends on quotes or a report builder, budget for the packs from day one. If it depends on contacts, deals and email, you will never pay a cent. The larger CRM and ERP category has options that bundle invoicing for free, but none of them matches the pace of Espo's interface.

Deployment: Docker plus MariaDB plus one cron line

The official image is espocrm/espocrm. Pair it with MariaDB and you get a working install in one file:

services:
  db:
    image: mariadb:11
    environment:
      MARIADB_ROOT_PASSWORD: change-me
      MARIADB_DATABASE: espocrm
      MARIADB_USER: espocrm
      MARIADB_PASSWORD: change-me-too
    volumes:
      - ./db:/var/lib/mysql
  espocrm:
    image: espocrm/espocrm
    environment:
      ESPOCRM_DATABASE_HOST: db
      ESPOCRM_DATABASE_USER: espocrm
      ESPOCRM_DATABASE_PASSWORD: change-me-too
      ESPOCRM_ADMIN_USERNAME: admin
      ESPOCRM_ADMIN_PASSWORD: pick-something
      ESPOCRM_SITE_URL: https://crm.example.com
    volumes:
      - ./data:/var/www/html
    ports:
      - "8080:80"
  daemon:
    image: espocrm/espocrm
    entrypoint: docker-daemon.sh
    volumes:
      - ./data:/var/www/html

The daemon container is the part people skip and then wonder why nothing works. Email fetching, workflows, scheduled reports and notifications all run from EspoCRM's internal scheduler, which needs a cron tick every minute. On bare metal that is * cd /var/www/html; php -f cron.php > /dev/null 2>&1 under the web server's user. Without it the CRM looks fine and quietly does nothing in the background. Set ESPOCRM_SITE_URL to the real HTTPS address or email links and the mobile view will point at the wrong host.

Customisation happens in the admin panel, not in code

Espo's best feature for a small business is the Entity Manager. You can add fields, create whole new record types (say, Vehicles or Grants), define relationships between them, and lay out the detail and list views by drag and drop, all from Administration without touching PHP. Layouts, dynamic logic (hide field X unless Y equals Z), and formula scripts on save give you a surprising amount of a real app builder. Upgrades survive this because customisations live in custom/ rather than in core files. The flip side is a smaller third-party ecosystem than SuiteCRM's: expect to build integrations against the REST API yourself rather than find a module.

When a bigger project is the safer pick

Three cases. If you need a full ERP with accounting and stock, Odoo or ERPNext will serve you better than Espo plus a Sales Pack. If your team is developer-heavy and wants a modern Notion-style CRM with a GraphQL API, look at Twenty, which is younger but moving fast. If you are migrating from an existing SugarCRM-derived install, SuiteCRM shares the data model and will hurt less. For a team leaving Salesforce with a plain pipeline, Espo is the one I would install.

What I'd do

Docker Compose as above on a 2 vCPU, 2 GB VPS, MariaDB dumps nightly with mariadb-dump, the data/ folder in the same backup job. Set up group email inboxes in week one because that is what converts sceptical colleagues. Buy the Advanced Pack only when someone asks for a report the built-in dashlets cannot show. Update from the admin panel's upgrade page every couple of months, after a backup, and read the release notes, because minor versions occasionally require a PHP bump.