CloudSignal CLI

Manage your CloudSignal organization from the terminal. Install, authenticate, and manage ACL policies without the dashboard.

The CloudSignal CLI lets you manage your organization from the terminal - the same way tools like supabase, wrangler, and vercel work.

Install

npm install -g @cloudsignal/cli

Verify the installation:

cloudsignal --version

cloudsignal login

This opens your browser for authentication. After logging in, the CLI stores a session token locally.

cloudsignal acl get

Outputs the current policy as JSON. Pipe it to a file:

cloudsignal acl get > policy.json

Edit policy.json in your editor, then validate and deploy:

cloudsignal acl validate policy.json
cloudsignal acl update policy.json

Command	Description
`cloudsignal login`	Log in via browser
`cloudsignal logout`	Clear stored credentials
`cloudsignal whoami`	Show current auth status
`cloudsignal acl get`	Fetch current ACL policy
`cloudsignal acl validate <file>`	Validate a policy file
`cloudsignal acl update <file>`	Deploy a policy from file
`cloudsignal acl simulate`	Simulate a pub/sub access check

The CLI stores config and credentials in ~/.cloudsignal/:

File	Purpose
`config.json`	API URL override (optional)
`credentials.json`	Session tokens (auto-managed)

Variable	Description
`CLOUDSIGNAL_API_URL`	Override the API base URL
`CLOUDSIGNAL_DASHBOARD_URL`	Dashboard URL (defaults to `https://dashboard.cloudsignal.app`)

Environment variables take precedence over ~/.cloudsignal/config.json.

How login, token refresh, and session management work

Get, validate, update, and simulate ACL policies