What the Developer Mac plan covers
ElseKept discovers supported project documents, Apple and Android developer data, configuration folders, tool-version files, Git configuration, shell dotfiles, Vim data, npm configuration, Gradle properties, SSH material, GPG material and cloud configuration.
SSH keys need more than copying
The app inventories common and custom-name SSH private keys conservatively and follows safe SSH configuration includes. Recovered keys and configuration are staged for review so permissions, destinations and old access can be checked before placement.
Keychain and signing identities have limits
ElseKept records identity metadata and can retain raw Keychain databases as encrypted recovery evidence. It does not silently export signing private keys or replace the live Keychain. Exportable identities should use a supported macOS export workflow, while Secure Enclave keys must be re-enrolled on the new Mac.
Do not forget reproducibility
- Keep source repositories pushed to a remote host.
- Record package and tool versions in project files where possible.
- Keep cloud recovery codes outside the Mac.
- Document applications and licenses that cannot be reconstructed from files.
- Test one recovery into a staging folder before retiring the old Mac.
A backup preserves bytes. It cannot preserve access to a revoked SSH key, expired signing certificate, inaccessible password-manager account or non-exportable hardware key.