White Label AI Agent Platform 2026: The Open Source Portal That Lets Agencies and Resellers Sell Voice and Chat Agents Under Their Own Brand

In short: The EchoCall White Label Portal is a customer portal and admin panel for AI voice and chat agents, run under your brand on your own server. The code is free on GitHub under the Apache-2.0 licence. [1] Agents, phone numbers and conversations come from EchoCall through a single API key. You pay for usage and your server, and you set your own prices.

We revised this post in October 2026. The old version named three required settings for the installation. With the bundled Docker Compose setup there are four, because Compose will not start without a database password. [2] It also said the euro for the card check is paid back and promised setup in ten minutes. We could not back up either, so both have gone. We also corrected the invoices part: the EchoCall service renders the PDF with your invoice details and the portal passes it on. [3]

What a white label AI agent platform is

A white label AI agent platform lets you sell AI phone assistants and chatbots under your own brand. The technology comes from a provider, while your customers see your name and prices. There are two models:

• A tenant at the provider. You get a partner account with your logo, sometimes your own domain. Code, database and interface stay with the provider. It is quick, but when the provider changes prices or features, so does your product.
• Your own portal. You run the interface and buy only the AI service via API. Server, updates and backups are your job, but code, portal accounts and branding are yours.

EchoCall offers both. In the EchoHub, partners get their own sign-in page with logo, company name and colour. This post covers the second route, the open source portal.

What the EchoCall White Label Portal is, and what it is not

The project puts one sentence at the top of its documentation: the portal is the interface, not the telephony. [1]

• On your server run an Angular front end and a NestJS back end with the customer portal, admin panel, user management, branding, mail sending and audit log.
• At EchoCall run the voice agents, chatbots, phone numbers, conversations, knowledge base and integrations. The portal fetches this data live with your reseller key and shows it under your brand. [1]

So you run no AI infrastructure and no telephony. Your server carries only the web interface, back end and database, and the documentation gives no minimum hardware specification. You do need an EchoCall account with reseller status, because the portal refuses a key from an ordinary customer account. [4] According to the README, the free pay as you go tier is enough: a one euro card check, no subscription fee, nothing to apply for. [1]

What your customers see in the customer portal

Your customers sign in on your domain to build voice agents and chatbots, manage phone numbers, read conversations with transcripts, check analytics, maintain their knowledge base, integrations and campaigns, and send you support requests, next to usage, balance, plan and invoices. [1]

Name, logo, colours and legal links come from your branding settings. According to the README, your customers never see EchoCall. [1] The interface is available in English, German and French. To see an agent from the customer's side, try the live demo: enter a website address, and in about 20 seconds the demo builds an agent you can call in the browser or write to.

What you control in the admin panel

The admin panel is where you run the business: [1]

• Customers: create an EchoCall account and its portal login in one step, top up or withdraw balance, read transactions and usage
• Plans and pricing, subscriptions, add-ons and invoices with PDF
• Phone numbers: import and remove them. The service refuses to remove a number a customer still holds. [3]
• Support tickets, revenue and cost analytics, and the agents your customers have built
• Settings: company data, payment keys, branding, mail server, sign-up and audit log

For support, you can open the portal as one of your customers and see exactly what they see. The administration stays locked meanwhile, and start and end go into the audit log. [1]

You invite users by email. Without a mail server, the portal shows you the invitations and sign-in links to pass on by hand. [4] Self-service sign-up is off by default and can only be switched on with a mail server. [1]

Installation with Docker Compose

The quick start takes four commands: [1]

git clone https://github.com/kristiangasic/echocall-whitelabel.git
cd echocall-whitelabel
cp .env.example .env
docker compose up -d

Before the last command, you set four values in .env: [2]

Then open the portal on port 3000, with a TLS-terminating reverse proxy in front for production. The first-run setup checks the connection to EchoCall and creates your admin account. [1] For the first hour, the operating guide recommends branding, a mail server, a second factor, a second administrator and one test restore of the first backup. [4]

