Installation
Install with Homebrew
Install with shell
Build from source
Contexts
The Sequin CLI uses contexts to manage different configurations and environments. Each context stores:- API token for authentication
- Hostname configuration (for self-hosted Sequin instances)
- TLS settings (for self-hosted Sequin instances)
sequin context
Display available context commands:
sequin context add
Create a new context:
Flags
--api-token: Your authentication token--set-default: Set as the default context
--hostname: API hostname of your Sequin instance (defaults to api.sequinstream.com)--tls: Enable/disable TLS (enabled by default)
--tunnel-ports: Configure default tunnel ports
sequin context ls
List all contexts:
sequin context select
Switch between contexts:
Using contexts with commands
Use a specific context for any command with the--context flag:
Config
Theconfig command group allows you to manage Sequin resources using YAML configuration files. This provides a declarative way to create and manage databases, sinks, HTTP endpoints, and other resources.
sequin config
See the sequin.yaml reference for detailed configuration options and examples.
Commands
sequin config export- Export current configuration as YAMLsequin config plan [file]- Preview changes from a YAML filesequin config apply [file]- Apply changes from a YAML filesequin config interpolate- Interpolate environment variables in a YAML file
file argument defaults to sequin.yaml if not specified.
Flags
--auto-approve- Skip interactive approval for theapplycommand (useful for CI/CD)
Example Workflow
Using with Contexts
All config commands respect the current context and can be used with the--context flag:
The
export command is experimental. Exported configurations may need manual adjustments before use:accountandusersections are not exported- Encrypted fields like passwords need to be manually specified

