Brand the app; the tunnel stays the same.

White-Label VPN and Sparkle

Sparkle can sit on a branded KloxVPN client. It does not replace WireGuard, OpenVPN, OpenConnect, Shadowsocks, the five-device limit, or the 7-day first-purchase refund.

KloxVPN Team
12 min readPublished 2021-10-31
White-Label VPN and Sparkle
Brand the app; the tunnel stays the same.

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.

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.

Sparkle may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Sparkle mode" inside the tunnel.

White-label VPN partners often ask how Sparkle 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.

Looking for a reliable VPN?

KloxVPN — from $2.83/month. Apps for every device.

View Plans

What Sparkle is in your stack

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

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.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Reseller and white-label paths differ; pick one story on your homepage.

WireGuard versus OpenVPN
Klox ships four protocols: WireGuard by default, OpenVPN when UDP fails.

    How to read this page

  1. 1Skim the diagram above.
  2. 2Do the numbered steps once on your real network.
  3. 3Use the FAQ if a sentence was too long.
  4. 4Follow one related article — not ten tabs.
Desks that must not share a checkbox. Confirm branded macOS packaging with engineering. Not a Klox Sparkle appcast dashboard. Not a claim that consumer Klox ships an appcast. Not a claim that every partner ships a tap.
SurfaceJobLieFailure
Sparkle appcast (Ruby)Name token, url, old Sparkle feedThe appcast is the installerold token, old appcast url, wrong KB
PKG packerOther wrapper; other essayThe Ruby is the product archiveWrong macro, old receipts blamed on brew
DMG disk imageVolume the user mounts; other essayThe appcast is the Finder windowWrong macro, old volume blamed on tap
NotarizationScan and ticket; other essayThe scan is the appcast XMLWrong macro, Friday status
WireGuard tunnelHandshake; other essayA old SUFeedURL is a protocol missWrong macro, Connect lecture
/download MacConsumer Mac artifact Klox shipsThis desk is the consumer buttonWrong bits, not the appcast
Cookie on klox.appSite cookiesThe installer is a cookieSee /cookie; neither is Sparkle

Sparkle appcast is the old appcast XML. It is not a PKG, a DMG, or notarization.

— KloxVPN operator notes

Cloudflare Learning: What is a VPN?

Wikipedia: Virtual private network

IETF RFC 8446 (TLS 1.3)

Sparkle documentation

Mullvad: VPN for macOS (competitor specimen)

Store vs tunnel

App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

When users mention Sparkle

If a subscriber cites `Sparkle` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.

Store reviewers compare screenshots to real behavior. Mislabelled `Sparkle` strings are an easy rejection reason.

What the tunnel still does

Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.

Keep marketing, engineering, and support in one thread when `Sparkle` changes. Silent renames cause refund spikes.

You inherit server capacity, protocol maintenance, and core app updates from Klox infrastructure. You own front-line support and brand promise.

Regardless of brand paint, the client wraps traffic the same way: encrypted tunnel to your chosen server, DNS through the tunnel when configured, kill switch optional per platform.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Device cap

five devices per subscription is still enforced. Your pricing page should say so clearly.

Keep marketing, engineering, and support in one thread when `Sparkle` changes. Silent renames cause refund spikes.

Protocol choice

WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.

Run quarterly content audits on blog posts that mention `Sparkle` so partners do not contradict each other.

Branding checklist around Sparkle

Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Run quarterly content audits on blog posts that mention `Sparkle` so partners do not contradict each other.

If you rebrand, update every surface in one release when possible. Half-old names confuse users and app review.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Five devices on one KloxVPN plan
One account, five devices online at the same time.

Comments and CMS plugins

Some partners embed comment systems or CMS tools named `Sparkle`. That is website plumbing, not VPN configuration.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

2FA and admin panels

Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.

Reseller and white-label paths differ; pick one story on your homepage.

Support scripts that work

Escalate tunnel failures to infrastructure. Escalate storefront or installer naming to your release manager.

When unsure, link to /white-label instead of improvising specs in sales email.

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.

Run quarterly content audits on blog posts that mention `Sparkle` so partners do not contradict each other.

Refund policy

Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.

Store reviewers compare screenshots to real behavior. Mislabelled `Sparkle` strings are an easy rejection reason.

Launch week

Use launch checklist so `Sparkle` questions do not land on day one.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

What not to promise

No invented "Sparkle 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.

White-label is speed to market with a proven tunnel — not a license to invent physics.

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

Store reviewers compare screenshots to real behavior. Mislabelled `Sparkle` strings are an easy rejection reason.

Competitor comparisons

Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

Next step

Talk to sales via /white-label when you are ready to ship glass with your logo.

When unsure, link to /white-label instead of improvising specs in sales email.

Release checklist when Sparkle appears in builds

Archive old screenshots so marketing does not resurrect retired strings.

Run smoke tests: install, connect WireGuard, switch to OpenVPN, sign out, reinstall.

Update release notes if `Sparkle` is user-visible.

Reseller and white-label paths differ; pick one story on your homepage.

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

App review

Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Versioning

Tag builds that change `Sparkle` so support can map tickets to releases.

Store reviewers compare screenshots to real behavior. Mislabelled `Sparkle` strings are an easy rejection reason.

Partner FAQ snippets

Q: Do we operate servers? A: You brand and support; infrastructure follows your Klox agreement.

Q: Where is pricing? A: You set retail; reference $2.83/month on the yearly plan only if you mirror consumer tiers.

Q: Can we sell unlimited devices? A: Only if your commercial plan allows it; default is five devices.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Reseller and white-label paths differ; pick one story on your homepage.

Sales

Point enterprise buyers to /trust-center for published policies.

Keep marketing, engineering, and support in one thread when `Sparkle` changes. Silent renames cause refund spikes.

Reseller

Reseller program if you want volume without full white-label.

Run quarterly content audits on blog posts that mention `Sparkle` so partners do not contradict each other.

Long-term maintenance

Keep a single internal doc listing approved product claims.

Collect user feedback on confusing labels — rename in the next release rather than debating in chat.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Document which version removed or renamed `Sparkle` so SEO pages like this one stay truthful.

Run quarterly content audits on blog posts that mention `Sparkle` so partners do not contradict each other.

Branding

Branding checklist

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Contact

White-label for partnership questions.

Reseller and white-label paths differ; pick one story on your homepage.

Key Takeaways

White-label · Launch checklist · Download reference app

Document naming decisions, split support tickets, and do not promise features the core app does not have.

Key takeaway: Sparkle 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.

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-label

Frequently Asked Questions

No. Partner apps still use WireGuard, OpenVPN, OpenConnect, and Shadowsocks.

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.