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.
Pkgsrc may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Pkgsrc 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.
White-label VPN partners often ask how Pkgsrc 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.
What Pkgsrc is in your stack
Partners grep builds, store listings, and support macros for strings like `Pkgsrc`. 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.
Document decisions in your runbook so marketing and engineering do not talk past each other.
Run quarterly content audits on blog posts that mention `Pkgsrc` so partners do not contradict each other.
Keep marketing, engineering, and support in one thread when `Pkgsrc` changes. Silent renames cause refund spikes.
- 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
| Surface | Job | Lie | Failure |
|---|---|---|---|
| pkgsrc pkgsrc Makefile (Tcl) | Name old, homepage, old pkg_info | The pkgsrc Makefile is the installer | old name, old master_sites, wrong KB |
| Homebrew cask (Ruby) | Other catalog; other essay | The pkgsrc Makefile is a cask | Wrong macro, old brew blamed on port |
| PKG packer | Other wrapper; other essay | The Tcl is the product archive | Wrong macro, old receipts blamed on pkgsrc |
| DMG disk image | Volume the user mounts; other essay | The pkgsrc Makefile is the Finder window | Wrong macro, old volume blamed on ports tree |
| Notarization | Scan and ticket; other essay | The scan is the pkgsrc Makefile | Wrong macro, Friday status |
| /download Mac | Consumer Mac artifact Klox ships | This desk is the consumer button | Wrong bits, not pkgin |
| Cookie on klox.app | Site cookies | The installer is a cookie | See /cookie; neither is pkgsrc |
pkgsrc old is the pkgsrc Makefile. It is not a Homebrew cask, a PKG, a DMG, or notarization.
— KloxVPN operator notes
Cloudflare Learning: What is a VPN?
Store vs tunnel
App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.
Document which version removed or renamed `Pkgsrc` so SEO pages like this one stay truthful.
When users mention Pkgsrc
If a subscriber cites `Pkgsrc` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.
When unsure, link to /white-label instead of improvising specs in sales email.
What the tunnel still does
Reseller and white-label paths differ; pick one story on your homepage.
Keep marketing, engineering, and support in one thread when `Pkgsrc` changes. Silent renames cause refund spikes.
Store reviewers compare screenshots to real behavior. Mislabelled `Pkgsrc` 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.
Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.
Device cap
five devices per subscription is still enforced. Your pricing page should say so clearly.
Reseller and white-label paths differ; pick one story on your homepage.
Protocol choice
WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Branding checklist around Pkgsrc
Confirm `Pkgsrc` still appears where you expect: installer metadata, about screen, support templates, and marketing site.
Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.
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.
Run quarterly content audits on blog posts that mention `Pkgsrc` so partners do not contradict each other.
Comments and CMS plugins
Some partners embed comment systems or CMS tools named `Pkgsrc`. That is website plumbing, not VPN configuration.
Run quarterly content audits on blog posts that mention `Pkgsrc` so partners do not contradict each other.
2FA and admin panels
Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.
Keep marketing, engineering, and support in one thread when `Pkgsrc` changes. Silent renames cause refund spikes.
Support scripts that work
Escalate tunnel failures to infrastructure. Escalate storefront or installer naming to your release manager.
Ask: OS, app version, protocol, and whether Connect ever worked on another network. Only then dig into build strings like `Pkgsrc`.
Keep marketing, engineering, and support in one thread when `Pkgsrc` changes. Silent renames cause refund spikes.
Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Refund policy
Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.
When unsure, link to /white-label instead of improvising specs in sales email.
Launch week
Use launch checklist so `Pkgsrc` questions do not land on day one.
Document which version removed or renamed `Pkgsrc` so SEO pages like this one stay truthful.
What not to promise
No invented "Pkgsrc encryption." No secret city counts. No SOC 2 badge unless you actually hold one.
Point enterprise buyers to /trust-center for what Klox publishes today, then add your own policies honestly.
White-label is speed to market with a proven tunnel — not a license to invent physics.
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 `Pkgsrc` so SEO pages like this one stay truthful.
Competitor comparisons
Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Next step
Talk to sales via /white-label when you are ready to ship glass with your logo.
Store reviewers compare screenshots to real behavior. Mislabelled `Pkgsrc` strings are an easy rejection reason.
Release checklist when Pkgsrc appears in builds
Search your repo and CI artifacts for `Pkgsrc` before every store submission.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
Run smoke tests: install, connect WireGuard, switch to OpenVPN, sign out, reinstall.
Archive old screenshots so marketing does not resurrect retired strings.
Run quarterly content audits on blog posts that mention `Pkgsrc` so partners do not contradict each other.
App review
Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.
Document which version removed or renamed `Pkgsrc` so SEO pages like this one stay truthful.
Versioning
Tag builds that change `Pkgsrc` so support can map tickets to releases.
When unsure, link to /white-label instead of improvising specs in sales email.
Partner FAQ snippets
Store reviewers compare screenshots to real behavior. Mislabelled `Pkgsrc` strings are an easy rejection reason.
Q: Where is pricing? A: You set retail; reference $2.83/month on the yearly plan only if you mirror consumer tiers.
Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.
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.
Sales
Point enterprise buyers to /trust-center for published policies.
Reseller and white-label paths differ; pick one story on your homepage.
Reseller
Reseller program if you want volume without full white-label.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
Long-term maintenance
Schedule quarterly reviews of strings like `Pkgsrc` across website, app, and support macros.
Keep a single internal doc listing approved product claims.
Collect user feedback on confusing labels — rename in the next release rather than debating in chat.
Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.
When Klox updates core apps, regression-test your branded build before wide release.
Branding
Run quarterly content audits on blog posts that mention `Pkgsrc` so partners do not contradict each other.
Contact
White-label for partnership questions.
Keep marketing, engineering, and support in one thread when `Pkgsrc` changes. Silent renames cause refund spikes.
Key Takeaways
Key takeaway: Pkgsrc 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.
Document naming decisions, split support tickets, and do not promise features the core app does not have.
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.