Warpdrive Review

Overview

Warpdrive is a self-hosted, MIT-licensed CRM that reimplements Pipedrive's core business development loop: kanban pipelines, a deal workspace, contacts and organizations, and two-way Gmail. It is single-tenant, runs on your own box, and has no per-seat bill. The README's comparison table against Pipedrive marks products, projects, invoicing, forecasting, multi-currency, workflow automation, and native mobile apps as intentionally out of scope, and the docs are blunt about it: if your team needs those, this is not the right tool. What it covers is deep for a project this young: pipelines with weighted stage totals and rotting-deal indicators, people and orgs with JSONB custom fields, a leads inbox with CSV import and undo, funnel stats, RBAC, and Gmail with thread linking, open and click tracking, templates, merge fields, and scheduled send. Sync is go-forward only: the docs state there is no backfill, so existing mail is never imported. AI access exists, but not as AI features. There is no lead scoring or drafting model; instead the project ships a documented MCP server at /api/mcp with 29 tools, OAuth 2.1 protected, so Claude, ChatGPT, or Cursor can search and update the CRM under each user's own permissions. The server has no delete tools for CRM records and no send tool: drafts are written for review and sending stays human. Contact enrichment is not AI either; it wraps your own paid Apollo, RocketReach, or GetProspect keys behind a review step. Setup is docker compose up -d --build after copying .env.example, bringing up Postgres 16, MinIO, a background worker, and Caddy for TLS. Requirements are specific: a domain with a second s3. subdomain record, ports 80 and 443, and a Google Workspace OAuth client, since Google is both the SSO and the mail provider. One maintainer, 35 commits, one release, 72 stars, and a public mirror of a private upstream: treat it as a young tool worth an afternoon, not a settled platform.

Key Integrations

How to install

1. Prerequisites (docs.warpdrivecrm.com/setup): a Linux box with Docker and the Compose plugin, a domain with A/AAAA records for both the app host and an s3. subdomain (browser uploads POST presigned requests there; skipping it breaks every upload), ports 80 and 443 open, and a Google OAuth client from the project that owns your Workspace.
2. Install is two commands from the repo: cp .env.example .env, fill in domain, Google OAuth, storage, and secrets, then docker compose up -d --build. That starts caddy, postgres (postgres:16-alpine), minio, app, ws, and worker, plus one-shot migrate and createbuckets services.
3. Secrets come from openssl: openssl rand -base64 32 for TOKEN_ENCRYPTION_KEY, openssl rand -hex 32 for WS_TICKET_SECRET, openssl rand -hex 16 for the MinIO keys, and openssl rand -base64 32 for OAUTH_SIGNING_KEY. DATABASE_URL and the other secrets accept a VAR_FILE variant for Docker secrets.
4. In Google Cloud, register two redirect URIs: the app sign-in callback and https://<your-domain>/api/gmail/oauth/callback. Set SEED_ADMIN_EMAIL (the first Google sign-in is promoted to admin) and keep ALLOW_FIRST_LOGIN_ADMIN=false, which the env boundary enforces in production.
5. Verify with docker compose ps and curl -fsS https://<domain>/api/health (returns {"ok":true}). Upgrades are git pull && docker compose up -d --build, with migrations running in the one-shot migrate service before the app restarts.

Requirements

Google Workspace is effectively mandatory: Google SSO is the only documented auth path and the Gmail API the only mail integration, with GOOGLE_WORKSPACE_DOMAIN available to pin sign-in to one domain. NEXT_PUBLIC_WS_URL must be set at build time; if it is missing the app still starts and looks healthy but the board, inbox, notifications, and presence indicators silently never update. Telemetry is switchable: leave POSTHOG_KEY and POSTHOG_HOST empty or set DISABLE_TELEMETRY, and DISABLE_UPDATE_CHECK=true for deployments that should make no outbound calls. Uploads cap at 25 MiB by default (MAX_FILE_BYTES). No RAM or CPU sizing is documented anywhere. If a CSV import sticks at "uploaded", the docs point at the worker process: background jobs run only there.

Best for

Business-development teams already on Google Workspace that want Pipedrive's pipeline-and-Gmail loop on their own infrastructure: single-tenant, MIT licensed, no per-seat bill, data in your own Postgres and S3-compatible storage, and an MCP server so assistants can work the CRM under each user's permissions.

Not for

Teams that need products, projects, invoicing, forecasts, multi-currency, workflow automation beyond email scheduling, web forms, or native mobile apps: the README marks all of them out of scope and the docs say plainly that this is not the right tool if you need them. Also not for shops without Google Workspace, and not for bulk integration work: CSV is the documented import route, with no REST API, no webhooks, and no API keys.

Hands-on notes

Assessed from github.com/sneg55/warpdrive, docs.warpdrivecrm.com (about 25 pages), and warpdrivecrm.com in September 2026; we have not deployed an instance. The repo is young and small: 72 stars, 35 commits, one contributor (Nikita Sawinyh), one release (v1.0.0, July 19, 2026), zero issues and zero pull requests ever filed, latest commit September 7, 2026. The docs site config describes the repo as a public mirror of a private source-of-truth repository, with pull requests merged upstream and synced back on the next release.

The correction that matters: our earlier text said the repo's CLAUDE.md and PostHog MCP config help developers work on the code rather than users sell, and recorded no API. Both were wrong. Warpdrive ships a user-facing MCP server as a documented headline feature: 29 tools (13 read, 16 write) at /api/mcp over OAuth 2.1, with no delete tools for CRM records and no send tool, so drafts are written for review and sending stays a human action. What remains true is the absence of a REST API, webhooks, and API keys.

Second correction: our earlier summary implied the README compares Warpdrive with other open-source CRMs. The comparison table is against Pipedrive only, and its out-of-scope rows are verbatim: products, projects, invoicing, forecast, multi-currency, workflow automation (email scheduling only), web forms, marketplace, and native mobile apps. The README calls Warpdrive a focused, self-hosted CRM rather than a feature-for-feature clone, and says it is used in production for a single team's BD workflow.

Free applies to the software, not every workflow: contact enrichment requires your own paid Apollo, RocketReach, or GetProspect keys, which are encrypted at rest and put the provider on a 24-hour cooldown when quota runs out. Backups need both a pg_dump and the miniodata volume; the docs note that a database dump alone restores records whose attachments are gone.

Verdict

A scoped, honestly documented self-hosted Pipedrive alternative whose AI story is an MCP server rather than a model. One maintainer and a private upstream mean you are betting on a person, not a community.

Similar Tools