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

Search for a white label AI agent platform in 2026 and you will find dozens of providers promising the same thing: your logo, your domain, your prices. What almost none of them say out loud is that "white label" nearly always means a tenant inside someone else's software. The vendor owns the code, the vendor holds the data, and if the vendor doubles its prices or shuts the program down tomorrow, your brand is left without a product. That is exactly where the EchoCall White Label Portal comes in: a complete customer portal and admin panel for AI voice and chat agents, open source under Apache-2.0, running on your own server, installed with one Docker command. This guide covers what the portal does, how the business model behind it works, and why open source is the real differentiator in this market.

TL;DR: The essentials in 60 seconds

• What it is: A self-hosted white label portal for AI phone agents and chatbots. Your customers sign in under your brand, build agents, and see their conversations and invoices. You manage customers, plans, balances and support in the admin panel.
• What it costs: The software is free and open source (Apache-2.0). You only pay EchoCall for what your customers consume, pay as you go, no base fee. Your end customer prices are yours to set.
• How fast it runs: git clone, three environment variables, docker compose up -d. The first-run setup checks the connection and creates your admin account.
• What your customers see: Your name, your logo, your colors, your legal pages. EchoCall appears nowhere.
• Where the code lives: github.com/kristiangasic/echocall-whitelabel, including a Docker image, a security review and an operating handbook.

Why "white label" in 2026 almost always means "a tenant in someone else's software"

The market for white label voice AI has exploded over the last two years. Agencies, IT service providers, telecom carriers and hosting companies have realised that AI phone agents are the first product in years that small and mid-sized businesses actively ask for. Accordingly, most platforms now run a partner program: you get a sub-account, you may upload a logo, sometimes you can map your own domain, and you bill your customers yourself.

What you do not get in that model:

• The code. You cannot adapt, extend or audit anything. When a customer asks how their data is processed, all you can do is point at the vendor's assurances.
• The data. Customer accounts, sessions, settings and audit logs sit in the vendor's database. Switching means starting over.
• Price certainty. The white label markup is part of the subscription, and the subscription changes whenever the vendor decides.
• An end to the dependency. If the partner program is discontinued, your product disappears with it.

For many agencies that is still a fine way to start. But anyone who wants AI agents to become a load-bearing revenue line needs more than a tenant. They need a portal they own.

What the EchoCall White Label Portal is (and deliberately is not)

The portal is the interface, not the telephony. The project puts that sentence at the very top of its own documentation, and it matters for understanding the architecture:

• The portal (Angular frontend, NestJS backend) runs on your server. It contains the customer portal, the admin panel, user management, branding, mail delivery and the audit log.
• The AI capability (voice agents, chatbots, phone numbers, conversation processing, knowledge base, integrations) comes from the EchoCall platform through a single reseller API key. The portal fetches that data live and shows it under your brand.

This separation has two consequences worth knowing. First: you run no AI infrastructure, no telephony and no language models. That is why the portal is so lean and runs on a small VPS. Second: you need an EchoCall account with an API key. The free pay as you go plan is enough; it costs a one euro card verification, no monthly fee, and the euro is refunded.

Everything else is yours: the code (Apache-2.0 permits commercial use, modification and redistribution), the database, the branding, the pricing and the customer relationship.

What your customers see: the customer portal

Your customers sign in on your domain and get a fully fledged workspace for their AI agents:

• Voice agents and chatbots to create, configure and test
• Phone numbers to manage and assign to agents
• Conversations with transcripts, duration, counterpart and outcome
• Analytics on minutes, chats and conversation flows
• Knowledge base for their own company knowledge
• Integrations and campaigns (inbound and outbound)
• Support requests that go to you, not to a third-party vendor
• Usage, balance, plan and invoices at a glance

Name, logo, colors and legal links all come from your branding settings. The customer sees your brand, your legal pages and your prices. If you want to feel what such an agent is like from the customer's side, the EchoCall live demo turns a website into a voice or chat agent in 20 seconds. That is exactly the experience you deliver to your customers under your own name.

What you see: the admin panel

The operator's side is where the business runs. The admin panel bundles everything a reseller needs day to day:

