Your operations team needs to find equipment and support staff across a sensitive site. Your security team needs to know where every positioning request goes, who can access it and where the result is stored.
Those requirements meet at the location service. If your policy requires location requests to stay inside infrastructure you control, on-premises geolocation gives you a local place to calculate them.
For defence facilities, law enforcement teams and critical infrastructure operators, location sovereignty starts with that control. The practical work is to define the data boundary, choose suitable positioning methods and verify the whole system against the site's requirements.
Start with the data boundary
A location request can carry information about the radio environment around a device, such as cellular identifiers or WiFi access point addresses. The service uses those observations to estimate a position. Repeated requests may also reveal information about activity over time.
A cloud service processes the request outside your own network. Whether that fits your requirements depends on your security policy, the service agreement and the controls in place. Sending a request to a cloud API does not make it public.
Some organisations require local processing regardless of a provider's privacy commitments. For those teams, the useful question is concrete: can the application get a location result without sending its positioning request to an external service?
Map that flow before selecting a deployment. Include the devices, application servers, location engine, logs, backups and any connected mapping or analytics services. A locally hosted calculation is one part of the boundary.
Resolve location requests on your own servers
The Combain On-Prem Location Server runs as a Docker container on your servers or in a private cloud. A local copy of the positioning database lets the server answer requests within your infrastructure.
An application sends observed radio identifiers to the local endpoint and receives a location estimate. Your team controls how that endpoint is reached and how results are used by the wider system.
Combain supports regional database licensing and online or offline updates. An isolated installation therefore needs an agreed process for bringing database updates into the environment.
Treat updates as part of operations from the outset. Decide who imports them, when they are applied and how your team checks the service afterwards. Record the software and data versions used during acceptance testing.

Conceptual illustration of a location request processed within a private environment.
Plan for the accuracy your team actually needs
A useful position has to support the decision at hand. Finding equipment in a broad outdoor area and locating a worker on a particular floor are different requirements. Define the acceptable uncertainty and update interval for each task before choosing the radio method.
Cell-ID positioning can help you locate devices when GNSS is unavailable. It needs usable cellular observations and reference data, and accuracy varies with the radio environment. Test coverage and accuracy at your site, including the places where you expect to need a fallback.
For indoor coverage, Combain AI Indoor Positioning uses WiFi and BLE observations with a Radio Environment Model. Start with the areas you need to cover, the devices your staff use and whether you need to identify a building, floor or room. That helps define the survey and local setup.
Test representative routes through the yard, entrances and indoor work areas. Include the difficult spots your staff encounter. Agree how the application should display an uncertain or missing location, then check that behaviour during the trial.

Conceptual illustration of outdoor and indoor radio positioning. Actual coverage depends on the site.
Separate offline calculation from live tracking
An offline location server can answer requests from its local database. A live tracking application still needs a permitted route for observations to reach the server and for results to reach the people who use them.
Define that route explicitly for an isolated network. Check whether devices report through the site's own connectivity, whether observations are imported for later analysis, and which components depend on external services.
This distinction matters when discussing GNSS fallback. A second positioning method can help calculate location when satellite positioning is unavailable. Your communications design determines when that estimate becomes visible to operations.
Assess private 5G as a separate positioning design
If your site has a private 5G network, discuss network-based positioning with the network team. The Combain 5G Positioning Engine calculates positions within a 5G Location Management Function (LMF).
You can use signal timing and cell measurements from your private 5G network to locate devices. The positioning method depends on what your network and devices support.
Choose methods against your network's measurements, base station placement and target accuracy. Confirm which components will be hosted locally and whether any roaming or database features require external connectivity. A private network alone does not establish the data boundary for every connected service.

Conceptual illustration of planning a positioning service for a private industrial network.
Give engineering and security teams a shared acceptance test
Bring a short list of requirements to the deployment discussion:
- Location task: which assets or staff need to be located, where, and how often?
- Data boundary: which requests, results, logs and backups must remain inside your environment?
- Device support: which radio observations can the selected devices collect and report?
- Performance: what accuracy, response time and request volume must the trial demonstrate?
- Operations: who owns updates, access, monitoring and recovery?
For application integration, compare your existing requests and responses with the Combain Location API documentation. Validate the fields and authentication your application uses against the chosen local deployment before changing its endpoint.
Then test the complete flow with your security and operations teams present. Local hosting gives you control over where positioning is processed. The acceptance test shows whether the proposed system meets the decisions, routes and operating conditions that matter at your site.
Talk to Combain about your on-premises geolocation requirements. Bring your data boundary, device types, coverage areas and accuracy targets so the discussion can focus on a deployment your team can evaluate.
Key Takeaways
What does location sovereignty mean for a sensitive site?
It means retaining control over where positioning requests are processed and how location data is accessed, stored and used. Define the boundary across the application, location engine, logs, backups and connected services.
How does the Combain On-Prem Location Server process requests?
It runs on your servers or in a private cloud as a Docker container and uses a local positioning database. Applications send radio observations to the local endpoint to receive a location estimate.
Can local positioning work without an internet connection?
The server can calculate locations from its local database in an offline deployment. You still need an approved update process and a permitted route for observations and results to move through the system.
Does cell-ID positioning guarantee an accurate GNSS fallback?
It can provide an alternative when GNSS is unavailable, if usable cellular observations and reference data exist. Accuracy and availability depend on conditions and should be tested against the site's requirements.
What should we check for indoor positioning?
Confirm device support for WiFi or BLE observations, the Radio Environment Model and survey requirements, local deployment options and the accuracy needed for each task. Test representative routes and difficult coverage areas.
How can private 5G support location sovereignty?
The Combain 5G Positioning Engine calculates device locations within the 5G core network. For private networks, positioning can be designed around your site's infrastructure, accuracy requirements and data residency policy.