Brand the app; the tunnel stays the same.

White-Label VPN and Solid Queue (Follow-up)

Solid Queue 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-12-29Updated 2024-03-03
White-Label VPN and Solid Queue (Follow-up)
Brand the app; the tunnel stays the same.

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

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

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.

Looking for a reliable VPN?

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

View Plans

What Solid Queue is in your stack

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

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

Store reviewers compare screenshots to real behavior. Mislabelled `Solid Queue` 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.

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

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 Solid Queue

If a subscriber cites `Solid Queue` 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

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

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.

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

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 Solid Queue UI
CropDeskNext move
Solid Queue 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 `Solid Queue` 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 Solid Queue

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

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

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

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

Download, sign in, connect WireGuard, fall back to OpenVPN
Install from klox.app/download. WireGuard first. OpenVPN if UDP is blocked.

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 `Solid Queue`. 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 `Solid Queue` strings are an easy rejection reason.

Support scripts that work

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

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

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

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

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

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

Launch week

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

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

What not to promise

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

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.

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

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

Release checklist when Solid Queue appears in builds

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

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

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

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

Archive old screenshots so marketing does not resurrect retired strings.

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

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

Partner FAQ snippets

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

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

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

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

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.

Store reviewers compare screenshots to real behavior. Mislabelled `Solid Queue` 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 `Solid Queue` across website, app, and support macros.

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

Keep a single internal doc listing approved product claims.

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

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

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 `Solid Queue` strings are an easy rejection reason.

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: Solid Queue 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.