Image: GitHub
Why it mattersA small sales team pays Pipedrive per seat for a known set of parts. Warpdrive covers the same parts on one machine, with no vendor bill.
A small open-source project is doing a classic trick this week. It takes a paid product that a sales team already knows. It rebuilds the parts people actually use. Warpdrive is a self-hosted alternative to Pipedrive. On 3 November 2026 it ranked 25 on Trendshift's daily list of trending GitHub projects. The repository shows 137 stars and 7 forks total.
What it rebuilds
Warpdrive's README matches its own feature set against Pipedrive's. Both products have a Kanban pipeline with drag-and-drop stages. Both support multiple pipelines. Both have a deal workspace with activities, notes, files and a full history timeline. Both let a team keep people and organizations with custom fields. Both have a leads inbox with CSV import and an undo step. Both do two-way Gmail: threads tied to deals, open and click tracking, templates, signatures and scheduled send. Both carry role-based permissions, team management and saved filters.
The parts Warpdrive leaves out are also written down. The README lists products, projects, invoicing, forecast, multi-currency, web forms, chatbot, marketplace and native mobile apps as out of scope. It says the goal is a focused CRM for the core workflow.
Where the data goes
Pipedrive is a paid cloud product. Warpdrive is single-tenant and self-hosted. The team runs the software on its own box. Postgres and an S3-compatible store live on the same box. Sign-in goes through the team's own Google Workspace. Customer data never leaves the team's own machine. There is no per-seat bill, because there is no vendor.
The deploy story is a single-box Docker set-up. One Docker Compose file brings up every piece: the app, a WebSocket server, a background worker, Postgres, MinIO for files, and Caddy for automatic HTTPS. Caddy provisions TLS for the domain. Postgres and MinIO stay on the internal network. The author's deploy document covers the Google OAuth setup and the required environment variables.
The stack
Warpdrive is written in TypeScript. The app runs on Next.js with the App Router. Drizzle ORM talks to Postgres through tRPC and TanStack Query. The interface is shadcn/ui on top of Tailwind, with dnd-kit for the board and Zustand for the board's local state. The realtime channel is a self-hosted WebSocket server backed by Postgres LISTEN/NOTIFY. Gmail works through the official Gmail API over Google OAuth. The package manager is pnpm.
The project status is honest. The README says Warpdrive is used in production for a single team's BD workflow and is actively developed. 137 stars and 7 forks is a small base. A team adopting it today is close to the author, with a smaller crowd around them for support.
For a small sales team or a sales-ops engineer
The practical check is one question. Does the team use the parts Warpdrive rebuilt, or does it need the parts the project left out? A team that lives in the Kanban board and the deal timeline can run Warpdrive on one virtual machine. A team that needs invoicing, forecasting or multi-currency cannot.
The per-seat Pipedrive bill grows with headcount. A self-hosted CRM has one bill: the box it runs on. Open-source means the team can also change what it does not like. The cost is the time to run it, patch it and back it up.
Source
sneg55, warpdrive repository, GitHub. The star count and trending position are from Trendshift's daily ranking.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.