• Customers: create the EchoCall account and the portal login in one step, top up or withdraw balance, read transactions and usage
• Plans and pricing: your own tariffs, your own margins
• Subscriptions and add-ons per customer
• Invoices with PDF, from the list and from the invoice page
• Phone numbers: manage, import and remove inventory
• Support tickets from your customers
• Revenue and cost analytics: what your customers pay, what you pay in usage, what stays in between
• Agents your customers have built, at a glance
• Company data, payment keys, branding, mail settings, audit log

One detail that is worth its weight in gold day to day: you can open the portal as one of your customers and see exactly what that customer sees. The session carries the customer's role, administration stays locked, and both the start and the end of the impersonation are written to the audit log. Support questions like "where do I find…" get answered in seconds.

Live in ten minutes: installation with Docker

The project's quick start is four lines:

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

In .env you set three required values: APP_URL (your domain), APP_SECRET (a random key) and ECHOCALL_API_KEY (your reseller key from the Developer section of your EchoCall account). Everything else is optional and documented variable by variable.

After start-up you open the portal on port 3000, put a TLS-terminating reverse proxy in front of it for production (the docs ship examples) and follow the first-run setup: it checks the connection to EchoCall and creates your admin account. Then you upload logo and colors, define your plans and invite the first customer.

If you would rather not build yourself, use the ready-made container image from the GitHub Container Registry: ghcr.io/kristiangasic/echocall-whitelabel:0.2.0 (also tagged 0.2 and latest). The image serves the web UI, the API and the health endpoints from one container and runs as an unprivileged user.

Own database? No problem. The Compose setup ships PostgreSQL, but a DATABASE_URL pointing at your own PostgreSQL 14+, MariaDB 10.6+ or MySQL 8 is all it takes. The schema is created and migrated automatically at startup.

Data sovereignty: what lives on your server and what does not

For GDPR conversations with your customers, the answer to "where is the data?" is decisive. With the White Label Portal it is cleanly delineated:

So the portal deliberately stores very little. There is no copy of conversation data in your database that you would have to secure and delete on top, and there is no path by which a customer or a browser could obtain your API key. The processing of the AI capability itself happens at EchoCall under its data protection terms, which you include in your own data processing agreement as a reseller. Background on that is in the GDPR guide to AI data security.

Security without passwords

The portal has no passwords. Whoever wants in types their e-mail address and receives a link that is valid for 15 minutes and works exactly once. A second factor, if set up, is still asked for afterwards. The response page reads the same whether or not an account exists for that address, so nobody can enumerate addresses.

That sounds like a small detail but solves several problems at once: there is no password database to leak, no password reset flow to attack, and no customer using "Password123".

On top of that come the standards you expect from a publicly auditable project:

• Server-side sessions in httpOnly cookies, mutating requests require a CSRF header
• Rate limits on login and token endpoints
• A strict Content-Security-Policy
• Every sign-in (refused or not) and every administrative change in the audit log
• A complete security review in the repository documenting what was checked

If the mail server goes down, there is a way in that only works on the machine itself: a CLI command inside the container prints the same sign-in link the mail would have carried. No back door from outside, but no locked-out operator either.

The business model: your prices, your margin, pay as you go

The arithmetic behind the portal is simple:

1. You pay for usage. Your EchoCall account runs pay as you go with no base fee. What your customers consume in minutes and chats is billed to you at reseller rates.
2. Your customers pay your plans. In the admin panel you create tariffs, balance packages and add-ons and bill your customers at your prices. The portal generates invoices with PDF.
3. The difference is your margin. The revenue and cost analytics in the admin panel show revenue, cost and contribution per period.

An example for scale, deliberately conservative: an agency with 25 customers, each on a monthly plan for an AI phone agent with a base fee and an included minute allowance, builds recurring revenue on top of its existing business (websites, ads, hosting) and ties that business more tightly to the customer. A customer whose phone is answered by your agent does not switch agencies lightly. The specific reseller terms are on the partner page, and the current end customer prices under Pricing serve as a reference point.

The portal is not the only route, either. If you already run WHMCS, you sell AI agents straight from the client area with the WHMCS plugin, and if you have your own system, you integrate the reseller API yourself. The White Label Portal is the option for everyone who wants a finished, standalone product without developing one.

Why open source is the decisive difference here

There is a reason white label portals for AI agents are practically never open source: the portal is the lock-in. Whoever owns the code owns the reseller. The EchoCall White Label Portal inverts that logic, and it does so for a sober reason: resellers who can audit, adapt and run their own portal build bigger businesses, and bigger resellers are better partners.

