!
One password for the whole company
Changing a shared password interrupts every employee and device at the same time.
For surveying companies
RTK corrections for surveying and cadastral field crews
Deliver corrections from your own base stations to multiple rover crews, issue separate credentials, and manage connections from one control panel.
- Separate access for every rover
- Mountpoints organized by base and project
- One control panel for all field crews
Example architecture
Two bases, three crews, one control layer
North Base
RTCM
South Base
RTCM
YouCORS
Private NTRIP caster and access management
Crew 1 · 2 rovers
Crew 2 · 2 rovers
Crew 3 · 2 rovers
Every correction stream and rover has a clear assignment. An administrator can change one device without disrupting every other field crew.
Important: YouCORS delivers corrections from your base stations to your rovers and applications. It does not sell access to a third-party RTK network or generate corrections without a source.
When to change the setup
Shared credentials and manual configuration stop scaling with the team
As the number of bases, rovers, and projects grows, it becomes harder to know who is using each stream and how to change access safely.
!
One rover cannot be revoked
A lost device or former contractor can retain access through shared credentials.
!
Crews choose the wrong base
Unclear stream names increase the chance of selecting the wrong mountpoint in the field.
!
Projects become mixed
The same credentials are reused across clients, territories, and field crews.
!
No connection overview
Managers cannot see which rovers and crews are using the infrastructure right now.
!
Every change is manual
Moving a server or source turns into reconfiguring a large fleet of devices.
The operating model
From your base station to a specific rover
Build infrastructure around real bases, projects, crews, and devices instead of anonymous shared access.
- 1
Bases publish RTCM
Your own base stations send correction streams over the internet.
- 2
Streams are separated
Create a clearly named mountpoint for every base or project.
- 3
Rovers receive clients
Issue separate NTRIP credentials to every field device.
- 4
Crews receive access
Users and groups see only the streams required for their work.
- 5
Administrators stay in control
Manage infrastructure and connections from a single control panel.
Use cases
One infrastructure layer for different field operations
Organize access around your company structure, operating regions, and project timelines.
Permanent field crews
Assign rovers and correction streams to internal teams.
Temporary contractors
Issue separate credentials and revoke them when the job is complete.
Cadastral regions
Separate bases and mountpoints by the territory where work is performed.
Multiple client projects
Keep devices and credentials for different clients separate.
Backup base
Prepare an alternative source while the primary base is under maintenance.
Distributed offices
Manage connections for multiple branches from one place.
Operational control
Know who is connected, where they work, and which stream they use
Managed access reduces dependence on shared passwords and manual coordination between office and field teams.
Separate credentials
Changing one rover's access does not affect every other device.
Clear ownership
Connect each rover, employee, project, and correction stream.
Targeted revocation
Disable a specific contractor or device without a global reset.
Consistent naming
Use one naming convention for bases and mountpoints.
Scalable operations
Add crews without deploying a separate caster for every team.
Fewer manual requests
Reduce scattered settings and repeated support work.
Example configuration
3 bases, 12 rovers, and 4 field crews
Each base receives its own mountpoint, every rover receives separate credentials, and crews are grouped by territory or project.
3
company-owned bases
12
GNSS rovers
4
field crews
| Project | Bases | Rovers | Groups | Backup plan |
|---|---|---|---|---|
| Northern region | 2 | 8 | 3 | Backup base |
| Southern region | 1 | 4 | 1 | Alternative source |
This is an architecture example, not a universal sizing rule. The final setup depends on operating geography, equipment, RTCM format, and redundancy requirements.
Phased rollout
Start with one base and one test rover
Validate the complete correction path in a pilot before moving every field crew.
Step 1
List your current bases, rovers, crews, and projects.
Step 2
Select an appropriate server region.
Step 3
Create the caster and clearly named mountpoints.
Step 4
Connect one test base station.
Step 5
Issue credentials to one test rover.
Step 6
Validate the complete workflow in the field.
Step 7
Move the remaining crews in controlled stages.
Frequently asked questions
Before launching your RTK infrastructure
Does YouCORS provide ready-to-use RTK corrections?
No. YouCORS deploys and manages NTRIP infrastructure that delivers streams from your own base stations or another configured correction source.
Can multiple rovers connect to one base?
Yes. One base can publish a stream to a mountpoint and multiple authorized NTRIP clients can consume it concurrently within the selected server configuration.
Can we use GNSS receivers from different manufacturers?
Yes, when the equipment supports compatible NTRIP versions and RTCM messages. Test one base and one rover from each configuration before a large rollout.
How do we give temporary access to a contractor?
Create a separate client for the device or contractor and set an expiration date. It can be revoked without changing every other rover.
Do we need a separate caster for every project?
Not necessarily. Projects can be separated through mountpoints, clients, users, and groups within managed infrastructure.
What if our crews work in different regions?
Map the locations of bases and users first, then select a server region and stream structure. Remote areas may require additional base stations or separate infrastructure decisions.
Discuss your configuration
Plan a setup around your bases, crews, and rovers
Share the size of your current infrastructure. We will receive a prepared email with the information needed to discuss the setup.
Already know the architecture?
Create an account and start a pilot with one base station.
Continue to registration