Your platform, your name, your customers
Five thousand a month buys the entire platform with every limit lifted, under your brand, on your domain, with the right to sell it to your own customers as your own product.
What it is, plainly
Some companies do not want to buy software. They want to sell it. This is the version of AlphaFlux that makes that possible.
A franchise group wants one system across its locations, branded as the group. A managed service provider wants to offer field operations alongside what it already sells. A software company serving an industry wants an operations module without building one. An agency running marketing for service businesses wants to hand them the tool as part of the retainer.
In each case the platform is the same platform. What changes is whose name is on it, whose domain the customer signs in at, whose sending identity the email comes from, and who sets the pricing.
There is one flat monthly price, every module is included, no limits are applied, and the right to resell is part of it rather than a separate negotiation.
-
Your brand everywhere a customer looks
Sign in page, console, mobile view, emails, invoices and the customer facing pages. No mention of AlphaFlux remains.
-
Your domain
Customers sign in at your address. Certificates are issued and renewed automatically, so there is nothing to maintain.
-
Your sending identity
Email leaves under your domain with your authentication records, so your reputation is built rather than borrowed.
-
Your bundles and pricing
Define your own plans, your own limits and your own add ons from the module catalogue, and price them however you want.
What arrives with it
Everything, with nothing held back for a higher tier.
Why the badge exists on every other plan
On every other plan, the customer facing pages carry a small line stating that the platform is provided by AlphaFlux. It is worth being direct about why, because it is an unusual thing to do.
It is how a host is discovered, and it is a large part of why a free plan can cost nothing. A company running happily on the free tier is, in a small way, paying for it by being an example. That keeps the free tier genuinely free rather than a trial with a countdown.
The badge is deliberately minimal. It appears only on the pages an end customer might see, never on the internal dashboards a company works in, and never in emails, invoices or anything a customer reads that is about money.
White label removes it entirely, along with every other trace, and hands over resale rights. That is the trade, stated plainly rather than buried in a footnote.
How a white labelled deployment works
Setting it up is a configuration exercise, not a fork of the software.
-
One line of configuration per brand
Brand name, marks, colour system, domain, sender identity and catalogue. Every one is a setting rather than a code change.
-
You hold the accounts
You provision workspaces and manage them. Your customers see your support, because it is your product.
-
Isolation is unchanged
Each of your customers is a company with its own records and its own scope, exactly as they would be under any other plan.
-
Your own integrations
The interfaces are the same ones documented for developers, so your team can build on them under your own API surface if you want.
-
Updates included
New modules and improvements land in your deployment. You are running the platform, not a frozen copy of one.
-
Your customers' data stays theirs
The platform does not read your customers' data, does not use it to train anything, and does not market to them.
If your customers are signing in somewhere with someone else's name on it, you are renting an audience rather than building one.
What white label changes
| Standard plans | White label | |
|---|---|---|
| Modules | By plan | All of them |
| Limits | By plan | None applied |
| Customers and locations | By plan | Unlimited |
| Users | By plan | Unlimited |
| Branding | AlphaFlux | Yours |
| Sign in domain | Platform domain | Your domain |
| Email sending identity | Platform | Yours |
| Your own bundles and pricing | Not included | Yes |
| Resale to your own customers | Not included | Yes |
| Badge on customer facing pages | Present | Removed |
| Support | Shared queue | Named contact |
| Setup | Self service | Onboarding included |
Questions people ask before signing up
Do I need technical staff to run it?
No. Branding, domains, sending identities and catalogues are configuration. Infrastructure is looked after, and certificates and updates are handled. Technical staff are only needed if you want to build custom integrations, and the interfaces for that are documented.
Can I set my own prices and keep the difference?
Yes. You define your own bundles, your own limits and your own pricing, and you bill your customers directly. The platform does not see your customer relationships and does not sell to them.
Is there a limit on how many customers I can have?
No. The white label plan carries no limits on customers, locations or users. The flat monthly price does not change as your customer base grows.
Will my customers ever be contacted by AlphaFlux?
No. They are your customers. The platform does not market to them, does not email them, and does not use their data for anything beyond running their workspaces.
Can I offer less than the whole platform to my customers?
Yes, and most operators do. You have every module available, and you decide which of them appear in which of your bundles. A customer of yours sees your product line, and you keep the rest in reserve for the next tier up.
What if I want custom modules?
That is an enterprise conversation. Custom modules follow the same contract as the existing ones, which is what allows them to be added without disturbing anything already running.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.