Sell TAK under your own brand

Who this is built for

Value-added resellers, managed service providers and systems integrators who already own the customer relationship and want TAK inside what they sell rather than beside it. If you are quoting a project and situational awareness is one line on it, a third-party login page in the middle of your delivery is a seam the customer can see — and a vendor they can go around next year.

The test is simple: do you want to be the one your customer calls? If yes, this is the arrangement. If you would rather hand them to us and stay out of the support path, say so on the contact page — that is a different and much smaller commitment, and there is no sense pretending otherwise.

What the white box actually changes

More than a logo swap. The console is themed rather than badged, and the parts that usually give a white label away are covered:

• The whole console palette, not an accent colour — surfaces, navigation, tables and type, so nothing reads as somebody else’s product wearing your logo
• Your logo, your favicon and your browser tab title
• A hostname you own, so the address bar is yours from the first click
• Your brand name in the mail the system sends — subjects, invitations and password resets. Worth auditing the exact wording with us before you launch, because an email body is the easiest place in any product for a vendor name to survive a rebrand
• Your support address, your terms of service and your privacy policy
• Visitors who reach your root URL without a session go to your site rather than a login screen

Who owns the customer

You do, and the platform is configured to make that true rather than merely say it. Sign-up can be closed entirely, so an account exists only because you created it. In-console billing can be switched off, so your customers never see a price that is not yours — you bill them on your terms, and we bill you.

What that arrangement costs is scoped per partnership rather than published on this page. The shape differs too much between an integrator adding TAK to a handful of large projects and a service provider putting it in front of a few hundred small accounts for a list price to mean anything honest.

What stays ours

The operations, and that is the actual point of the arrangement. Scaling, updates, patching, certificate issuance and rotation, and uptime remain our responsibility.

The failure mode for a reseller is accidentally becoming a hosting company. You put your name on something, and the call at two in the morning arrives with it. Here the brand is yours and the pager is ours, and that does not change with a private server either — that gives your customer a dedicated instance in a region they name, still operated by us. If you want to own the infrastructure as well, you want to run TAK Server yourself, which is not something we sell.

What cannot carry your brand

The client apps. ATAK on Android, iTAK on iOS and WinTAK on Windows come from tak.gov, and they are not ours to rebrand. Your customer installs the standard clients and they look like themselves.

Everything on the server side is yours: the console, the hostname, the enrolment packages, the email. Worth putting in your own proposal in those words, because a customer who was told ‘fully branded’ and then sees an ATAK splash screen will ask you about it, and the answer is much better given in advance.

Not reselling? The same box serves an internal brand

Agencies use it too, for reasons that have nothing to do with margin. A console that reads as an internal system gets adopted differently from one that reads as a vendor’s product, particularly by operators who did not choose it. The mechanics are identical; only the commercial half of the conversation is missing.

How a partnership gets scoped

Tell us what you sell and who you sell it to. What we need to establish is the shape of the arrangement: roughly how many end customers, whether they are separate organizations or one, whether you want billing in your hands or ours, and what support you intend to own.

Then the part worth settling before anything is signed — where your support stops and ours starts. Your customers will call you, because your name is on it. What escalates, how fast we answer and what you handle yourself is the substance of the agreement, not an appendix to it. Start that on the contact page.