Accounts, access and plans

An Upstate account owns projects, monitored servers, check-ins, alert destinations and deployment history. An application repository's saved connection points to one account; your browser's currently selected account and the CLI's active account are not automatically the same.

Accounts and team access

Use your account settings to manage the account and its members or invitations, subject to the account's current plan and your role. Owners and admins can manage connected resources and notification destinations; regular members have narrower read access. A membership or coding-agent grant is not a host credential.

For CLI account selection:

upstate account list
upstate account use "My account"
upstate auth whoami

A repository's saved account mapping prevents another saved login from accidentally reading or sending to the wrong project. Use upstate connect --account NAME when setting up under a different saved account. CLI command reference explains local session and token storage.

Understand what is counted

Upstate bills by watched components, not by Docker container count or by server. A component is a Kamal app role or accessory; several running replicas count once. Shared accessories count once. Discovered but not watched containers, kamal-proxy, the Upstate observer and manually entered external resources do not count.

Current base allowances:

Projects themselves are unlimited. One Free account per owner can connect servers: if you create another account while already owning a Free account, the new account requires a Solo subscription before it can connect any servers. Your first Free account keeps its allowance, and accepting an invitation to someone else's account does not count as creating another owned Free account. Limits and checkout availability can change; your account's billing screen is the authoritative place to see your current plan and any configured purchase options. The account's recorded subscription, not a checkout return page alone, determines paid entitlement.

When usage exceeds a limit

Existing monitored resources are not immediately deleted or disconnected after a downgrade. New additions above the plan allowance are blocked. When watched components exceed the allowance, there is a 14-day grace period during which all existing components continue monitoring and alerting.

If the account remains over its component allowance after 14 days, only the newest components beyond the limit stop sending alerts, but app-health and request-metrics collection pauses across the entire account, including components that are within the allowance. Their app-health and request metrics no longer update; do not mistake previously recorded healthy evidence for a fresh measurement. Server observations, check-ins, TLS/domain checks and deployment receipts continue. Returning to the component allowance restores app-health and request-metrics collection and the suppressed component alerts. The affected components stay visible throughout; check your account's over-plan warning before relying on their evidence.

A paid subscription's payment status and its product allowance are related but different. Use the billing settings to inspect or manage an active subscription or payment recovery.

Notification preferences

Owners/admins can choose whether deployment outcome emails cover all results, only problems, or are off. Alerts, deployment notifications, provider delivery history and individual email preferences are separate settings.

The weekly digest is included on both plans. Eligible members can control it through user settings; its scheduled delivery uses the saved timezone (or UTC when Automatic). A digest is a summary of retained evidence, not confirmation that unknown checks passed.

For resource counts and server grouping, see Projects, components and infrastructure. For notifications, see Alerts and notifications.