🪪 White Label Program

I help you stop selling websites.
Start selling command infrastructure.

MetrAIyux 0S ships as a complete, brandable business operating system. You put your client's name on it, deploy it to their domain, and collect monthly revenue. I already built the platform, the backend, and the operating model.

Available on Autonomous Office+ Read the Full Sell Sheet

📸 What you can show clients

I want your pitch to have real surfaces in it.

When you sell white-label, you are not promising a future build. You can show the command deck, the pricing surface, and the proof router before the client ever signs.

MetrAIyux command deck screenshotCommand deck MetrAIyux pricing screenshotPricing Live proof router screenshotProof router

💸 The economics

Here is what white-label looks like as a business.

You pay for Autonomous Office ($1,497/mo). What you charge your clients and how many you onboard determines your margin. Here is how I think about realistic scale.

3 clients × $800/mo = $2,400/mo revenue
$1,100/mo net
After your Autonomous Office cost. Month 3 you're profitable if setup fees covered onboarding.
8 clients × $800/mo = $6,400/mo revenue
$5,000/mo net
$60K/yr recurring at roughly $0 additional infrastructure cost per client (shared Worker, isolated workspaces).
15 clients × $1,000/mo = $15,000/mo revenue
$13,500/mo net
$162K/yr ARR. You're running a real SaaS business on top of infrastructure you deployed once.

Setup fee leverage

Beyond monthly recurring, charge a one-time setup fee per client ($1,500–$5,000 is reasonable for what they're getting). Three clients onboarded at $2,000 setup each = $6,000 upfront, before they pay a single monthly invoice. That covers your first four months of Autonomous Office.

Why clients pay recurring

Clients pay monthly because the platform is infrastructure, not a project. The Workers keep running. The approval gates keep working. New routing events keep logging to D1. Security scans keep firing.

The comparison your client makes is not "MetrAIyux 0S vs. nothing." It's "MetrAIyux 0S vs. Salesforce ($150/user/mo) + Notion ($20/user/mo) + a compliance tool ($300/mo) + an agency to tie it together ($5K/mo)." Against that stack, $800/mo for a complete branded operating system is cheap. That's the sale you're making.

🏗️ What your client owns

I want the client to receive a sovereign deployment, not a logo on someone else’s subdomain.

White-label is not a shared instance with their logo dropped in. It is a complete deployment under the client's brand, domain, and Cloudflare account. They own the infrastructure. You built it for them.

Brand

Their domain, their identity

Full logo, color, and copy replacement. Client's company name throughout. Deployed to their custom domain via Cloudflare Pages.

Infrastructure

Their own Cloudflare Workers

Workers deploy to the client's Cloudflare account. Their data lives in their D1 database, not yours.

Brains

Configured for their vertical

Cabinet structure and brain personas configured for their specific operating model — staffing, consulting, construction, healthcare, whatever their vertical.

Isolation

Runtime tenant separation

If they have their own clients, each gets an isolated workspace with 0meg4kAI tenant isolation at the Worker level. The platform scales with them.

🧭 Deployment process

How I would run a white-label engagement.

From intake to first invoice, a standard white-label deployment takes about 10 days. Most of that is configuration, not invention, because the platform is already built.

Day 1–2

Intake and brand configuration

Collect the client's brand assets (logo, colors, domain), operating model details (services, functions, cabinet roles), and Cloudflare account credentials. Run the brand replacement pass across the static site and update cabinet persona definitions.

Day 3–5

Deploy static site to Cloudflare Pages

Deploy the branded static site to the client's Cloudflare account. Verify DNS, SSL, and Cloudflare Access for the /admin/* route. Run link audit and confirm all 522 pages resolve.

Day 5–7

Deploy and configure the 8 Workers

Add environment secrets (SkyeGate token, Resend API key, ADMIN_TOKEN or SkyeGate role config). Run D1 migrations. Deploy all 8 Workers via wrangler. Verify each Worker endpoint responds correctly and logs to D1. Wire Resend approval notifications to client's admin email.

Day 7–10

Smoke test and admin onboarding

Walk through the admin brain chat, issue test commands, verify routing receipts appear in D1, confirm 0meg4kAI quarantine triggers for test violations, confirm approval email fires. Walk the client through the admin tutorial and their specific operating workflows.

Day 10+

Handoff and recurring billing starts

Deliver the handoff documentation kit. Start the client's monthly billing. The platform is live, the client is operational, and you collect recurring revenue on infrastructure you deployed once.

❓ Common questions

What I expect builders and agencies to ask.

Can I customize the brain structure for each client?
Yes. The brain routing system uses JSON persona definitions and a keyword classifier. You can add, rename, or reconfigure cabinet brains for each client's actual operating structure. A construction company doesn't need a Staffing brain. A staffing firm doesn't need a Construction Materials brain. The configuration is per-deployment.
What if the client already has a Cloudflare account and Workers deployed?
The Workers are standard Cloudflare Workers (ES module format) with no conflicts with existing Worker deployments. They deploy to separate named routes. The only thing to watch is D1 namespace naming if the client has existing D1 databases — wrangler.toml bindings are configurable per deployment.
Do I need to know Cloudflare's platform to deploy this?
You need to be comfortable with the Cloudflare dashboard, basic DNS configuration, and running wrangler CLI commands. You don't need to understand Workers internals or D1 SQL deeply — the deployment documentation covers every step and the D1 schema migrations are included. If you've deployed a web application before, this is within reach.
What happens when MetrAIyux 0S ships updates?
You receive the updated Worker kits and static site patches. Applying them to client deployments is your responsibility as the white-label licensee — it's a re-deploy operation, not an automatic update. For clients on managed hosting through you, this is part of what the monthly fee covers.
Can a client add their own team members to the admin layer?
Yes. SkyeGate handles this via the allowlist configuration in the auth bridge — you add email addresses permitted admin-scoped access. Cloudflare Access policies can be configured per user or per group. A team of five people can all have access to their admin brain and approval inbox with different role scopes if needed.

🚀 Ready to start

I keep white-label on
Autonomous Office and above.

Get on Autonomous Office, complete the deployment, and you have what you need to sell serious command infrastructure to your clients under your own brand within two weeks.

See Autonomous Office Pricing Read the Full Sell Sheet