Serversinc Operator manual
The operator's manual.
Connect a server, ship an application, and know exactly what Serversinc changes along the way.
Serversinc manages applications on servers you control. Connect a server you already have or provision a new one, then deploy from a container image or GitHub repository.
First run
Section titled “First run”Add a server to your organisation.
Create an application on that server.
Set its environment, storage, and network.
Deploy and follow the reported state.
Operate it from the dashboard or tools.
Find the operation
Section titled “Find the operation”How the pieces fit together
Section titled “How the pieces fit together”Your organisation owns the resources and credentials managed through Serversinc. Each application belongs to one server. A deployment applies the application’s saved configuration and creates or replaces its current container.
Database instances also run on managed servers, but they have their own lifecycle. A database instance can contain multiple logical databases and users. Backups are written to an object storage provider configured for the organisation.
The dashboard, CLI, REST API, and MCP server all act on the same resources. Pick the interface that suits the job; the underlying model stays the same.
Before you add a server
Section titled “Before you add a server”For the quickest first deployment, have these ready:
- A Serversinc account with an active organisation subscription.
- An existing supported server you can access over SSH, or credentials for a supported cloud provider.
- A public container image to deploy. You can connect GitHub or a private registry later.
Start with Servers to choose how to add your first machine.