Projects, components and infrastructure

A project groups your application and its supporting components. An environment is one Kamal destination or service deployment. A component is a watched Kamal role or accessory, not a server or an individual container instance.

See what Upstate discovered

Open Overview, Projects and Infrastructure. The observer reports Docker workloads it can recognize. Some Kamal services may appear as Discovered, not watched until you connect or explicitly watch them.

Watched components belong to a connected project, or are shared accessories linked to one. They count toward component limits and participate in monitoring.
Discovered components are visible for inspection but do not count toward limits, open alerts or generate notifications until watched.
Running instances are the individual containers of a component. One component with several instances counts only once toward the plan.
The Upstate observer itself, kamal-proxy and unclassified containers are infrastructure context, not billable components.

Use Watch this to adopt an appropriate discovered service or link a standalone accessory to a project. Owners/admins can rename projects, move environments and manage shared accessory associations. Review target changes carefully; different projects may share the same server or database.

Check coverage rather than assuming protection

Open Coverage on the Projects page to review gaps in deployment verification, current host reporting, public HTTP monitoring, deploy notifications, backup check-ins and application health reporting. Overview can link to the Projects coverage section when gaps exist; it does not contain the coverage controls itself. Each dimension may be protected, not configured, stale, unknown or unsupported.

An owner/admin can mark a gap Not needed when it is intentionally accepted. That acknowledgement changes how gaps are presented; it does not create evidence that monitoring is working. Restore it if circumstances change. A configured check is different from a proven latest successful check.

Inspect servers and supporting services

Infrastructure groups observed servers and their attached projects and shared services. Server pages show what the observer last reported, including status and capacity evidence. Timestamps matter: a stale report is a visibility gap.

Where available, Upstate infers provider or region from limited cloud metadata, IP ownership or DNS hints. Those are best-effort labels, not verified cloud bills. Owners/admins can override provider, region or plan and enter monthly cost manually. Cost summaries include only the resources you supplied a cost for; missing prices are never guessed.

You can also record external resources for databases or services that do not run on your observed hosts. These are manual inventory rows with optional provider, cost, notes and project links. A recorded resource is not automatically monitored, and external resources do not count as Kamal components.

Retire resources deliberately

Retiring a project, environment or server stops active watching and alerts for the retired subject while preserving eligible history. This is different from deleting a Docker container or shutting down a live server; Upstate does not do either. Reconnecting or restoring may require fresh credentials and observer evidence.

For detailed runtime health, see Monitoring; for configuration confidence, see Production audit.