Keep the environment you trust
Your code stays on the machine where it runs. Agent credentials, shells and project tools remain there too.
Self-hosted Denshin
Remote control without moving the workload.
Run beside your code and credentials. Keep the terminal on infrastructure you control.
Your machine remains the runtime.
Denshin adds a durable daemon and a mobile control surface. It does not copy your repository into a hosted workspace.
Run as your user, with consent
Install starts nothing. Denshin explains OS-user authority before the first run; an optional launchd or systemd service keeps durable tmux sessions available afterward.
Update with a rollback path
Versioned releases, mandatory checksums and an atomic current pointer keep the previous host release intact until the new one is ready.
Choose the reachable path
Connections use HTTPS/WSS or private Tailscale. A stable TLS origin remains available when a private network is not the right fit.
From install to first session.
The public host runtime and TestFlight app follow the same tested installation contract.
- Install the signed runtimeDownload the public host release with one command.
- Allow host accessReview the OS-user permissions, then start Denshin beside the repositories and agents already on your machine.
- Pair your phoneScan one short-lived QR, then open the same durable terminal and agent sessions.
Self-hosted still needs a trust boundary.
Owning the machine does not make every network path or device trusted. Enrollment and application authority remain explicit.
Enrolled deviceDevice credential
HTTPS/WSS or private TailscaledenshindOn your machine
Local PTYTerminal plaintext