One platform, eleven modules, one customer record
AlphaFlux is not eleven products bolted together. It is one system with a registry of modules, a single data model underneath, and three interchangeable ways to drive it.
Modules are switched on per company, not per installation
Every feature area ships as a module with a stable identity. A company sees the modules it has and nothing else.
That matters for two reasons. First, a company that answers the phone, books the work and invoices it does not have to look at fleet telematics or chemical registers it will never use. Second, turning a module on later never means a migration, because the module was always reading the same records the rest of the platform already keeps.
Modules are grouped into bundles so pricing stays legible, and any single module can be added to any plan as an add on. The catalogue, the bundles and the limits are all data, which is what makes white labelling possible: the whole catalogue can be repackaged under another brand.
-
A registry, not a menu
Each module declares its own identity, the limits it enforces and the permissions it needs. The screen is generated from that registry rather than hard coded.
-
No cross-module coupling
Modules work on shared records through defined interfaces, so one can be replaced without touching the others.
-
Bundles and add ons
A plan is a set of modules plus limits on customers, locations, users, volume and storage.
-
Limits that announce themselves
Approaching a limit is visible before it is hit, and hitting one never destroys data. It stops the next thing from being created.
How your data is kept separate from everyone else's
Multi-tenant software earns trust by being specific about what separates one company's records from another's. Here is exactly what does.
- Owner, administrator, office manager, dispatcher, technician, billing, marketing, support, and read only auditor
- Permissions are explicit per capability rather than implied by a job title
- Restricted actions are refused by the server and the reason is named in the response
Three ways to drive the same platform
The screen, the API and an agent are three clients of one thing. Nothing is available in one and missing from another.
This is the design decision that separates AlphaFlux from software that bolted a chat box onto an existing interface. Every capability is an interface first, which is why an agent can do real work here rather than summarising a dashboard.
It also means you are not locked into a single way of working. A manager uses the board. An ops lead scripts a nightly report. An agent answers the phone at nine at night. The same records change either way.
-
The screen
A console for the office and a mobile view for the field, both generated from the module registry and the permissions of the person signed in.
-
The API
A documented REST interface with a machine readable specification, so an integration can be written against it without a conversation.
-
The command line
A single binary that talks to the same API and prints JSON, for scripts, cron jobs and pipelines.
-
Agent access
A protocol server that presents the platform to an AI client as a set of callable tools, authenticated with a scoped key.
The engineering choices a buyer should care about
None of this is visible on screen, and all of it decides whether the platform is still fast and correct in year three.
-
Fast by construction
A small compiled service per component, no framework layered on top, and no third party script running in your browser. Pages and lists stay quick as the data grows.
-
Money in whole cents
Prices, payments, splits and recurring revenue are stored as whole cents and basis points. There is no floating point arithmetic anywhere near an invoice.
-
Callbacks verified when they arrive
Inbound carrier webhooks and provider callbacks are checked before they are acted on, so a forged request cannot create a job or move money.
-
An audit entry on every change
Who acted, under what role, on which company, doing what, at what time. Readable by the owner, filterable by an agent.
-
Idempotent where it counts
Recurring visit generation, campaign sends and imports are safe to run twice. A retry never bills a customer twice.
-
Built to be left alone
Scheduled work, retrying jobs and health checks run without supervision, and a person is alerted when something needs one.
If the platform is doing its job, nobody should be copying and pasting between two tabs.
What happens when a module goes live
The catalogue changes, not the data
Enabling a module registers its screens, its permissions and its endpoints. The records it needs already exist because the customer record is shared.
Limits attach to the company
The plan sets what the module is allowed to grow to. The module enforces those limits itself rather than trusting the interface.
Permissions appear for the roles you choose
Enabling a module adds new available permissions. Nothing is granted automatically, so nobody gains access because a feature was switched on.
History starts now, and it is complete
From the first day a module is on, its actions appear in the account timeline and the audit trail alongside everything else.
Questions people ask before signing up
Can I run more than one company on one installation?
Yes. One installation serves many companies, each with its own records, users, modules, limits and branding. That is the same mechanism white labelling uses, so an operator can run their own business and their customers' businesses side by side.
What happens when I reach a limit on my plan?
The platform stops the next record from being created and tells you which limit you reached and what plan lifts it. Nothing is deleted, nothing is hidden, and nothing you have already entered becomes read only. Raising the plan takes effect immediately.
Can I use just one module?
Yes. Some companies start with the phone module and nothing else, because that is the part that is losing them money. Modules can be added one at a time as the need appears.
Is there a mobile app?
The field views install to a phone home screen and work offline, which covers the technician case without an app store. Camera capture, signatures and location reporting all work from the browser, and status changes made without signal are queued and applied when the connection returns.
Do I need a server?
No. AlphaFlux runs on infrastructure the platform provider hosts and maintains. Self-hosting on your own hardware is available for organisations that require it, and it uses the same components.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.