A private TAK server, in the region you choose

What a private server is

A dedicated, single-tenant ArgusTAK instance, deployed into the cloud provider and region you name, and operated by us. Your own database, your own certificate authority, your own hostname. Nothing shared with another customer, which is usually the real question behind a request for ‘our own server’.

Everything on the platform page applies unchanged: automated certificates, federation, missions, streaming video, and the standard ATAK, iTAK and WinTAK clients from tak.gov. It is the same product, in a place you picked.

When the location is the requirement

Most teams do not need this, and we will say so. The shared service is cheaper, identical in function, and running already. But a class of requirement cannot be satisfied by any amount of reassurance about the shared service, because it is not about the software at all:

• Data residency — the data must remain in a named country or economic area
• Sovereignty or accreditation rules that name an approved provider or region
• A government cloud your organization is already required to use
• A contractual obligation to a customer of yours that flows down to your suppliers
• Isolation from other tenants as a stated condition rather than a preference

What it is not

It is not air-gapped, and we would rather lose the enquiry than blur that. We operate the instance, which means a management path exists. Any vendor who offers to run your server for you and calls the result air-gapped is selling you one or the other, and it is worth asking them which.

It is also not a deployment on your own hardware. We previously offered that and no longer do. If your policy genuinely requires equipment in a building you control, say so on the contact page and we will tell you plainly that this is not that — which is more use to you than a proposal that quietly is not either.

What stays ours

The operations, and that is the point rather than a caveat. Scaling, updates, patching, certificate issuance and rotation, backups, restore testing and uptime remain our responsibility on a private server exactly as they do on the shared service.

This is the trade that makes the offering worth having. Where the data lives and who keeps the server alive get conflated constantly, and a private server separates them: you take the jurisdiction, we keep the certificate authority.

Private and branded together

A private server and the white box are the same mechanism seen from two directions, so they combine. A reseller can put a dedicated instance in a region their customer requires, under their own name and hostname, with their own support address on it.

For an agency, the same combination produces a console that reads as an internal system and runs in the jurisdiction policy names — two arguments that usually have to be won separately.

How a deployment gets scoped

Tell us the shape of it: which provider and region, roughly how many users and devices, what the compliance regime is and who signs off on it, and what support you expect. That conversation is about operations and obligations more than about software, because the software part is settled.

Private servers sit in the Enterprise tier and are quoted per deployment. Start on the contact page. If the shared service would serve you better, that is what we will tell you — a private server you did not need is a cost you carry every month for a requirement nobody actually has.