Warpdrive is an open-source, self-hosted CRM for business-development teams that reimplements the core Pipedrive pipeline-and-deal workflow as software you run on your own infrastructure.

What it is

Warpdrive is a single-tenant, self-hosted customer relationship management application written in TypeScript and licensed under MIT. It lives in the business-software and CRM ecosystem, and it specifically replaces Pipedrive: the README describes it as "an open-source, self-hosted Pipedrive alternative for business-development teams." The information architecture and workflows follow the tools business-development teams already know, while all code, styling, and assets are original, and the interface ships its own visual layer built on shadcn/ui. Warpdrive is not affiliated with or endorsed by Pipedrive.

The concrete problem it solves is data ownership and per-seat cost. Pipedrive runs on vendor cloud and charges per seat, and customer data lives on vendor servers. Warpdrive instead runs on your own box, with your own Postgres and object storage, authenticated with your own Google Workspace. Customer data never leaves your infrastructure, and there is no per-seat bill. The scope is deliberately bounded: Warpdrive covers the core business-development loop and leaves Products, Projects, Invoicing, Forecast, multi-currency, web forms, chatbot, marketplace, and native mobile apps intentionally out of scope. It is a focused self-hosted CRM, not a feature-for-feature clone.

Key capabilities

• Kanban pipeline board with drag-and-drop stages, multiple pipelines, custom stages, per-stage weighted totals, rotting-deal indicators, and saved filters, plus board, list, and archive views.
• Deal workspace with a unified timeline covering activities, notes, files, email, and full change history, with participants, followers, labels, lost reasons, close dates, and won/lost handling.
• Contacts module for people and organizations with custom fields stored as JSONB, organization firmographics, org-to-org relationships, a leads inbox, and CSV import with an undo step.
• Two-way Gmail over the Gmail API, with thread linking to deals and people, open and click tracking, templates, signatures, merge fields, and scheduled send.
• Personal inbox plus shared, deal- and contact-linked threads with follow-up labels and unread state.
• Role-based permissions, teams, and user management, plus notifications and basic pipeline stats covering funnel, deal, and activity performance.
• Realtime updates across the board, inbox, notifications, and presence over WebSocket.

Who uses it and how

• Business-development teams that already run a Pipedrive-style pipeline and want the same workflow on hardware they control.
• Organizations with data-residency or data-ownership constraints that rule out vendor cloud CRM storage.
• Teams standardized on Google Workspace, since authentication and two-way email both run against Google rather than a separate mail provider.
• Sales operations that need role-based permissions, teams, and user management without a per-seat licence line item.
• Smaller teams that can accept the out-of-scope list, given that multi-currency, workflow automation beyond email scheduling, and native mobile apps are not provided.

Getting started

The README carries a "Quickstart (local development)" section and a separate "Self-hosting" section covering deployment on your own box with your own Postgres, object storage, and Google Workspace authentication; no published package name, Docker image, or compose file is named in the material provided.

How it compares

Against Pipedrive, the licence axis is MIT and open source versus proprietary, and the hosting axis is self-hosted single-tenant versus vendor cloud. Pricing differs accordingly: Warpdrive costs nothing beyond your own infrastructure, while Pipedrive is paid per seat. Data ownership is the sharpest contrast, since Warpdrive data stays on your infrastructure rather than vendor servers. The trade is scope: Pipedrive ships advanced pipeline stats, Products, Projects, Invoicing, Forecast, multi-currency, workflow automation, web forms, chatbot, marketplace, and native mobile apps, all of which Warpdrive marks out of scope, offering only basic pipeline stats and email scheduling as automation.

When to use it — and when not to

A self-hoster must operate Postgres, object storage, and Google Workspace authentication, and the two-way email features depend on the Gmail API, so teams outside Google Workspace should not pick it. Teams needing invoicing, forecasting, multi-currency, native mobile apps, or advanced automation should look elsewhere, because those are explicitly out of scope. The project is also young and lightly adopted, with 72 stars and 3 forks at last recorded push, and it has no established release or support track record in the facts provided.

pnpm install
cp .env.example .env
# bring up Postgres and MinIO with host ports and no TLS:
docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d postgres minio
pnpm db:migrate
pnpm dev

cp .env.example .env    # fill in domain, Google OAuth, storage, and secrets
docker compose up -d --build

pnpm test:unit          # fast unit tests
pnpm test:integration   # spins up a disposable Postgres via Testcontainers