Local or Cloud · Statuz

Same commands in both. Only where they run changes.

Local

Free. No account, no watermark.
Posts and media in ~/.statuz. Tokens in the OS keychain.
Publishes straight to each platform.
Bluesky and Mastodon need nothing. X and LinkedIn need your own developer app (how).
Your computer must be on. Posts more than an hour late are marked missed.
Personal computers only; VMs and headless servers are refused.

Publishes on time, computer on or off.
Orgs, teams and roles. Viewers look. Members write posts and change their own. Admins also change anyone's and run the team, keys and settings. Owners also hold billing.
Web composer.
No developer apps: Cloud uses Statuz's own X and LinkedIn apps.
Photos bigger than a platform takes are shrunk for it as they go out; the original stays as it is. Videos and GIFs must fit.
API keys for scripts, CI and agents, each with its own role: viewer, member or admin, never owner, so no key touches billing. A key also never does more than the person who made it can today.
Each org has a time zone, for times like "tomorrow 9am" that come without one (agents, mostly). It starts as yours; change it in Settings or with statuz cloud org update --timezone America/Sao_Paulo.
Holds the tokens, posts and media it needs to publish. See Privacy.

Extra seat: $5 a month.
Prepaid credits, $5 minimum, expire after six months. Oldest spent first. Owners add them.
Free: drafts, scheduling, edits, reads, agent calls, failed or cancelled publishes.
A thread costs the sum of its posts.

Current prices: Pricing or statuz cloud pricing.

Terminal

statuz use cloud
statuz use local

Same as statuz config set --key target --value cloud. The CLI, MCP and your agent all follow it. Local and Cloud posts are kept apart.