White-label VPN partners often ask how Mercure fits next to a branded Klox client. Short answer: branding, billing, and support are yours; the tunnel is still WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.
We keep commercial facts upfront: consumer pricing reference is $2.83/month on the yearly plan with 7-day money-back on your first purchase; partner economics live on /white-label and /reseller.
This page is for founders, agencies, and IT shops packaging Klox under their own name. It is not a consumer setup guide — end users still download your app build and press Connect.
Mercure may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Mercure mode" inside the tunnel.
Looking for a reliable VPN?
KloxVPN — from $2.83/month. Apps for every device.
What Mercure is in your stack
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Keep marketing, engineering, and support in one thread when `Mercure` changes. Silent renames cause refund spikes.
Document decisions in your runbook so marketing and engineering do not talk past each other.
It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.
- 1Skim the diagram above.
- 2Do the numbered steps once on your real network.
- 3Use the FAQ if a sentence was too long.
- 4Follow one related article — not ten tabs.
How to read this page
Store vs tunnel
App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
When users mention Mercure
If a subscriber cites `Mercure` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
What the tunnel still does
Document which version removed or renamed `Mercure` so SEO pages like this one stay truthful.
Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.
Run quarterly content audits on blog posts that mention `Mercure` so partners do not contradict each other.
You inherit server capacity, protocol maintenance, and core app updates from Klox infrastructure. You own front-line support and brand promise.
When unsure, link to /white-label instead of improvising specs in sales email.
| Crop | Desk | Next move |
|---|---|---|
| Mercure in a listing or helper | Packaging / white-label | Strip, rename, or leave |
| Handshake / Connecting | Consumer app | Swap protocol once |
| Store metadata lag | Console + binary | Edit listing after rebuild |
| Cafe destinations visible | VPN tunnel | Connect. Not a string rename |
Device cap
five devices per subscription is still enforced. Your pricing page should say so clearly.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Protocol choice
WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.
Reseller and white-label paths differ; pick one story on your homepage.
Branding checklist around Mercure
If you rebrand, update every surface in one release when possible. Half-old names confuse users and app review.
Reseller and white-label paths differ; pick one story on your homepage.
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
Confirm `Mercure` still appears where you expect: installer metadata, about screen, support templates, and marketing site.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
mercure is packaging until engineering says otherwise. The wrap is still WireGuard, OpenVPN, OpenConnect, and Shadowsocks.
— KloxVPN white-label notes
Comments and CMS plugins
Some partners embed comment systems or CMS tools named `Mercure`. That is website plumbing, not VPN configuration.
Keep marketing, engineering, and support in one thread when `Mercure` changes. Silent renames cause refund spikes.
2FA and admin panels
Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.
Run quarterly content audits on blog posts that mention `Mercure` so partners do not contradict each other.
Support scripts that work
Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Document which version removed or renamed `Mercure` so SEO pages like this one stay truthful.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Keep marketing, engineering, and support in one thread when `Mercure` changes. Silent renames cause refund spikes.
Refund policy
Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Launch week
Use launch checklist so `Mercure` questions do not land on day one.
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
What not to promise
White-label is speed to market with a proven tunnel — not a license to invent physics.
No invented "Mercure encryption." No secret city counts. No SOC 2 badge unless you actually hold one.
When unsure, link to /white-label instead of improvising specs in sales email.
Point enterprise buyers to /trust-center for what Klox publishes today, then add your own policies honestly.
Reseller and white-label paths differ; pick one story on your homepage.
Competitor comparisons
Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.
When unsure, link to /white-label instead of improvising specs in sales email.
Next step
Talk to sales via /white-label when you are ready to ship glass with your logo.
Document which version removed or renamed `Mercure` so SEO pages like this one stay truthful.
Release checklist when Mercure appears in builds
Archive old screenshots so marketing does not resurrect retired strings.
Keep marketing, engineering, and support in one thread when `Mercure` changes. Silent renames cause refund spikes.
Confirm billing pages still mention five devices and refund policy accurately.
Run smoke tests: install, connect WireGuard, switch to OpenVPN, sign out, reinstall.
Update release notes if `Mercure` is user-visible.
App review
Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
Versioning
Tag builds that change `Mercure` so support can map tickets to releases.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Partner FAQ snippets
Q: Refunds? A: Honor 7-day money-back on your first purchase or publish your own policy clearly.
Q: Do we operate servers? A: You brand and support; infrastructure follows your Klox agreement.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Run quarterly content audits on blog posts that mention `Mercure` so partners do not contradict each other.
Document which version removed or renamed `Mercure` so SEO pages like this one stay truthful.
Sales
Point enterprise buyers to /trust-center for published policies.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Reseller
Reseller program if you want volume without full white-label.
Reseller and white-label paths differ; pick one story on your homepage.
Long-term maintenance
Train new support staff on tunnel vs branding tickets in the first week.
Collect user feedback on confusing labels — rename in the next release rather than debating in chat.
Run quarterly content audits on blog posts that mention `Mercure` so partners do not contradict each other.
Store reviewers compare screenshots to real behavior. Mislabelled `Mercure` strings are an easy rejection reason.
Reseller and white-label paths differ; pick one story on your homepage.
Branding
Keep marketing, engineering, and support in one thread when `Mercure` changes. Silent renames cause refund spikes.
Contact
White-label for partnership questions.
Run quarterly content audits on blog posts that mention `Mercure` so partners do not contradict each other.
Key Takeaways
Document naming decisions, split support tickets, and do not promise features the core app does not have.
Key takeaway: Mercure is part of your brand or stack — not a new tunnel protocol. Klox white-label still ships WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.
Related Resources
Launch your branded VPN
KloxVPN — WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, $2.83/month on the yearly plan. 7-day money-back on your first purchase.
Explore white-labelFrequently Asked Questions
KloxVPN Team
Experts in VPN infrastructure, network security, and online privacy. The KloxVPN team has been building and operating VPN services since 2019, providing consumer and white-label VPN solutions to thousands of users worldwide.