# Callia

> The AI voice agent platform Vapi and Retell keep for themselves — owned once, white-labeled, and rebranded as yours.

Source page: https://saascode.ai/products/callia
Machine-readable record: https://saascode.ai/products/callia.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $349 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Callia is a self-hosted platform for building AI phone agents. The platform owner deploys it, connects their own telephony, speech-to-text, text-to-speech and language-model keys, and their end-users create agents that handle business calls autonomously — inbound reception, outbound campaigns, appointment booking, lead qualification and support.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/callia — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://callia.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Agent operator** (`member`) — `user@demo.com` / `demo123`
  Runs agents, reviews calls and manages contacts.
- **Business owner** (`admin`) — `jordan.kim@demo.com` / `demo123`
  Runs the account: agents, campaigns and the team.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every organisation and the admin panel.

Or open a role directly: https://saascode.ai/demo/callia?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, super_admin, viewer
- **tables: 60** — distinct CREATE TABLE statements across every applied migration
- **migrations: 52** — .sql files in supabase/migrations
- **page modules: 85** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 125,509** — lines of code (comments and blank lines excluded) across 913 TypeScript files (114,600) and 76 SQL files (10,909); node_modules and .next excluded
- **api route files: 196** — files named route.ts under src/app/api
- **http operations: 263** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 60 tables, 103 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-06-20

## Complete capability inventory

11 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Building & running agents

- **Agent Builder (create/edit/publish/version/rollback)** — Agents are created, edited, published, versioned and rolled back. A published agent is a fixed version answering calls; editing produces a new one.
- **Call Flow Designer (@xyflow voice nodes)** — A visual canvas for the conversation: branching, conditions and the voice-specific nodes a phone call needs. It is where the difference between a chatbot and a phone agent lives — a call is linear, interruptible and unforgiving of a pause.
- **Knowledge Base + RAG** — Each agent carries its own knowledge: documents, FAQs and URLs, chunked, embedded and searched at conversation time. The agent answers from the business's own material rather than from the model's general knowledge.
- **Inbound Calling** *(seller-authored)* — Answers real calls on a real number, with barge-in so a caller can interrupt, transfer to a person when the conversation needs one, and business-hours handling for when nobody is there. It ships on every tier.
- **Outbound Campaigns (real dial engine)** — A real dialling engine rather than a queue that hopes. Campaigns dispatch through a job queue, and a do-not-call check runs before every dial — before, not as a nightly reconciliation, because the compliance failure happens at the moment of the call.

### Providers, numbers & calls

- **Call Logs & Recordings** — Every call produces a record: the recording and the transcript, synchronised so a passage in one selects the moment in the other.
- **Phone Number Management** — Buy, assign, release and route numbers, and set caller ID. A number is assigned to an agent, which is what makes a multi-agent deployment tractable — a main line, a support line and an outbound campaign line, each answering differently.
- **Contact Management** — A contact record with tags, custom fields and per-contact call history, plus a do-not-call flag that the outbound engine honours before dialling.
- **Provider Configuration (5 layers)** — Configuration is per layer, and each carries the same three controls: a key, a connection test, and an active toggle.
- **Analytics Dashboard** — Call metrics and agent performance on every tier. The deeper layer — a peak-hours heatmap, knowledge-gap analysis showing what agents were asked and could not answer, and cost tracking per provider — is available on the higher tiers.
- **Voice Library Browser** — Voices from every configured synthesis provider, aggregated into one browser with preview. Choosing a voice is comparison shopping, and comparing across four provider dashboards is how people end up staying with whoever they started with.

## What each system gives the operator

*stated.*

- **Building & running agents** — A phone line that answers in your customer's voice and knows their business.
- **Providers, numbers & calls** — Every layer of the stack stays swappable, so no vendor owns your margin.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Swap the voice, the model or the carrier without rebuilding the agent.

Voice AI is assembled from other people's services, and each one is a hand on your margin. A telephony provider raises per-minute rates, a voice vendor changes its licensing, a model doubles in price — and a platform that hardcoded any of them passes the increase straight through to whoever is running the business. Agencies discover this at renewal, when the economics that justified the whole operation stop working and there is no way to move without rebuilding everything they have shipped to clients.

### Interruptions, transfers and after-hours calls behave the way callers expect.

Text assistants fail on the phone in ways that are obvious the first time a real customer calls. Someone interrupts mid-sentence and the agent keeps talking over them. Someone asks for a human and there is nowhere to go. Someone calls at nine at night and gets the same script as noon on Tuesday. Each one reads to the caller as a company that could not be bothered, and the business that bought the service hears about it from their own customers before they hear about it from anyone else.

### The check runs before the dial, not as a report afterwards.

Outbound calling carries a rule that everyone knows and most systems enforce too late: some numbers must not be called. A queue that dials first and reconciles later has already made the call by the time anyone notices, and the record of it exists. For the business running the campaign this is not a reporting inconvenience — it is the one part of outbound where being wrong is expensive, and it is the part cheap dialling tools are quietest about.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security and vector search for agent knowledge.
- **A telephony account** (required) — Supplied by the platform owner. Numbers are bought through it.
- **Speech and language provider keys** (required) — At least one of each layer. All five layers are the owner's own accounts.
- **A job queue** (required for campaigns) — Outbound dialling dispatches through it. Inbound calls are unaffected.
- **Relay component** (required for direct browser test calls) — Deployed alongside the platform. Without it that one test mode reports a clear error; live calling is unaffected.
- **Object storage** (required for recordings) — Call audio.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 125,509 lines across the application and its database, 60 tables defined by 52 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Callia demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Agent operator, Business owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 85 page modules and 263 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A telephony account, Speech and language provider keys, A job queue, Relay component, Object storage. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 52 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $349?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Best AI Voice Agent Platforms in 2026, Ranked by Who Owns Your Phone Numbers When You Leave](https://saascode.ai/inside/best-ai-voice-agent-platforms-in-2026-ranked-by-who-owns.md)
- [What You Still Pay — Then What Separates the Platforms](https://saascode.ai/inside/callia-vs-dograh-ai-voice-agent-platform-comparison-self.md)
- [Callia: a multi-tenant voice-agent platform you own and rebrand](https://saascode.ai/inside/road-to-callia.md)

## Links

- Catalog page: https://saascode.ai/products/callia
- Product record: https://saascode.ai/inside/products/callia
- Live demo: https://callia.saascode.ai
- Every product: https://saascode.ai/llms.txt