MagnusBilling vs ASTPP
Community, Enterprise, free and paid — compared with public evidence
Executive summary
MagnusBilling 8 targets Asterisk 20, PJSIP and OpenSIPS. ASTPP primarily targets FreeSWITCH and documents a broader Enterprise edition. The reviewed evidence shows more operational workflows in MagnusBilling's public core, while ASTPP Enterprise documents corporate modules without a documented native MagnusBilling equivalent. The choice depends on telephony architecture and operating model. MagnusBilling source · ASTPP source · ASTPP Enterprise
Methodology
- MagnusBilling free is compared with ASTPP Community.
- MagnusBilling add-ons are compared with ASTPP Enterprise/Premium.
- Enterprise features are never presented as free.
- Code presence does not prove that a feature is included free.
- When evidence is insufficient, the page says that no equivalent was found in the public code and documentation reviewed.
- Every verification carries a review date.
Repository and project activity
Stars and forks indicate community interest. They do not, by themselves, prove software quality, scalability or security. Commit totals are not ranked because migrated, squashed and moved histories are not directly comparable.
MagnusBilling
- Stars / forks
- 340 / 155
- Last push
- 2026-08-15
- Default branch
- source
- License
- LGPL-3.0
- Repository
- Independent
- Technologies
- JavaScript / PHP / Asterisk
- Public version
- 8 (active line; latest GitHub release tag is 7)
ASTPP
- Stars / forks
- 178 / 172
- Last push
- 2026-06-26
- Default branch
- V6.0
- License
- AGPL-3.0
- Repository
- Independent
- Technologies
- PHP / FreeSWITCH / Lua
- Public version
- V6.0.6 (public repository); Enterprise V7/7.1 is vendor-documented
Free versus free
| Capability | MagnusBilling Core | ASTPP Community | Evidence |
|---|---|---|---|
| Prepaid and postpaid billingBilling | Verified in public codefree | Verified in public codefree | Core capability in both projects. |
| Routing strategies / LCRRouting | Verified in public codefree | Verified in public codefree | ASTPP documents LCR; MagnusBilling documents routes and routing. |
| ResellersAccounts | Verified in public codefree | Verified in public codefree | Documented in both public repositories. |
| DIDsTelephony | Verified in public codefree | Verified in public codefree | Documented in both. |
| Calling cardsTelephony | Verified in public codefree | Verified in public codefree | Documented in both. |
| IVR and queuesTelephony | Verified in public codefree | Public evidence not foundnot found | No equivalent was found in the public code and documentation reviewed for Community. |
| Campaigns and CallShopOperations | Verified in public codefree | Public evidence not foundnot found | No equivalent was found in the public code and documentation reviewed for Community. |
| InvoicesBilling | Verified in public codefree | Verified in public codefree | Documented in both. |
| Payment gatewaysPayments | Verified in public codefree | Verified in public codefree | MagnusBilling payment integrations present in the public LGPL-3.0 repository include PayPal, Stripe, Mercado Pago, PagSeguro, PayU Latam, cryptocurrency and multiple regional/custom gateways. Their source is included without a MagnusBilling add-on license; transaction, account or provider fees remain external. ASTPP Community documents built-in PayPal. |
| Web APIIntegration | Verified in public codefree | Verified in official documentationfree | MagnusBilling provides a public PHP API wrapper installed through Composer. Its connection documentation covers API credentials, user-group permissions and IP restrictions. ASTPP API availability is documented in its official edition matrix. |
| OpenSIPS integrationArchitecture | free | Public evidence not foundnot found | ASTPP is documented around FreeSWITCH; no equivalent OpenSIPS integration was found in reviewed Community sources. |
| Multi-server operationArchitecture | Verified in public codefree | Public evidence not foundnot found | Repository presence confirms implementation evidence, not a commercial entitlement outside the published license. |
Paid and Enterprise comparison
| Capability | MagnusBilling / Add-on | ASTPP Enterprise / Premium | Public price | Evidence |
|---|---|---|---|---|
| STIR/SHAKEN module | Verified in public codepublic code | Verified in official pricingcommercial | MagnusBilling: public implementation; certificate/provider costs separate. ASTPP: $1,000 one-time setup + $149/month; store says Community & Enterprise | MagnusBilling commit ccc9578 implements signing and verification on OpenSIPS 3.6; signing requires an STI certificate, EC private key and public HTTPS x5u URL. Public code confirms implementation, not zero-cost certificates or third-party services. The ASTPP store compatibility statement is more specific than its edition matrix. |
| Multi-tenant IP PBX and per-tenant service limits | Verified in public codepublic code | Vendor claim — not independently verifiedincluded | MagnusBilling: operator-defined monthly service price; ASTPP: included/availability described by vendor, public line-item price not found | MagnusBilling group modules grant tenant-facing capabilities; IVRs and queues are user-owned. The Services module documents operator-priced monthly services with call, recording disk-space and SIP-account limits. ASTPP availability is documented by the vendor but not independently verified in its public Community repository. |
| Shadow billing | Public evidence not foundnot found | Verified in official documentationenterprise | Enterprise/add-on; public price not found | Documented by ASTPP. |
| Demand- and quality-based routing | Public evidence not foundnot found | Verified in official documentationenterprise | Enterprise/add-on; public price not found | No natively documented equivalent was found in MagnusBilling sources reviewed. |
| Salesforce, Zoho and SSO integrations | Public evidence not foundnot found | Vendor claim — not independently verifiedenterprise | Commercial availability; line-item prices not confirmed | Edition matrix claim; not independently verified in public code. |
| Switch monitoring | Vendor claim — not independently verifiedincluded with app_mbilling | Verified in official pricingcommercial | MagnusBilling app_mbilling: $40/month per server, support separate. ASTPP Switch Monitoring: $10/month | MagnusSolution states that the commercial app_mbilling package includes Magnus Sentinel. The linked sales page confirms app_mbilling availability, architecture, price per server and separate support, but does not currently name Magnus Sentinel in its public text; the inclusion is therefore labeled as a vendor claim. ASTPP pricing is from its public Hub. |
Features documented only in ASTPP
The reviewed official ASTPP material documents shadow billing, demand- and quality-based routing, Salesforce, Zoho and SSO without a documented native MagnusBilling equivalent. Switch monitoring is no longer listed as ASTPP-only: MagnusSolution states that Magnus Sentinel is included with the commercial app_mbilling package, although the linked public sales page does not currently name Sentinel. Multi-tenant PBX and STIR/SHAKEN are also documented for MagnusBilling. This is not a claim that no custom or third-party implementation exists. ASTPP edition matrix · MagnusBilling app_mbilling
Features documented only in MagnusBilling
The MagnusBilling public project scope explicitly includes campaigns and CallShop workflows, Asterisk/PJSIP provisioning, AMI control and AGI call processing. Its public code also documents tenant-owned DIDs, IVRs, queues and SIP accounts, with group permissions and an operator-priced Services module that limits simultaneous calls, recording disk space and SIP-account creation. Payment gateways visible in the public LGPL-3.0 repository are included without a separate MagnusBilling add-on license; payment-provider fees remain external. The comparison does not classify WhatsApp, DID supplier or other visible integrations as free unless public entitlement evidence is available. MagnusBilling project scope · Payment gateway source
Limitations and documentation inconsistencies
MagnusBilling: older MB7/Asterisk 13 material remains public; MB8 is the current line. Old documentation is not automatically attributed to MB8, and visible integration code may still require separate commercial availability.
ASTPP: the public repository remains on V6 while Enterprise materials describe V7/V7.1. General documentation can mix editions, and the feature matrix can conflict with product-specific store metadata. Audience-size claims remain vendor claims unless independently audited.
Is MagnusBilling a fork or derivative of A2Billing?
No. MagnusBilling has an independent repository and development history. MagnusSolution previously worked with A2Billing, but later created a new platform using ExtJS, Yii and Asterisk. MagnusBilling can be used as an alternative or replacement for A2Billing, but it is not an A2Billing code fork.
MagnusBilling repository · A2Billing repository · MagnusSolution