What's your threat model here? The way this works is that on your development machine, localias (through caddy/mkcert) generates a root cert and the per-site ce

What's your threat model here? The way this works is that on your development machine, localias (through caddy/mkcert) generates a root cert and the per-site certs and installs them to your development machine's trust store. All of the certs live entirely on your device and never leave. You have full control over them and can remove them at any time. The certs and keys live in the localias application state directory on your machine: • tree /Users/pd/Library/Application\ Support/localias/caddy/pki/authorities/local/ /Users/pd/Library/Application Support/localias/caddy/pki/authorities/local/ ├── intermediate.crt ├── intermediate.key ├── root.crt └── root.key The whole nicety of localias is that you can create domain aliases for any domain you can think of, not just ".localhost". For instance, on my machine right now, the aliases are: • localias list cryptoperps.local -> 3000 frontend.test -> 3000 backend.test -> 8080