# OpenDialer for Call Centers and BPOs: Your trunks. Your servers. Your margins.

Run outbound at volume on infrastructure you control. Use your existing SIP trunks, host OpenDialer yourself and keep your margins.

[Get Early Access](https://opendialer.dev/early-access/) · [See pricing](https://opendialer.dev/pricing/)

### Use the Trunks You Have

Connect existing SIP trunks through the SIP gateway, or route through Twilio or Telnyx.

### Host It Yourself

Run OpenDialer in Docker on your own servers and keep every call record in house.

### Built for Volume

Parallel dialing puts up to four lines behind every agent.

### Do-Not-Call, Enforced

A stop request logged once is honoured in every campaign, for every agent.

At volume, the dialer is not a tool. It is a cost line and a compliance risk, and usually somebody else controls both.

## Own the Stack

OpenDialer runs where you run it. Your trunks carry the calls, your database holds the records, and your team decides when to upgrade.

## Keep What You Earn

No per-seat licence and no markup on minutes means the savings from your carrier contracts stay with you.

## Stay in Control

Sessions are bounded by design, with limits on width, length and contacts, and every attempt is recorded with its final carrier state.

## The features that matter here.

### [Carriers and SIP](https://opendialer.dev/features/carriers/)

Your carrier. Your rates. Your numbers.

### [Parallel Dialer](https://opendialer.dev/features/parallel-dialer/)

Four lines ringing. One conversation.

### [Campaigns](https://opendialer.dev/features/campaigns/)

Turn any list into a calling machine.

## Questions, answered.

### Can we run OpenDialer entirely on our own infrastructure?

Yes. It runs in Docker with PostgreSQL and ClickHouse, and the optional SIP gateway connects directly to your trunks.

### Do we have to change carrier?

No. OpenDialer is provider-agnostic and works with the SIP trunks you already have.

---
Source: https://opendialer.dev/use-cases/call-centers/
