One platform from checkout to licence key
What the platform covers
Each module works alone; the value is that they share one source of truth.
Storefront and checkout
A product catalog, tiered pricing and a checkout wired to POK, Stripe or PayPal. Buyers pick the gateway they like at checkout.
Licence issuing
A paid order issues a key on its own, tied to the seat count of the site pack bought. No one has to send keys by hand.
Protected delivery
Digital files are served through signed links tied to the order, not a public path anyone can guess. A shared link stops working.
Support and CRM
Tickets, contacts and chat transcripts sit on the same customer record as the order. One look shows what a person bought and asked.
Invoices on every order
Branded PDF invoices are attached to each order and emailed for you. Your logo and footer text are set once in the invoice builder.
Content and SEO engine
Products, pages and articles are written against your own catalog, with scheduling and SEO checks built in. All of it runs on the same database.
Why one platform and one database matter
Most stacks answer "who is this customer?" differently depending on which tool you ask. The store knows about the order, the licence manager knows about the key, and the helpdesk knows about neither. Every link between them is a place where the three can disagree.
PABAA keeps them in one schema. The order that issued a licence, the licence that grants access and the ticket asking about it are joined rows. That works for any shop that sells online, from a kitchen appliance store to a software vendor. They are not records to match by email across three exports, the way a separate CRM system would need.
Runs on ordinary hosting
The platform is PHP and MySQL with a statically exported frontend. It installs on standard cPanel or Hostinger hosting through a simple wizard. There is no Node process to watch and no container to maintain. It is the kind of hosting a web design agency offers with a website.
Role-based from the start
Super Admin, Admin, Manager and User are checked against a permission matrix that covers every module. Access is enforced in the backend, not just hidden in the interface. Licences themselves are handled by the Master Hub licensing module.
Key takeaways
- One platform covers sales, licensing, delivery and support.
- Everything shares one database, so the facts agree.
- It runs on ordinary PHP and MySQL hosting.
- Roles are enforced on the server for every module.
Frequently asked questions
Can I use only part of the platform?
Yes. Modules can stay switched off. The licensing and checkout core does not need the AI features.
Does it work with WooCommerce?
It can run alongside WooCommerce or on its own, depending on how you sell.
What are the hosting requirements?
PHP 8.1 or newer, MySQL 5.7 or newer, and a scheduled task if you want scheduled publishing.
Is support included?
Yes. Tickets, contacts and chat transcripts are part of the platform, all linked to the same customer record.
See the platform priced
Every tier includes the full platform. The difference is how many sites it covers.