Brand the app; the tunnel stays the same.

White-Label VPN and Oban Web

Oban Web 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-12-04
White-Label VPN and Oban Web
Brand the app; the tunnel stays the same.

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

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

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.

Looking for a reliable VPN?

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

View Plans

What Oban Web is in your stack

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

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

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

Partners grep builds, store listings, and support macros for strings like `Oban Web`. 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.

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

    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.

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

When users mention Oban Web

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

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

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.

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.

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

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

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

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

Protocol choice

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

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

Branding checklist around Oban Web

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

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

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

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 `Oban Web` so SEO pages like this one stay truthful.

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

oban web 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 `Oban Web`. That is website plumbing, not VPN configuration.

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

2FA and admin panels

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

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

Support scripts that work

Document which version removed or renamed `Oban Web` 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.

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

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

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.

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

Launch week

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

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

What not to promise

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

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

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

No invented "Oban Web encryption." No secret city counts. No SOC 2 badge unless you actually hold one.

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

Competitor comparisons

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

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

Next step

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

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

Release checklist when Oban Web appears in builds

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

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

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

Confirm billing pages still mention five devices and refund policy accurately.

App review

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

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

Versioning

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

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

Partner FAQ snippets

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

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

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

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

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.

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

Reseller

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

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

Long-term maintenance

Train new support staff on tunnel vs branding tickets in the first week.

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

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

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

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

Branding

Branding checklist

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

Contact

White-label for partnership questions.

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

Key Takeaways

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

Key takeaway: Oban Web 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

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.