White-label VPN partners often ask how Metabase 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.
Metabase may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Metabase mode" inside the tunnel.
Looking for a reliable VPN?
KloxVPN — from $2.83/month. Apps for every device.
What Metabase is in your stack
Keep marketing, engineering, and support in one thread when `Metabase` changes. Silent renames cause refund spikes.
Document which version removed or renamed `Metabase` so SEO pages like this one stay truthful.
It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.
Reseller and white-label paths differ; pick one story on your homepage.
Document decisions in your runbook so marketing and engineering do not talk past each other.
- 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.
When unsure, link to /white-label instead of improvising specs in sales email.
When users mention Metabase
If a subscriber cites `Metabase` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.
Document which version removed or renamed `Metabase` so SEO pages like this one stay truthful.
What the tunnel still does
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.
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 `Metabase` so SEO pages like this one stay truthful.
You inherit server capacity, protocol maintenance, and core app updates from Klox infrastructure. You own front-line support and brand promise.
Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.
| Crop | Desk | Next move |
|---|---|---|
| Metabase UI 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.
Run quarterly content audits on blog posts that mention `Metabase` so partners do not contradict each other.
Protocol choice
WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.
Keep marketing, engineering, and support in one thread when `Metabase` changes. Silent renames cause refund spikes.
Branding checklist around Metabase
If you rebrand, update every surface in one release when possible. Half-old names confuse users and app review.
Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.
Keep marketing, engineering, and support in one thread when `Metabase` changes. Silent renames cause refund spikes.
Run quarterly content audits on blog posts that mention `Metabase` so partners do not contradict each other.
When unsure, link to /white-label instead of improvising specs in sales email.
metabase ui 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 `Metabase`. That is website plumbing, not VPN configuration.
Reseller and white-label paths differ; pick one story on your homepage.
2FA and admin panels
Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Support scripts that work
Reseller and white-label paths differ; pick one story on your homepage.
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.
Run quarterly content audits on blog posts that mention `Metabase` so partners do not contradict each other.
Ask: OS, app version, protocol, and whether Connect ever worked on another network. Only then dig into build strings like `Metabase`.
Refund policy
Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.
Document which version removed or renamed `Metabase` so SEO pages like this one stay truthful.
Launch week
Use launch checklist so `Metabase` questions do not land on day one.
When unsure, link to /white-label instead of improvising specs in sales email.
What not to promise
When unsure, link to /white-label instead of improvising specs in sales email.
No invented "Metabase encryption." No secret city counts. No SOC 2 badge unless you actually hold one.
White-label is speed to market with a proven tunnel — not a license to invent physics.
Store reviewers compare screenshots to real behavior. Mislabelled `Metabase` 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.
Competitor comparisons
Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.
Store reviewers compare screenshots to real behavior. Mislabelled `Metabase` strings are an easy rejection reason.
Next step
Talk to sales via /white-label when you are ready to ship glass with your logo.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Release checklist when Metabase appears in builds
Confirm billing pages still mention five devices and refund policy accurately.
Reseller and white-label paths differ; pick one story on your homepage.
Update release notes if `Metabase` is user-visible.
Archive old screenshots so marketing does not resurrect retired strings.
Store reviewers compare screenshots to real behavior. Mislabelled `Metabase` strings are an easy rejection reason.
App review
Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.
When unsure, link to /white-label instead of improvising specs in sales email.
Versioning
Tag builds that change `Metabase` so support can map tickets to releases.
Document which version removed or renamed `Metabase` so SEO pages like this one stay truthful.
Partner FAQ snippets
Q: Does `Metabase` change encryption? A: No. WireGuard, OpenVPN, OpenConnect, and Shadowsocks still powers the tunnel.
Q: Where is pricing? A: You set retail; reference $2.83/month on the yearly plan only if you mirror consumer tiers.
Run quarterly content audits on blog posts that mention `Metabase` so partners do not contradict each other.
Q: Can we sell unlimited devices? A: Only if your commercial plan allows it; default is five devices.
Document which version removed or renamed `Metabase` so SEO pages like this one stay truthful.
Sales
Point enterprise buyers to /trust-center for published policies.
Run quarterly content audits on blog posts that mention `Metabase` so partners do not contradict each other.
Reseller
Reseller program if you want volume without full white-label.
Keep marketing, engineering, and support in one thread when `Metabase` changes. Silent renames cause refund spikes.
Long-term maintenance
Train new support staff on tunnel vs branding tickets in the first week.
Keep a single internal doc listing approved product claims.
When unsure, link to /white-label instead of improvising specs in sales email.
Keep marketing, engineering, and support in one thread when `Metabase` changes. Silent renames cause refund spikes.
Store reviewers compare screenshots to real behavior. Mislabelled `Metabase` strings are an easy rejection reason.
Branding
Reseller and white-label paths differ; pick one story on your homepage.
Contact
White-label for partnership questions.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Key Takeaways
Document naming decisions, split support tickets, and do not promise features the core app does not have.
Key takeaway: Metabase 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.