Or use the ready-made image ghcr.io/kristiangasic/echocall-whitelabel with the tags 0.2.0, 0.2 and latest. [5] Without Docker, install manually with Node.js 22.22.3 or later and npm 12. DATABASE_URL can point at your own PostgreSQL 14+, MariaDB 10.6+ or MySQL 8 server instead of the bundled container, and the portal creates the schema at startup. [1]

Data ownership and GDPR: what lives on your server

Where the data lives is clearly split: [1] [3]

Conversation data is not copied into your database, so there are no transcripts there to secure or delete. Per the operating guide, you back up exactly two things: the database and the environment. [4]

EchoCall processes your customers' conversation data in IONOS data centres in Frankfurt and Karlsruhe. In the usual setup, you are a processor for your customers under Art. 28 GDPR and engage EchoCall as a further processor. [6] That belongs in your customer contracts. EchoCall's template is under DPA.

The portal does not produce ready-made GDPR reports. For your records you have the audit log and the security review in the repository.

Passwordless sign-in and other security features

The portal has no passwords. You enter your email address and receive a link that is valid for 15 minutes and works once. A second factor, if set up, is asked for afterwards. The response reads the same whether or not an account exists, so nobody can probe for addresses. [1]

If the mail server fails, this command on the server itself prints the link the email would have carried: [1]

docker compose exec app node apps/api/dist/cli/sign-in-link.js you@example.com

Anyone with access to the machine can get past the mail server, so protect server access. [4]

Per the README, sessions are server-side behind an httpOnly cookie, and requests that change data need a CSRF header. The reseller key never reaches the browser. Sign-in and token endpoints are rate limited, and a strict Content Security Policy is set. Every sign-in, including refused ones, and every administrative change is written to the audit log. [1] The security review describes what was checked, which limits the portal knowingly has and what you as the operator must do yourself. [7]

Business model: your own prices and the partner programme

1. You pay for usage. Your customers' minutes and chats are charged to your partner account at your conditions. The tiers are on the PartnerNet page, and the smallest has no monthly fee. [8]
2. Your customers pay your plans. You create plans, balance packages and add-ons in the admin panel and issue invoices there. The EchoCall service renders the document with your invoice details. If a mandatory field such as your address or tax number is missing, the service refuses the invoice. [3]
3. The difference stays with you. The revenue and cost analytics put revenue and costs side by side.

Worked example with assumptions, not a forecast: an agency sells an AI phone assistant to 25 existing customers as a monthly plan at 99 euros net. That makes 2,475 euros of revenue a month. Deduct usage at your purchase conditions, the server and your time for setup and support. Purchase conditions depend on your partner tier, so use your own figure. As a pricing guide, EchoCall's public customer prices on the pricing page are 75 euros for 250 voice minutes, 40 euros for 100 chat conversations. Phone numbers and telephony costs are not included.

Portal, WHMCS plugin or API: which route fits

All four routes run through your EchoCall partner account. For developers, The EchoHub API Guide 2026: Connecting Voice and Chat Agents to Your Software via REST API covers endpoints, webhooks and the reseller features.

Why open source makes the difference in white label

As a tenant in someone else's software, you depend on promises. With the portal, every line that touches the API key is public, and your data protection officer can check the code. What the Apache-2.0 licence means: [9]

• Use, modification and distribution are permitted, including commercially.
• You do not have to publish your changes. If you pass the code on, the licence text, copyright notices and a note on changed files go with it.
• The licence grants no trademark rights. That suits a white label product, since you trade under your own name anyway.

The portal needs no licence key. It is maintained with CI, a changelog following Keep a Changelog, version numbers following Semantic Versioning and a dependency bot. Release 0.1.0 came out on 17 September 2026, and the current release 0.2.0 on 22 September 2026. [3] [10]

