Brand the app; the tunnel stays the same.

White-Label VPN and Makeself

Makeself 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 2023-05-07Updated 2024-12-08
White-Label VPN and Makeself
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.

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

White-label VPN partners often ask how Makeself 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 Makeself is in your stack

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

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

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

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

It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.

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.

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 Makeself

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

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

What the tunnel still does

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

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

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

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

Packaging desk versus tunnel desk for Makeself
CropDeskNext move
Makeself 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.

Keep marketing, engineering, and support in one thread when `Makeself` 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 `Makeself` so partners do not contradict each other.

Branding checklist around Makeself

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

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

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

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

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

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 `Makeself`. 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

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

Ask: OS, app version, protocol, and whether Connect ever worked on another network. Only then dig into build strings like `Makeself`.

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

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

Run quarterly content audits on blog posts that mention `Makeself` 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 `Makeself` strings are an easy rejection reason.

Launch week

Use launch checklist so `Makeself` 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

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

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

Point enterprise buyers to /trust-center for what Klox publishes today, then add your own policies honestly.

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

Store reviewers compare screenshots to real behavior. Mislabelled `Makeself` 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 `Makeself` 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 Makeself appears in builds

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

Archive old screenshots so marketing does not resurrect retired strings.

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

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

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

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 `Makeself` so support can map tickets to releases.

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

Partner FAQ snippets

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

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

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

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

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

Sales

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

Keep marketing, engineering, and support in one thread when `Makeself` 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 `Makeself` so partners do not contradict each other.

Long-term maintenance

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

When Klox updates core apps, regression-test your branded build before wide release.

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

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

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

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

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