October 2026: Sliplane CLI and Confidential Region

Sliplane now has a CLI. You can deploy and manage services, servers, PostgreSQL databases, and S3 buckets from your terminal. We also opened a new region for data protected by professional secrecy and added a few things to the public API.

Sliplane CLI

Install it on macOS, Linux, or WSL:

curl -fsSL https://sliplane.io/install.sh | sh

Then log in through your browser and get going:

sliplane auth login                   # log in through your browser
sliplane service list                 # list your services
sliplane deploy n8n --name workflows  # deploy a preset
sliplane logs workflows --follow      # stream its logs
sliplane ssh workflows                # open a shell in it

The CLI covers most of what you do in the dashboard: services, servers, domains, volumes, environment variables, PostgreSQL, S3 buckets and files, registry credentials, and SSH keys. A few things work better in a terminal than in a browser:

• sliplane ssh opens a shell in a service with a temporary key, and sliplane tunnel forwards a local port to it.
• sliplane postgres connects you to a database and can check its allowlist for your current IP.
• sliplane metrics charts CPU and memory history or watches live usage of a service or server.
• sliplane agent init adds Sliplane best practices to your project, so coding agents like Claude Code, Codex, or Cursor know how to deploy it.

Add -o json to any command for structured output. In CI, set SLIPLANE_TOKEN to an API key, ideally one with scopes limited to what the job needs. If you work in more than one team, --profile switches between them.

The CLI is open source and still in alpha. Releases are signed, and it checks for updates on its own. Find the code, releases, and issue tracker on GitHub.

Germany (Confidential) Region

Germany (Confidential) is a separate region for data that falls under professional secrecy (§ 203 StGB), for example in law firms, tax advisory, or software built for them. It runs isolated from the rest of Sliplane, and only a small group of authorized staff can access the infrastructure. Sliplane and its infrastructure provider are bound to secrecy under § 203 StGB.

To enable it, the team owner accepts the Confidential Data Agreement on the compliance page. After that, you can pick the region when you create a server or a database. It only offers dedicated CPUs. Prices are on the pricing page, and the professional secrecy page has the details.

API Updates

• Deploy hooks: services now return their deployHookUrl when your API key has secrets read access. POST /projects/{projectId}/services/{serviceId}/deploy-hook/rotate creates a new one and disables the old URL.
• Postgres metrics: GET /v0/postgres/{postgresId}/metrics returns CPU, memory, disk, and connection history.
• Server disk usage: server metrics now include usedDisk, freeDisk, and totalDisk, so you can monitor disk space over time.
• Internal port: service responses include network.internalPort.

Check the API reference for the full details.

That's it for now. As always, if you run into any issues or have feedback, hit us up via the chat widget or at support@sliplane.io.

See you next time,

Jonas