What Apache-2.0 means for you in concrete terms:

• Auditable. Every line that touches the API key, every piece of session logic, every database query is public. Your data protection officer can read instead of trust.
• Adaptable. An extra field in onboarding, an integration into your CRM, different invoicing logic: you fork and build what you need.
• Operable without permission. There is no license server, no activation key, no seat limit.
• Commercially usable. Apache-2.0 allows use in your own business without copyleft obligations for your modifications.
• Maintained in the open. CI pipeline, a changelog following Keep a Changelog, semantic versioning, Dependabot, issue and pull request templates are all part of the repository.

The dependency that remains is named honestly: the AI capability itself. It comes from EchoCall, and that is stated in the first paragraph of the README rather than in the fine print.

Who the portal is for

From conversations with partners, five profiles emerge that the portal was built for:

• Marketing and web agencies that want to offer existing clients a recurring revenue product that increases retention.
• IT service providers and MSPs whose customers ask for "something with AI" and who need a credible, self-hosted answer.
• Hosting providers that sell domains, mail and web space and want to add a product with a significantly higher basket value.
• Telecom and VoIP carriers that already sell phone numbers and want to deliver the agent with them.
• SaaS founders who want to launch a niche product for one industry (medical practices, trades, real estate, restaurants) under their own brand without building telephony infrastructure.

What they all share: they have the customers but not the time to build a portal. If you are unsure whether your own target group asks for AI agents, the industry articles on trades, medical practices and real estate agents contain concrete use cases that can be packaged into an offer one to one.

How to start today

1. Create an account. Sign up at EchoCall, choose the reseller plan and complete the card verification. There is nothing to apply for and nobody to write to.
2. Create an API key. Under Developer you generate your reseller key. It starts with eck_live_ and belongs exclusively in the .env on your server.
3. Install the portal. Clone the repository, fill in .env, run docker compose up -d, put a reverse proxy in front, walk through the first-run setup.
4. Set up brand and plans. Logo, colors, legal pages, mail server, then your tariffs. Invite the first customer or switch on self-service sign-up.

From that point on you are selling AI agents under your own name. The operating handbook in the repository covers the first hour, what to watch, how to rotate an API key, restore a backup and run an upgrade.

FAQ: White label AI agent portal

Is the portal really free?

Yes. The code is on GitHub under Apache-2.0, there is no license fee, no activation key and no user limit. Costs arise only from your customers' usage on the EchoCall platform, which you pay at reseller rates, and from your own server.

Do my customers see EchoCall anywhere?

No. Name, logo, colors and legal links come from your branding settings. The portal runs on your domain, mails come from your mail server, support tickets land with you. The provider of the AI capability is not visible to your customers.

What are the server requirements?

Docker (recommended) or Node.js 22.22.3+ for a manual install. The Compose setup ships PostgreSQL; alternatively you use your own PostgreSQL 14+, MariaDB 10.6+ or MySQL 8. For production a TLS-terminating reverse proxy goes in front. A small VPS is enough because the portal carries no AI load.

Can I customise and extend the portal?

Yes, that is the point of open source. The Angular frontend and the NestJS backend are cleanly separated, and the architecture is documented in the repository. Apache-2.0 permits modification and commercial use without requiring you to publish your changes.

How does billing my customers work?

You create plans, balance packages and add-ons with your prices in the admin panel. Customers see usage, balance and invoices in their portal. The portal generates invoices as PDF with your company details. How you collect the money (direct debit, bank transfer, payment provider) is your decision.

What happens if my mail server goes down?

Since sign-in works through e-mail links, there is a way in that only works on the server itself: a CLI command inside the container prints the sign-in link directly. You never lock yourself out, and from outside the path stays closed.

How is the portal different from the WHMCS plugin?

The WHMCS plugin adds AI agents as an add-on product to an existing hosting client area. The White Label Portal is a standalone product with its own customer portal, user management and billing. If you have WHMCS, take the plugin; if you want your own branded product, take the portal. Both run on the same reseller key.

Where do I get help?

Issues and discussions happen publicly in the GitHub repository. Questions about the reseller account, terms and the platform are answered by the EchoCall team via support and the partner page.