Open-source CRM
The open-source CRM for outbound sales
AgentSDR is an open-source CRM under the MIT License, built for outbound sales. It runs your outreach and your replies in one app, on your own server and database, with no per-seat fee.
Action required
Every reply the AI has classified, with the answer it drafted. Approve, edit or reclassify.
In the queue
23
replies and follow-ups due
Drafts to review
11
written by your model
Follow-ups due
4
past their due date
Errors
0
nothing failed today
Queue
Newest reply first. Hover a reply or a draft to read it whole.
The short version
What is an open-source CRM?
An open-source CRM publishes its source code under a licence that lets you run it, change it and share it. The practical effects are that you can host it where you choose, read what it does with your data, and extend it without waiting for a vendor.
Most open-source CRMs are general-purpose: contacts, accounts, deals and a set of modules. AgentSDR is narrower on purpose. It is an AI CRM that starts when a prospect replies to outbound, so the CRM and the sending engine are one product. The guide to the best open-source CRMs compares it with the general-purpose projects.
This page is about the CRM. For AgentSDR as an AI SDR that automates the outreach itself, see open-source AI SDR.
What you get
What does AgentSDR's open-source CRM cover?
Everything between a prospect's first reply and a booked meeting, plus the lead data behind it.
One record per lead
Replies from email, LinkedIn and WhatsApp land on the same record, with the cold outreach that came before them.AI classification
Each reply is sorted into Interested, Customer, Not interested or Other, with a subcategory you define and a confidence score.Drafts you approve
The AI writes the answer from your instructions and knowledge base. By default a person reviews and sends it; a sequence can be set to send on its own.Follow-up sequences
Timed follow-ups of up to 30 steps start once you send the reply, and stop when the lead replies again.Meetings through Cal.com
A booking moves the lead to Meeting Booked, and a meeting that passes with no outcome asks whether they showed up.Lead database
People and companies exist once, whatever channel or campaign they are in. Import from CSV or Excel and add custom fields.API and MCP
A small public API adds leads to email campaigns. An MCP server lets Claude and other assistants work the CRM queue.Teams and clients
Organizations keep one team's or one client's leads, accounts and rules apart on a single deployment.
The CRM in detail is on the AI CRM page. The unified inbox and lead database have their own pages.
Fit
Is AgentSDR a general-purpose CRM?
No, and the boundary is clear enough to decide on in a minute.
| You need | AgentSDR | Look instead at |
|---|---|---|
| Cold email, LinkedIn and WhatsApp outreach with replies tracked | Yes. This is the product. | Nothing else is needed. |
| AI-classified replies and drafted answers | Yes | Nothing else is needed. |
| Invoicing, quotes or billing | No | An accounting or billing tool, or a general-purpose CRM with those modules. |
| A helpdesk or support tickets | No | A helpdesk tool. |
| ERP: inventory, purchasing, manufacturing | No | An ERP suite. The Odoo comparison covers one that includes a CRM. |
| A broad contact and deal database for every team | Partly. The lead database and pipeline serve outbound. | A general-purpose open-source CRM; see the comparisons below. |
Side-by-side pages: Twenty, SuiteCRM, EspoCRM, Odoo, Salesforce and HubSpot.
The licence
What does the MIT License allow?
The MIT License lets you use, copy, modify, self-host, distribute and sell AgentSDR, including in closed-source products and as a hosted service. You do not have to publish changes you make. You keep the copyright and licence notice in copies you distribute. The LICENSE file in the repository is the binding text.
Some open-source products keep their best features in a paid edition or restrict how you may host them. AgentSDR has one MIT-licensed codebase. Decisions about the project are written down in GOVERNANCE.md.
Make it yours
How do you customize an open-source CRM?
Start inside the app. Change the code only when the settings run out.
| Level | What you change | Where |
|---|---|---|
| Fields | Add fields to people and companies: text, number, date, select and other types. Imported columns the importer does not know become merge fields. | Settings, Lead columns |
| Categories | Add, rename and re-describe the subcategories that replies are sorted into, and give each a funnel stage. | Settings, CRM and leads, Lead categories |
| Sequences | Write reply and follow-up flows with a goal for each step, then attach one to a subcategory. | CRM, Sequences |
| AI behaviour | Write the instructions and knowledge documents every draft and classification draws on. | Settings, AI |
| Pacing | Set emails a day, send gaps, sending hours and the LinkedIn and WhatsApp limits for each organization. | Sending rules |
| Integrations | Add leads from another application with the public API, or let an assistant work the CRM over MCP. | Settings, API keys and AI assistants |
| Source | Fork the repository and change anything. TypeScript, Next.js, PostgreSQL and Drizzle. | The repository |
The full walkthrough, from a server to a customized install, is in how to self-host a CRM.
Running it
What do you need to run it?
One app and one PostgreSQL database. There is no queue server and no separate worker.
| Requirement | Detail |
|---|---|
| Database | PostgreSQL 16 or newer. The Compose file starts PostgreSQL 18 for you. |
| Runtime | Docker with Compose, or Bun 1.2+ (Node.js 20.9+ also works) to run from source. |
| Public address | A public HTTPS origin if webhooks and email links must reach people outside your network. |
| Email for sign-in | A Resend account, only to invite people or send password resets. |
| Channels | Google Workspace for email, Unipile for LinkedIn and WhatsApp, your own OpenRouter key for AI. Each is connected inside the app. |
Run it as a single instance, because the email sender has no distributed lock. The details, and what you take on by hosting it, are on self-hosted CRM. If you are weighing it against a vendor-run tool, read open-source vs SaaS CRM.
Who it suits
Who uses an open-source CRM for outbound?
- Founders who run outbound themselves and want the sequences, inbox and CRM without a stack of subscriptions.
- Agenciesthat run outreach for several clients and need each client’s leads, accounts and rules kept apart.
- Sales teams that want a shared pipeline, per-rep accounts and one inbox.
- Teams that need to run sequences across channels and keep the data on their own infrastructure.
FAQ
Questions, answered
What is an open-source CRM?
A CRM whose source code is public under a licence that lets you run, change and redistribute it. You can read how it works, host it yourself and fix or extend it. AgentSDR is an open-source CRM under the MIT License, aimed at outbound sales.
What is the best open-source CRM for sales?
It depends on the job. If you need a general-purpose CRM with modules beyond sales, compare the general-purpose projects in our guide to the best open-source CRMs. If your work is outbound, meaning cold email, LinkedIn and WhatsApp plus handling the replies, AgentSDR is built for that and puts the sequences and the CRM in one app.
Is AgentSDR a full replacement for Salesforce or HubSpot?
No. AgentSDR is an AI CRM built around outbound and replies. It has no invoicing, no helpdesk and no ERP. Teams that use those tools mainly to track outbound and replies can move that work to AgentSDR. Teams that rely on the rest of those suites should keep them or pick a general-purpose CRM.
Does an open-source CRM cost anything?
AgentSDR has no licence fee, no seats and no per-contact pricing. You pay for the server that runs it, the accounts you connect to it (Google Workspace for mailboxes, Unipile for LinkedIn and WhatsApp) and the AI usage on your own OpenRouter key.
Can I customize AgentSDR?
Yes, at two levels. Inside the app you add custom fields to people and companies, edit the lead categories, build reply sequences and write the instructions and knowledge the AI uses. Because the code is MIT-licensed you can also change the source, and you do not have to publish your changes.
Where does the data live?
In your own PostgreSQL database, with call recordings in your own Cloudflare R2 bucket. Saved integration credentials are encrypted in the database with a key you control. The services you connect, such as Google, Unipile and OpenRouter, process the data that passes through them under your own accounts.
Keep exploring
- Self-hosted CRMYour CRM, your database, your server
- Open-source sales engagementEmail, LinkedIn and WhatsApp sequences you host yourself
- Best open-source CRMsSeven open-source CRMs compared for sales teams
- Self-host a CRMFrom a server to a running CRM in an afternoon
- Open-source vs SaaS CRMCost, control and effort, side by side
- Salesforce alternativeAn open-source CRM for outbound teams
- HubSpot alternativeOpen-source CRM and outreach without per-seat tiers
- Open source & self-hostedMIT-licensed code on your server, with your own AI key
- AI CRMEvery reply classified and the lead moved for you
Read it, run it, change it
Clone the repository or start it with Docker Compose. The code, the data and the keys stay with you.