Private access
A dedicated strackt user connects over a private network using short-lived SSH certificates.
What access strackt needs
The dedicated user needs administrative rights to install updates, apply configuration and restart services. Day-to-day work uses this account, not your personal login.
Data and credentials
What strackt stores
- Server addresses and recorded configuration.
- Application secrets and access credentials in an encrypted vault.
- Operation history and results.
What strackt never stores
- Application databases and uploads; these stay on your server or in your own backups.
- Permanent SSH private keys or root passwords.
- Application traffic; strackt is not a proxy in front of your app.
What gets recorded
Your activity history records what ran, what triggered it and the result. Deploys and provisioning stream live into the dashboard.
Leaving strackt
Detaching generates a standalone server configuration, activates it and verifies the services before releasing management. You keep the server and its running applications. Completed backups remain in your own storage, recoverable with your key and stock restic.
When something goes wrong
strackt is unavailable. Your application keeps serving traffic; our control plane is outside its request path.
Your server is unreachable. strackt retries and reports a persistent connection failure.