1. Selected repository
A GitHub App installation token reads only selected repositories. GitLab and legacy OAuth use provider tokens.
2. Alkimist control plane
Stores encrypted configuration and queues work in an isolated per-account runtime workspace.
3. Your VPS
Receives images and configuration over SSH, runs the application, and remains in your cloud account.
Trust boundaries
Browser ↔ control planeSession authentication, CSRF protection, confirmation and lockout controls.
Control plane ↔ Git providerShort-lived GitHub installation token where configured; provider APIs determine repository authorization.
Runtime ↔ customer VPSDedicated generated SSH key. The public half is installed by the user; the encrypted private half drives requested operations.
VPS ↔ public internetYour application, firewall, DNS, data, and provider account remain your responsibility.
Threats considered
- ✓ A stolen database should not reveal application-encrypted tokens, private keys, or environment secrets without the separate encryption key.
- ✓ A leaked repository token is limited in lifetime and repository scope when the GitHub App path is used.
- ✓ Cross-account record access is constrained through ownership scopes and per-account runtime workspaces.
- ✓ Webhook requests use provider signatures or secrets before triggering deployment work.
- ✓ Destructive AI operations require the product's authorization and approval controls.
- ✓ Credential revocation is possible without moving the application or server.
Known limitations
Alkimist is a managed control plane, so a control-plane compromise could affect connected repositories and servers within their granted permissions. The public status page is served by the same application and is not an independent uptime monitor. GitLab OAuth permissions are broader than GitHub App repository selection. No independent penetration test, SOC 2 report, or ISO certification is currently claimed.