One dependency remains: the AI service itself. Without a working connection to EchoCall, the portal shows its own pages but no agents and no conversations. [4]

Who the portal suits

• Marketing and web agencies that want to offer existing customers a product with monthly revenue
• IT service providers and MSPs whose customers prefer self-hosted software
• Call centres and answering services that want to add an AI phone service under their own brand
• Telephony and VoIP providers that already sell numbers
• Founders who want to launch a product for one sector, such as trades, practices or estate agents

If nobody in your team wants to run a server, the sign-in page in EchoHub or the WHMCS module is the shorter route.

Limits you should know about

• You run the server. TLS, updates, backups and monitoring are yours. The operating guide covers key rotation, lost second factors, mail outages, restores and upgrades. [4]
• Without a mail server you pass invitations and sign-in links on by hand, and self-service sign-up stays off.
• New features depend on the API version. Spoken conversations in the chat widget are on the repository's main branch but not yet in a release, and they need API version 1.13.0. [3]

How to get started

1. Create a partner account and complete the card check. According to the README, the account is ready straight away. [1]
2. Create an API key in the Developer area. It starts with eck_live_, is shown in full only once and belongs only in your server's .env.
3. Install the portal: clone the repository, set the four values, run docker compose up -d, add a reverse proxy, complete the first-run setup.
4. Set up your brand, invoice details and plans, then invite your first customer.

Code questions go to the GitHub repository, partner account questions to EchoCall support or the contact page.

Frequently asked questions

Is the White Label Portal really free?

The software is: Apache-2.0 on GitHub, no licence key. Costs come from your customers' usage at your partner conditions and from your server.

Do my customers see EchoCall anywhere?

According to the README, no. Name, logo, colours and legal links come from your branding settings, the portal runs on your domain, and emails come from your mail server.

What are the server requirements?

Docker (recommended) or Node.js 22.22.3 or later with npm 12, the bundled PostgreSQL or your own PostgreSQL 14+, MariaDB 10.6+ or MySQL 8, and a TLS-terminating reverse proxy in front. No minimum hardware is documented.

May I customise the portal and sell it under my brand?

Yes. Apache-2.0 permits changes and commercial use, and you do not have to publish your changes. If you pass the code on, the licence text and change notices go with it.

How do I bill my customers?

You create plans, balance packages and add-ons with your prices and issue invoices in the admin panel. The EchoCall service renders the PDF with your invoice details, as long as every mandatory field is filled in.

How does the portal differ from the WHMCS plugin?

The WHMCS module adds AI agents to an existing hosting client area as an add-on, and customers build their agents in the EchoHub behind your sign-in page. The portal is a standalone product with its own customer portal on your server. Both run through your EchoCall partner account.

Sources

1. EchoCall White Label Portal, README: github.com/kristiangasic/echocall-whitelabel
2. Configuration: docs/configuration.md
3. Changelog: CHANGELOG.md
4. Operating guide: docs/operating.md
5. Container image: ghcr.io/kristiangasic/echocall-whitelabel
6. Regulation (EU) 2016/679 (GDPR), Art. 28 Processor: eur-lex.europa.eu
7. Security review: docs/security-review.md
8. EchoCall PartnerNet, partner tiers: PartnerNet
9. Apache License, Version 2.0: apache.org
10. Release 0.2.0: github.com/kristiangasic/echocall-whitelabel/releases/tag/v0.2.0

All links were checked on 6 October 2026. This post is not legal advice.

Read next

• WHMCS Plugin for AI Voice and Chat Agents: How Hosting Providers and Resellers Sell AI Agents as an Add-On
• The EchoHub API Guide 2026: Connecting Voice and Chat Agents to Your Software via REST API
• AI and Data Security 2026: The GDPR Guide for Voice Agents and AI Chat in Customer Service
• Retell AI Alternative 2026: Costs, GDPR Without EU Operations, White Label and When Retell Is the Better Choice