Private access
Your app runs on servers reached through a private network. A dedicated strackt account connects with signed SSH certificates capped at one hour. The normal platform connection uses a certificate valid for 30 minutes. Each new connection gets a fresh certificate.
What access strackt needs
The dedicated account needs administrative rights to install security fixes and upgrades, apply the recorded setup, deploy releases and restart services. That access can reach application files and data on the servers. Day-to-day work uses this account, not your personal login. While managed, your team has its own logins with full admin rights, using short-lived signed certificates capped at one hour.
Data and credentials
What strackt stores
- Server addresses and the recorded setup.
- Application secrets and access credentials in an encrypted vault.
- A fallback SSH key, held in that vault, for when certificate signing is unavailable.
- Operation history and results.
What stays outside strackt
- Application databases and uploads stay on your servers or in the backup destinations you choose.
- Application traffic goes to your app; strackt is not a proxy in front of it.
- Your personal login is not the account we use for routine work.
What gets recorded
The activity history records what ran, what triggered it and the result: the server work as well as deploys. Deploys and setup changes stream live into the dashboard.
Leaving strackt
It’s your app, on your servers. You can leave strackt anytime, and your app keeps running where it is. The servers stay in your provider account. Handover is in beta and is not enabled in every workspace.
When available, the owner supplies a username and their own SSH public key. strackt activates a standalone NixOS setup under /etc/nixos, with the current apps, databases and services, and checks the services before releasing management. You receive a downloadable guide for rebuilding, security updates and editing secrets.
You sign in with your own key and confirm access within 14 days. Until confirmation, strackt retains admin access. Choose to remove that access at release, or keep it for a later return. If you do not confirm in time, the servers return to strackt management and overwrite manual setup changes made during handover.
Your custom domains and certificate renewal keep running, as do supported local snapshots and configured S3 backup jobs. Platform addresses on on-strackt.dev stop working, so arrange your own domains first. Carried backup credentials need attention; the guide explains how to point backups at your own bucket. Any completed backups in your own storage remain recoverable with your key and standard backup tools.
From handover, strackt stops deploying, monitoring, patching and maintaining those servers. Their upkeep is yours again. Keep the guide and your access details. Read the handover guide.
When something goes wrong
strackt is unavailable. Your application keeps serving traffic; our control plane is outside its request path.
Your servers are unreachable. strackt retries and reports a persistent connection failure. Server work that needs a connection cannot continue until access returns.