Run your database workflow from the terminal.

From the SaveOn repository, run npm link to expose the saveon command locally. When a published package becomes available, the same command can be installed from the package registry.

Create an API key in your SaveOn workspace, then store it in the CLI’s restrictive local configuration file. Do not commit that file or paste the key into browser code.

Use the CLI to list databases, inspect a database, create a new database from a live package identifier, retrieve connection details when needed, and delete a database after confirming the identifier. The server remains responsible for authentication, wallet checks, limits, provisioning, and authorization.

The CLI prints API responses to your terminal because the command is an explicit developer action. Treat API keys and connection strings as secrets: use a trusted machine, avoid shell history where practical, and never include secrets in issue reports or screenshots.

Use separate API keys for different environments and revoke a key from the workspace when it is no longer needed.

The CLI speaks in terms of workspaces, databases, packages, regions, service state, and connection access. It does not require developers to know which underlying infrastructure service SaveOn uses.