September 2026: API Key Scopes, Server Migration, and Volume API

You can now limit API keys to exactly the resources they need, move services with persistent data between servers, manage volumes through the public API, and change where a volume is mounted without touching your data.

API Key Scopes

API keys are no longer all or nothing. Open the API tab in your team settings, create a key, and pick the access it gets for each area: projects, services, servers, Postgres databases, buckets, SSH keys, registry credentials, and OAuth clients. For every area you choose none, read, or write. The All row sets everything at once.

Secrets get their own switch. Without secrets access, environment variable values and database passwords come back empty. A key for a monitoring script can see your servers and nothing else, and a CI key can deploy services without ever reading your secrets. Keys show a Custom or No secrets badge in the list, and you can change a key's access later with Edit from its menu. If a request needs access the key doesn't have, you get a 403 that names the missing scope.

Migrate Services Between Servers

Backups can now be restored on a different server, so you can move services to another server even when they have persistent data. Click Restore next to a backup, pick the Target server, and Sliplane creates a new volume with the backup's contents there. Attach it to a copy of your service, switch your domains over, and you're done. Restores to another server need a current-generation server as the target.

Our step-by-step guide shows the whole process: How to Migrate a Service to Another Server on Sliplane.

Manage Volumes via the API

The public API can now manage volumes too. Attach a volume to a service, change its mount path, detach it, or rename a volume on a server, all with an API key. That makes volume setup scriptable as part of your own tooling or CI.

Change a Volume's Mount Path

Picked the wrong path when you attached a volume? Open the volume on your service, click Update below the mount path, or choose Edit Volume from the three dot menu. Enter the new path and save.

Your service redeploys and the data in the volume stays untouched, it simply shows up at the new path. If a volume is shared between services, only the mount path of the current service changes. Check the volumes docs for 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,

Lukas