Create separate, segmented environments between your clients for full analysis and utilization. It simplifies management and billing, supports clear security boundaries, and provides white-label options with customer subdomains, storage and portals.
Select your own infrastructure resources for each client — SIP termination, SIP-compatible phones and recording storage — with no middleman. Buy termination, SMS and storage directly from the providers of your choice.
Built on a documented REST API for integration with your in-house systems. VoipAppz provides custom development, upgrades and new features for the requirements agreed in each project.
Use your carriers, infrastructure and existing product. Adapt the platform where the project requires it.
Operate customer accounts, numbers, routing, rate plans and billing from one system. Keep carrier relationships direct and give customers their own branded access.
Connect an AI agent, CRM, helpdesk or other application to phone numbers and carriers. Keep the product and its business logic.
Add browser calling, queues, campaigns and call records to the systems your team already uses.
Run voice at a customer site, in a private cloud or across multiple sites. Keep signaling, media, call records and recordings inside the required infrastructure boundary.
Keep it. VoipAppz connects the application to phone numbers and SIP carriers and provides the routing, recordings, billing and operational tools around it.
Keep the AI agent, CRM, helpdesk, browser application or workflow your users already know.
Use the compatible SIP carriers, phone numbers and rate plans that fit your operation.
Choose the cloud account, servers, networks and storage used for calls, data and recordings.
Set access, retention, maintenance and support requirements for each deployment.
How it works: Connect the application. Map numbers and carriers. Install the agreed voice nodes. Verify the call path. Operate through the portal, API or CLI. Discuss your system.
Comments from teams we have worked with on production communications projects.
The delivery controls and operating features needed to run calls, customers, providers, data and integrations from one platform.
We run the platform for you. Connect your product and carrier accounts, then manage customers, calls and operations without maintaining the platform hosts.
Keep call processing close to your carriers or customer network on a server you control. We install and verify it; your team keeps the agreed data, recording and network boundaries. Existing PBX systems can remain connected.
Run the control system in your own environment. Your team controls the domain, users, data, recordings, access rules and operating procedures while the same voice-node model serves each site.
The delivery loop builds and verifies each release. After deployment, the runtime layers route calls, process media and report health across the node fleet.
Keep your agent and product logic. Give users the portal, browser calling and customer views they need, with services, workflows, billing and reports in the same operating model.
Incoming calls reach a dedicated voice edge, which applies the route and selects a voice node. Add an active-active entry pair when availability requires it.
Run media, recordings and PBX services near a carrier, customer network or local data boundary. Add nodes as your sites or call capacity grow.
Each node sends outbound traffic over the trunk selected by your routing and cost rules. Keep existing PBX systems connected as SIP peers.
Release the portal independently from the voice fleet. Pin node images, validate every node before service and keep a defined rollback path.
Build and prove the node image in CI. Install and verify each node from the command line; health checks and monitoring continue after deployment. See the commands →
Run a softphone in the browser for assigned extensions, with calling, hold, transfer, mute and DTMF—without a separate desk-phone workflow.
Use the portal for call state and agent availability. Add the optional Chrome extension for a configured CRM screen pop beside the browser tools agents already use.
Connect calls to CRM, webhooks, email, SMS and provisioning through the service and workflow definitions your business needs.
Apply tariffs and plans, run prepaid or postpaid accounts, meter call usage and enforce balance rules before a call costs you money.
Start, transfer and end calls from your application, then retrieve the resulting call records.
Connect your product through the API, tokens and event callbacks. Test locally, inspect call events and ship changes without learning every telecom detail.
A read-only MCP endpoint lets approved developer tools search locally stored call events and review one call's timeline. It cannot change the system or run arbitrary database queries.
Build the complete voice-node image, place a real SIP test call and verify each node after installation.
Assign phone numbers and route them to menus, queues, groups or application workflows.
Store, index and retrieve recordings under the retention policy and storage location you select.
Review call activity and operational data, query historical records and export results to CSV.
Notify your product when a call is answered, transferred or ended so its workflow stays in sync.
Put customers and teams in the same conversation when a call needs more than one person.
See active calls, registered devices and node health while the service is running.
Route callers into queues, assign agents and skills, and follow queue and agent state.
Run outbound call lists with retry rules, dispositions and blacklist handling.
Send calls to the right destination for the customer’s hours, timezone and holiday schedule.
Build scripted menus, announcements and text-to-speech flows for customer-specific call handling.
Deliver voicemail notifications and recordings using customer-specific email templates.
Give customers branded access to the resources and views assigned to their account.
Free trial: evaluate the platform with your team before choosing a deployment. Contact us to arrange access and review your requirements.
CI builds and proves the node image. The installer writes the runtime under /opt/voipappz, registers the node, starts its container and finishes with a 16-check health verdict. The same operational checks remain available after deployment.
Reference: control-system CLI and the public node installer.
# install and register one voice node $ curl -fsSL https://raw.githubusercontent.com/voipappz/installer/main/install.sh | sh # from the installer checkout $ make help # list supported tasks $ make check # run the first CI gate $ make install # run install.sh locally $ sudo make up # recreate or start the node $ make logs # follow node logs $ make health # run the 16-check verdict $ make cli ARGS="sbc egress status" # on an installed node $ docker exec va-voip voipappz health $ docker exec -it va-voip voipappz monitor # release the customer-facing portal with Kamal # from the portal checkout (apps/portal) $ make verify $ make deploy DEST=<environment> # build, push, swap, smoke-test $ make status
Contact us to see it running on your own infrastructure
A concurrent call is an active internal or external call. Users include extensions. It is not a per-seat price.
| Voice and PBX | Browser calling, extensions, phone-number routing, voice menus, voicemail, call recording and group calling. |
|---|---|
| Contact center | Queues, agents, skills, live call control, business-hours routing and outbound campaigns. |
| Customer operations | Customer accounts, environments, users, permissions, balances, customer portals, dashboards and reports. |
| Billing | Tariffs, rate plans, prepaid and postpaid accounts, call metering, transactions and balance rules. |
| Integrations | API access, event callbacks, services, workflows, developer tools and read-only MCP documentation resources. |
| Infrastructure | Node health, live registrations, system monitoring, command-line checks, release checks and software updates. |
Billed separately: carrier charges, phone numbers, call usage, installation and custom integrations.
Support and monitoring: $280 USD per month, when required. Includes node and service health checks, alerts, incident handling, maintenance coordination and service reporting. Professional services are quoted separately.
One-time purchase: self-hosted deployments are available as a separate commercial offer. The quote covers the license, node capacity, installation and optional support.
Every quote states the tier, user and concurrent-call capacity, deployment scope, carrier costs and support. Discuss yours.
It is a repeatable delivery path for the voice layer: source and configuration checks, a complete node-image build, a real SIP round-trip, a versioned release, installation and a post-install health verdict. Project-specific carrier and acceptance tests are added to that path where required.
The current MCP interface is for approved developer and coding tools. It can search the local event store and return one call's events in time order without write access. Automatically giving a live voice agent previous recordings, transcripts or customer conversations requires a separately designed and approved integration.
PCloud is priced by concurrent calls and maximum users or extensions. Monthly billing is standard; annual billing is shown in the table. Carrier usage, installation, integration and support are quoted separately.
A self-hosted deployment includes the central control system and the agreed voice nodes on your infrastructure. The written scope defines capacity, sites, data storage, updates, installation and who operates each part.
Carrier calling and messaging charges are separate from the platform. Migration, integration, custom development, on-site work, training, professional server deployment and support are listed in the written scope.
Yes. Connect compatible SIP trunks and load your own rates. Your carrier relationship and carrier charges remain yours; the VoipAppz quote states any platform or service charges.
The optional support and monitoring plan is $280 USD per month. It covers node and service health checks, alerts, incident handling, maintenance coordination and service reporting. Support hours, response targets, covered systems and escalation contacts are stated in the written SLA. Migration, custom development, on-site work and training are professional services and are quoted separately.
Yes. CRM, helpdesk and business tools connect through the API and webhooks; deeper integration is scoped in the quote.
In a self-hosted deployment, the central database and recording storage run on infrastructure you select. A hybrid deployment can keep call processing and recordings at the required site. Storage location, retention, backup and access are agreed in the deployment design.
Customer separation and role-based access rules control which screens and operations an account can use. Authentication events and call activity are recorded for operational review. Any export, archive or retention requirement is defined as part of the deployment.
Yes. The architecture review defines what stays in your product, what connects to VoipAppz, and whether carriers, routing, recordings or customer deployments move to the VoipAppz layer. Your existing providers are not automatically replaced.
Keep LiveKit as the realtime room or agent layer. VoipAppz can sit around it with DID and customer assignment, carrier routing, human handoff, provider-cost records, usage, invoicing and audit. The production adapter and end-to-end call proof are scoped and certified for the deployment; this is not presented as a built-in adapter today.
Telecom operators, service providers, enterprise engineering teams, call centers and software companies.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
TechMer MER Group |
HOT Telecom |
Discuss your infrastructure, migration or integration +972.3.3723999
Support and documentationHelp center · Open a ticket
You can also email us