Dedicated regional node
Each subscription receives a private virtual server in the selected region, isolated from other customer workloads.
Dedicated private NTRIP infrastructure
Your own CORS.
Online in minutes.
Deploy a private NTRIP caster close to your project, with 31 core compute locations across five geographic areas. Connect GNSS base stations, create secure rover credentials, and manage RTK correction streams from one dashboard.
✓ 31 core region locations
✓ NTRIP base & rover credentials
✓ Pay with TechnoGIS Points
✓ Daily RINEX Logger included
Private CORS Node
Online
Regional GNSS correction delivery
GNSS BaseRTCM source
RTCM
Private CasterDedicated region
NTRIP
RTK RoversSurvey · drone · machine
31 locationsChoose a nearby core region
Private accessPer-user credentials
ScalableUpgrade without downgrade
Surveying
Drones
Construction
Infrastructure
Agriculture
Built for operational RTK
Private correction delivery without managing servers
Private CORS provides the infrastructure layer between your GNSS base and field devices, while TechnoGIS manages provisioning, monitoring, and service lifecycle.
Base, operator & rover access
Create base, operator, and rover credentials with clear package limits for base stations, operator accounts, client accounts, and simultaneous rover connections.
Live connection visibility
Monitor base availability, rover sessions, mountpoint status, and server health from the control dashboard.
Broad global region choice
Select from 31 Private CORS Global Cloud locations across North America, Europe, Asia, South America, and Oceania, subject to live capacity.
Automatic RINEX Logger
Active base-station RTCM streams are logged automatically and finalized into daily RINEX archives. Archive retention is included according to your plan.
One TechnoGIS wallet
Activate, renew, and upgrade with the same TechnoGIS Points used across participating TechnoGIS cloud services.
Global deployment footprint
Place the caster closer to your GNSS operation
Private CORS can be provisioned across 31 TechnoGIS-managed cloud locations. Select the country and city that best fits your base stations and rover teams.
31Global cloud locations
5Geographic areas
LiveAvailability checked at order
Region availability can change based on current cloud capacity. The selected location is verified automatically before points are captured.
Check availability during provisioning →
Simple deployment
From checkout to correction stream
The control plane provisions the regional server, installs the caster node, applies credentials, and gives you a stable hostname for GNSS configuration.
Choose a package
Select base-station capacity, NTRIP client accounts, concurrent rovers, subscription term, and renewal mode.
Select a region
Search all available deployment locations by country, city, or region code, then select the most suitable location for your operation.
Connect the base
Use the generated host, mountpoint, base username, and password to publish RTCM corrections.
Operate & archive
Create rover credentials while Private CORS continuously logs active base streams and prepares the previous UTC day as a downloadable RINEX archive.
Clear package limits
Flexible monthly billing
Choose the Private CORS capacity you need
Each plan clearly defines the number of base stations, operator accounts, saved NTRIP client accounts, and rover connections that may be active at the same time. Prices are shown primarily in US dollars and can be paid with the equivalent TechnoGIS Points, where 100 points = US$1.
Automatic RINEX Logger — included
Continuous RTCM logging and automatic daily RINEX generation are included for active base stations. RINEX archive retention is 3 months on Starter, 6 months on Team, and 12 months on Business and Enterprise.
IncludedNo per-base add-on fee
Why private infrastructure
Control your own correction distribution
A private caster is designed for organizations that already operate GNSS bases and need controlled, scalable delivery to multiple rover devices.
| Capability | Private CORS | Public/community caster | Self-managed VPS |
|---|---|---|---|
| Dedicated customer node | Included | Usually shared | Possible |
| Base and rover user management | Dashboard managed | Varies | Manual setup |
| Regional deployment choice | 31 global cloud locations | Fixed infrastructure | Manual selection |
| Provisioning and lifecycle automation | Included | Not customer-controlled | You maintain it |
| Capacity limits | Base stations, operators, client accounts, and concurrent rovers | Varies by service | Manually enforced |
| Package upgrade | Control-plane upgrade | Provider dependent | Manual migration |
| Automatic daily RINEX logger | Included with plan-based retention | Varies by service | Manual setup |
| TechnoGIS Points billing | Included | No | No |
A TechnoGIS product
Engineered by TechnoGIS GmbH
TechnoGIS develops integrated geospatial systems combining GNSS, LiDAR, remote sensing, WebGIS, and spatial intelligence for industrial and infrastructure applications.
Visit TechnoGISGNSSPrecision survey technology
Cloud GISSpatial platforms and workflows
Remote SensingEarth observation and analytics
DüsseldorfTechnoGIS GmbH · Germany
Frequently asked questions
Before you deploy
Is Private CORS an RTK correction network?
Private CORS is the delivery infrastructure for corrections produced by your connected base station. The caster receives the base stream and distributes it to authorized NTRIP clients. Network RTK functions such as VRS require a separate processing engine and are not implied by the standard packages.
What counts toward the package limit?
Base stations and NTRIP client accounts are saved configuration limits. Concurrent rovers means active correction sessions at the same time. One username used by two connected rover devices consumes one client account and two concurrent-rover slots.
What equipment can connect?
GNSS receivers, survey controllers, drones, machines, and software that support compatible NTRIP and RTCM workflows can generally connect. Confirm the required NTRIP version, correction format, port, and device network support before deployment.
Why choose a nearby region?
NTRIP depends on an internet connection. A geographically suitable region can reduce routing distance and improve operational responsiveness, although total latency also depends on the base, rover, mobile network, and wider internet path.
Are all 31 regions always available?
The sales page lists 31 Private CORS Global Cloud locations. Actual provisioning depends on current capacity, package type, and regional pricing. Private CORS checks the selected location again before creating the server.
Can a package be upgraded?
Yes. Upgrades are supported. When the target package uses the same virtual server size, limits can be updated in place. When more compute is required, the provisioning service performs a server resize or managed migration. Package downgrades are not offered in the current design.
How do renewals work?
Choose manual or automatic renewal. Automatic renewal deducts the required TechnoGIS Points when the next term begins. When the balance is insufficient, the service follows the configured grace, suspension, and termination policy.
How many operator accounts are included?
Starter includes 1 operator, Team 3 operators, Business 10 operators, and Enterprise 25 operators. Operator limits are separate from NTRIP client and concurrent rover limits.
Is RINEX Logger an additional paid add-on?
No. Automatic RTCM stream logging and daily RINEX generation are included for active base stations within the capacity of your Private CORS plan.
How long are RINEX archives retained?
Starter includes 3 months of RINEX archive retention, Team includes 6 months, and Business and Enterprise include 12 months. Logging continues while the base and caster are active; the retention period controls how long historical RINEX archives remain available.
Does the logger require the receiver to upload RINEX files?
No. The GNSS base continues publishing its normal RTCM stream to the Private CORS mountpoint. Private CORS logs that stream and generates the daily RINEX archive on the server after the UTC day closes.
Deploy your private caster near the project.
Select a package, choose a region, and receive the first base and rover credentials after provisioning.