Brand the app; the tunnel stays the same.

White-Label VPN and Sphinx Book (CMS installs)

Sphinx Book 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 2022-09-28Updated 2023-12-03
White-Label VPN and Sphinx Book (CMS installs)
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.

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

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

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.

Looking for a reliable VPN?

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

View Plans

What Sphinx Book is in your stack

Partners grep builds, store listings, and support macros for strings like `Sphinx Book`. That is a packaging question: does the name still ship, should it be renamed, or removed?

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

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

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

Document decisions in your runbook so marketing and engineering do not talk past each other.

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

    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.

Store vs tunnel

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

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

When users mention Sphinx Book

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

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

What the tunnel still does

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

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.

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.

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

Packaging desk versus tunnel desk for Sphinx Book CMS Again UI
CropDeskNext move
Sphinx Book CMS Again UI in a listing or helperPackaging / white-labelStrip, rename, or leave
Handshake / ConnectingConsumer appSwap protocol once
Store metadata lagConsole + binaryEdit listing after rebuild
Cafe destinations visibleVPN tunnelConnect. Not a string rename

Device cap

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

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

Protocol choice

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

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

Branding checklist around Sphinx Book

Confirm `Sphinx Book` still appears where you expect: installer metadata, about screen, support templates, and marketing site.

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

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

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

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

White-label branding versus the VPN tunnel
Your logo is packaging. The tunnel is still WireGuard, OpenVPN, OpenConnect, and Shadowsocks.

Strip, rename, or leave. Those are the three moves. Inventing a dashboard is how you lie on a store listing.

— KloxVPN white-label notes

Comments and CMS plugins

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

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

2FA and admin panels

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

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

Support scripts that work

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

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 `Sphinx Book` changes. Silent renames cause refund spikes.

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

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

Refund policy

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

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

Launch week

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

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

What not to promise

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

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

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.

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

Competitor comparisons

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

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

Next step

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

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

Release checklist when Sphinx Book appears in builds

Search your repo and CI artifacts for `Sphinx Book` before every store submission.

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

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 `Sphinx Book` so partners do not contradict each other.

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

App review

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

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

Versioning

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

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

Partner FAQ snippets

Q: Refunds? A: Honor 7-day money-back on your first purchase or publish your own policy clearly.

Q: Does `Sphinx Book` change encryption? A: No. WireGuard, OpenVPN, OpenConnect, and Shadowsocks still powers the tunnel.

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.

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

Sales

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

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

Reseller

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

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

Long-term maintenance

Schedule quarterly reviews of strings like `Sphinx Book` across website, app, and support macros.

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.

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

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

Branding

Branding checklist

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

Contact

White-label for partnership questions.

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

Key Takeaways

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

White-label · Launch checklist · Download reference app

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

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.