Deploy from GitLab

Connect a GitLab Account

Deletions That Finish, Even Offline

Stop and Start One Container at a Time

Reconnect a Restored App

Tokens are never written into repository addresses — Server Compass no longer stores a personal access token inside a repository URL on your server, so a token can't be read out of a checkout later

If an old checkout still has one, you're told — the app shows whether the address needs migrating or whether the exposed token should be rotated, and walks you through replacing it and confirming you revoked the old one

Self-managed GitLab is trusted deliberately — connections use HTTPS by default, and plain HTTP or a self-signed certificate each require your explicit approval, remembered per account

An account can't be swapped to a different person by accident — replacing a token with one belonging to another user is refused with a clear explanation rather than quietly repointing the account

"Hide all data" now hides more — the dashboard also masks each server's username, port, and authentication type

Adding a Git account is clearer about what's supported — the empty state now offers GitHub, GitLab.com, and self-managed GitLab, and the account list shows every connected provider account with the servers it's linked to