Servers

Servers are the infrastructure that runs caster instances. The caster handles NTRIP access; the server provides the compute resources, IP address, and network ports.

Server list

The section shows the servers in the account. Open a server to view its state, connected instances, and technical metrics.

If there are no servers yet, the interface offers to create one. Before creating a server, check your plan limits. The number and size of servers you can run depends on the subscription.

Creating a server

The server form asks for:

• Name: a clear internal name;
• Region: the data center where the server will run;
• Size: CPU and memory.

Choose a region close to the base stations and users that care about latency. Choose the size based on expected load: number of casters, active sessions, and connection volume.

Server page

From the server page you can:

• view the current status;
• request a fresh status check;
• view server stats;
• see which instances are running on the server;
• check those instance statuses;
• reboot the server;
• rename or delete the server.

Status and stats actions ask the backend for up-to-date information. That matters because server state can change outside the page during installation, rebooting, or provider-side issues.

How servers relate to casters

A server is useful because it runs instances. One server can host more than one instance if it has enough resources and available ports.

When you create a caster instance, you choose a server and set the NTRIP and HTTP ports. That means the server must exist before the instance can be created.

Rebooting and deleting

Rebooting can help when a server is stuck, not responding, or needs system-level changes applied. Keep active connections in mind: bases and rovers may disconnect while the server restarts.

Delete a server only after checking the instances attached to it. If production casters are running there, deleting the server will stop those connections.