Reselling software under your own name is an old idea. The hard part has never been swapping the logo. It is that a white-label arrangement puts a third company between a customer and their data, usually without the customer ever being asked.

White-label partners in the AI Rule Engine Partner Program can now sell the product as their own: their name, their colours, their domain. We built it so a partner gets a product that really looks like theirs, and its customers keep the final say over their own organizations.

Your brand, all the way through

The Branding tab of the Partner Portal holds the brand your customers see:

Product name and Primary colour, the two things needed to go live. The primary colour drives a full palette, in both the light and dark themes. An Accent colour for links and highlights is optional.
Logo and Favicon, for the toolbar, the sign-in page and the browser tab.
Support email, Support page, Help or documentation, Terms of service and Privacy policy, so Contact support and the Help menu lead to you rather than to us.
Hide “Powered by AI Rule Engine”, where your terms allow it.

A Live preview beside the form shows a small mock of the app in your brand as you type, in light and dark, before you save anything. Once your partnership is live, your own staff and every member of the customers you manage see your product rather than ours.

A domain of your own

The Domain tab serves the product on a subdomain you own, such as app.yourcompany.com. Claim it, publish a TXT record that proves you own it and a CNAME that points it at the app, and choose Check DNS records. The tab works out the exact host names to enter with your DNS provider, which is where most domain setups go wrong.

A claim has seven days to verify, and the tab shows the deadline. Once verified, we connect the domain to our hosting and switch it on.

The domain is checked again every day. If the TXT record goes missing three days in a row, the domain lapses: it stops showing your brand and accepting sign-ins, and you get a new value to publish. A lapsed domain never goes back live on its own. A person confirms with you that you still hold it first, because a domain whose registration expires can be registered by somebody else, who could then publish the old record. Your customers’ sign-ins should never depend on who registers a name next.

Customers you manage

A managed customer arrives in one of two ways. You create it on the Customers tab, naming the organization and its owner, or someone creates it after following your sign-up link. Either way it starts on the Free plan, and you take it from there:

Change plan shows each plan at your price with the list price struck through. Each paying customer has its own subscription on your card, at list price less your discount.
Transfer credits moves credits from your balance to theirs. If a transfer is interrupted, pressing Transfer again in the same dialog finishes it and never sends the credits twice.
Release customer hands the organization back. It drops to Free, sees the standard product, and can buy its own plan from then on.

Your customers see their plan and usage without a price, and a Managed by notice naming you where the plan choices would be. You set your prices and bill your customers yourself, and the product never shows them what you charge.

The customer decides

This is the part we spent the most time on. A white-label partner can see and change a great deal in the organizations it serves, so the customer is asked, in plain words, before that ever happens:

Agreeing to be managed. Before an organization is created through your sign-up link, its creator is told, by your company’s name, what you will see in your portal, that you choose and pay for the plan, and that signing in on your site lets you see and change everything they can in the organizations you serve. They can agree, or create the organization as a direct customer instead.
Agreeing to each hand-over. Sign-in itself happens on our standard address. Before a session is handed to your domain, the person is asked to confirm, by your company’s name, your product, your domain and the account they are signed in as. Cancel hands nothing over.
Blocking your site. A managed customer’s owners and admins can block sign-in through your site from their organization page at any time, and sign out every session on your domain that has worked in their organization.
A record of what you did. Everything a session on your domain does is recorded in the customer’s audit log as having come via your company, and a ruleset published there says so in its signed release evidence.

A session on your domain reaches only your partner organization and the customers you manage, and is checked again whenever it switches organization, so a released customer stops working there at its next switch. Anything that would outlive that session - API keys, AI provider keys, adding members or changing roles, single sign-on, audit streaming and backups - is managed on the standard address instead. Nothing set up through a partner’s site survives the partner losing access to it.

What stays ours

A few things keep naming AI Rule Engine whatever your brand, and we would rather say so than have you discover them:

The Google, Microsoft and LinkedIn consent screens, which name our app.
Links the platform creates for a running environment, such as human intervention reviews. They open on the standard address and show your brand after sign-in.
Stripe receipts and invoices, which come to you, because you are the one paying.
Dedicated environments installed in a customer’s own Azure subscription, which open only on the standard address.

Every detail of branding, domains and managed customers is in the White-Label Reselling documentation.

Visit RuleEngine.ai to try it.

The AI Rule Engine Team