Self-hosted · Asterisk & FreePBX
One console. Every customer.
AI voice across the PBXs you already run. Your providers, your server, your Customers — predictable appliance pricing with no AVA per-minute platform fee.
How it fits together
One appliance beside your estate. Recordings stay with you; live audio goes only to the AI providers you choose.
Bring your own providers
Mix and match per agent. You pay providers directly at their rates — we never take a slice of a minute.
Provider availability and model choices depend on the capability contracts shipped with the installed release. Unsupported combinations stay visible in Console with a reason.
Pricing
One monthly appliance subscription. No AVA usage meter or per-minute platform fee.
$149per appliance / month
billed monthly · prices in USD
- 3 Customers included
- 3 Agents included per Customer
- Customer portal included
- $35 / month per additional Customer
- $15 / month per additional Agent
- Customer capacity capped at $499 / month
- Your own provider keys
Designed for MSP margin
The first 3 Customers are included. At full included capacity, the AVA subscription works out to $49.67 per Customer / month.
Customers 4–13 add $35 / month each. Further Customers add no AVA subscription charge, so base plus Customer capacity is capped at $499 / month.
Each Customer includes 3 Agents. Additional Agents are $15 / month each and are billed separately from the Customer-capacity ceiling.
AI provider usage is billed to you directly at the provider's rates. AVA adds no per-minute platform fee.
Capacity increases are prorated immediately; decreases take effect at the next renewal. First payment refundable for 14 days. Renewals are non-refundable except where required by law.
Get started
Step one changes nothing — it only looks.
-
1
Check the server
Read-only. Reports PBX flavour, Asterisk version, modules and ports.
sudogives it the access andPATHit needs to detect your system — without it, Asterisk itself can read as missing. It still changes nothing.Run this on the server you intend to use. The authenticated installer on clean Debian 12 amd64 installs signed managed-native Asterisk 22. Ubuntu is not supported, even with Asterisk installed; other operating systems and ARM/arm64 are also unsupported. A supported existing FreePBX 17 with Asterisk versions 20 or 22 on Debian 12 amd64 is reused; AVA never installs a second Asterisk beside it. A supported existing vanilla Asterisk 22 on Debian 12 amd64 is reused; AVA never installs a second Asterisk beside it.
curl -fsSL https://get.agent6789.com/check | sudo bash -
2
Get your token
Emailed instantly. One per account, single-use.
-
3
Install
Review and approve the proposed changes. On an accepted existing PBX, AVA adds dedicated accounts and integration includes. On a clean supported host, it installs managed Asterisk 22; Docker may also be installed when required. Recovery is phase-dependent and can retain prerequisites and Installation identity. Follow the final health result and any manual steps before using the printed Console link and one-time password.
curl -fsSL https://get.agent6789.com/operator | sudo bash -s -- --token YOUR-TOKENRead the setup guideRequirements, Self-test, first Customer and recovery.
Specs
| Tested on | FreePBX 17 with Asterisk versions 20 or 22 on Debian 12 amd64 · vanilla Asterisk 22 on Debian 12 amd64 |
|---|---|
| Also detected | Issabel, VitalPBX, Wazo — support follows as each is validated |
| Transport | AudioSocket · chan_pjsip · ARI |
| Install | Guided signed installation; duration depends on the host and downloads. May install Asterisk and Docker. See the setup guide for approval and recovery boundaries. |
| Data | Recordings, transcripts and call history stay on your server |
| Licensing | Verified offline · limits gate management actions only, never calls |
| Core licence | Engine is MIT and stays free · the Operator layer is commercial |
Verify what you install
Every release manifest is signed. The public key lives here, on a different host from the download endpoint — so whoever serves you a binary is never also the one telling you what it should be.
Release signing key (Ed25519, base64)
NVqQU1O//GNzRdvwfcP1yg5t7UIv3Gk8yD6XYpbjsTw=
Fingerprint
SHA256:VjpqIaG9Gw9dKejBG1nMx5qTEAgeXoUVIJy6XL_GHmI
Each release ships MANIFEST.json and MANIFEST.sig on its GitHub
release page, pinning every container image by digest. The installer refuses any image
reference that is not a digest, so a tag can never be repointed at different software after
your Installation is running. ·
Security contact: [email protected]