Servers

A server is a machine managed by Serversinc. It supplies the CPU, memory, disk, networking, and Docker runtime used by your applications and database instances.

You can connect a server you already control or ask Serversinc to provision one through a supported cloud provider.

Add a server

Connect an existing server

Use this path when the machine already exists. Serversinc gives you a one-time connection command to run over SSH. The command registers the server, prepares its Docker environment, and starts the management connection.

Before connecting a production machine, check the supported operating system, required privileges, network access, and any workloads already using Docker or common web ports.

Provision a new server

Use this path when you want Serversinc to create the machine. Add a provider key for your organisation, then choose the provider, region, size, server name, and environment.

Provisioning has two parts: the cloud provider creates the machine, then Serversinc prepares it for applications. The server’s status shows which stage it has reached.

Understand server status

A connected server reports regular snapshots to Serversinc. These snapshots drive the overview, metrics, Docker resources, and health checks shown in the dashboard.

A stale or offline server does not always mean the machine itself has stopped. It means Serversinc has not received a recent report. Check network access and the management connection before restarting workloads.

Monitor resources

The server detail page shows host-level CPU, memory, disk, and network data. Use these metrics to answer questions about the machine as a whole. Application logs and container state belong to the application and container views instead.

Metrics are historical reports, not a replacement for request-level application monitoring.

Check and improve server health

Serversinc checks common host settings, including:

• Direct root login over SSH
• Automatic package updates
• Fail2Ban
• Time synchronisation
• Firewall status and open ports

Supported checks can be changed from the dashboard. Some checks are informational until a remediation action is available. An unknown check has not reported enough information to be changed safely.

Run commands

Run an ad-hoc shell command from the server’s Commands tab. Serversinc records the actor, status, exit code, output, and errors in command history.

Commands that look destructive require an extra confirmation. That check is a guardrail, not a sandbox. The command still runs on the server with the privileges used by the management service.

For recurring work, create an interval, hourly, daily, or weekly schedule. Scheduled runs appear in the same command history as manual runs.

Manage server settings

Server settings cover:

• Display name and environment
• Provider and provider-side server ID
• Region or datacenter metadata
• Reported IPv4 and IPv6 addresses
• Backup retention by age and count

Disconnecting a server removes its Serversinc record and associated application and container records. Read the deletion summary in the dashboard before confirming. Do not assume disconnecting a server destroys the machine at its cloud provider.

When something stops reporting

Start with the boundary between the machine and Serversinc:

1. Confirm that the server is running and reachable.
2. Check outbound connectivity from the server.
3. Confirm that Docker and the management container are running.
4. Compare the last reported state, metrics, and command history.
5. Collect the relevant logs before reconnecting or removing anything.

The connection is designed to update itself. Manual agent installation is not the normal customer workflow.

Next steps

• Applications: deploy a workload to the server.
• Databases and backups: provision a database or protect existing data.
• Automation: manage servers from the CLI, API, or MCP server.