Teams, servers, applications, operations, and events.
ServerChirp uses a small set of resources consistently across the dashboard, API, assistant, and MCP. Understanding these relationships makes the rest of the product easier to navigate.
A team owns servers, applications, credentials, monitors, status pages, and billing. Members act through roles and can be limited to selected servers or applications. API tokens are team-wide but remain limited to their granted scopes.
A server is an Ubuntu machine connected to ServerChirp. It owns system services, users, firewall rules, databases, cron jobs, and one or more applications.
An application is a managed workload. Web applications, Docker containers, game servers, long-running console processes, and reverse proxies share common operations such as files, logs, environment, domains, metrics, and lifecycle controls where those operations make sense.
A mutation that may take time creates an operation. Operations retain attribution, progress, step output, and final state. Closing a browser does not cancel background work.
Examples include provisioning a server, installing an application, deploying a release, issuing a certificate, importing a database, and restoring a backup.
An event is a durable record of something operationally meaningful: a deployment completed, a server disconnected, a certificate is expiring, or an uptime monitor changed state. Events can fan out to alerts, notifications, and webhooks.
Dashboard updates arrive over authenticated realtime channels. Events are signals to refresh the canonical resource; the database remains the source of truth.
ServerChirp separates reusable credentials from public resource shapes. Secret values are encrypted at rest and are normally write-only after creation. API responses never expose agent tokens, provisioning credentials, registry secret keys, or private storage keys.
The dashboard shows friendly names, but automation uses stable resource IDs. You can copy an ID from a resource page or list resources through the REST API. An out-of-scope resource and a missing resource both return not found, preventing the API from revealing another team's inventory.
