A white-label funnel builder with no per-client fee
Apache-2.0 with no commercial-use restriction: stand up a branded deployment for each client, on their domain, with their payment accounts and your name on the admin. Nobody charges you for the twentieth one.
curl -O https://raw.githubusercontent.com/autonnel/autonnel/master/docker-compose.yml
docker compose up
# Settings -> Branding: name, logo, favicon
# Settings -> Domains: the client's hostnameRepeat per client. The licence cost of the second one is the same as the first.
The actual editor, unedited. No mockups on this page.
Autonnel vs Hosted agency platforms
The right-hand column describes the common shape of agency-tier funnel platforms sold by sub-account, not one specific product.
| Autonnel | Hosted agency platforms | |
|---|---|---|
| Licence cost per client | $0. Apache-2.0 with no commercial-use restriction and no separate agency tier. Run it for yourself, for clients, or inside a paid service. | Priced per sub-account or per client, which is the meter that grows with your roster. |
| What each client gets | Their own deployment: their domain, their branding, their Stripe or PayPal keys, their storage bucket, their database. | A sub-account inside the vendor tenancy, with the isolation the vendor chose to give it. |
| Whose name is on it | Yours or your client's. Display name, logo and favicon are configuration, and they carry into the admin UI, the storefront pages and outgoing email. | Usually white-labelled too, often as a paid upgrade. |
| Cross-client console | None. Ten clients means ten deployments you operate and upgrade. | One console across all sub-accounts. This is the thing they are actually selling. |
| Consolidated billing | None from us. There is no invoice to consolidate, because there is no licence fee. | One vendor invoice covering every client. |
| What happens when a client leaves | You hand over a deployment and a database, or you delete it. Apache-2.0 means the client can keep running it without you. | The sub-account and its data stay in the vendor tenancy. |
| What happens if we raise prices | Nothing. The version you deployed keeps working, under a licence that cannot be revoked. | Your margin per client is set by their pricing page. |
Agency platforms charge per sub-account because the roster is the growth curve they want to price against. Apache-2.0 has no such meter: the twentieth client costs the same in licence as the first, which is nothing. What you pay per client is a server and a database, and you keep the difference between that and what you invoice.
Each client gets an isolated install with its own database, catalog, orders and users, rather than a partition inside somebody else's tenancy. That is a real boundary rather than a policy, and it means a client can be handed over, exported or shut down without touching any other client.
Display name, logo and favicon are settings on every install, free and self-hosted included. They carry into the admin header, the storefront pages and the transactional email your client sends. Nothing has to be unlocked and nothing phones home.
Be clear-eyed about what you are choosing here. Ten clients means ten deployments: ten upgrades, ten sets of credentials, ten things that can break at 2am, and no single screen showing all of them. We do not sell a managed agency plan today, we have no consolidated billing, and there is no way to log into one account and switch between client workspaces. If those are the features you are shopping for, a hosted agency platform is a better fit and you should buy one. Choose this when the per-client licence fee is the line item you want to delete, and when client isolation and a clean handover matter more than a unified dashboard.
FAQ
Can I really charge clients for something I did not pay for?
Yes. Apache-2.0 has no commercial-use restriction and we do not sell a separate agency tier. You can run Autonnel for yourself, for clients, or inside a paid service you charge for. There is no revenue share and nothing to report to us.
Can one deployment host several clients?
Not usefully. A deployment can bind multiple domains, but all of them serve the same set of pages, catalog and orders, so multi-domain is for one client's markets or vanity hostnames rather than for separating clients. Give each client their own deployment.
Can my client log into an admin on their own domain?
On a self-hosted deployment, yes: it is your deployment, so the admin lives wherever you host it. On our managed Cloud this is not available - the tenant console stays on an autonnel.com hostname, and only the storefront binds to a custom domain.
What can I actually rebrand?
The display name, the logo and the favicon, set in Settings and applied across the admin UI, storefront pages and transactional email. Beyond that the code is Apache-2.0, so anything else is a fork you are allowed to make.
Can I put clients on your Cloud instead of hosting them?
You can, one tenant per client at a flat $29 a month with 0% of their revenue, but each tenant is a separate account with its own login. There is no agency view across them and no combined invoice. If that shape works for you it is available today.
Do you have a managed agency plan?
No. A hosted plan with one account managing many client workspaces does not exist today, and we would rather say so than sell a roadmap. If that is what you need, tell us your client count and we will factor it into whether we build it.
How do clients keep their own payment accounts?
Stripe and PayPal credentials are per-deployment settings, so each client connects their own processor and the money never routes through you or through us. The same is true of their storage bucket and their LLM key.
One login, many client workspaces, one invoice: we have not built it, and whether we do depends on how many people actually want it rather than on how good the idea sounds. If you run client funnels for a living, tell us how many clients you carry and what the cross-client screen would need to show. That is the input we are weighing.
Email sales@autonnel.com