Security & Trust
Terminalwire ships a command line to your users from software you can read: the server is open source and runs in your infrastructure, and the client is sandboxed like a browser, asking permission before it touches anything. Here's exactly how it holds up to a real security review.
Open, in your infra
The server is Apache-2.0. The code near your data runs on your servers.
Least privilege
The client can't touch a file, host, or the browser unless you granted it.
Fail-closed updates
Every client update is signature-verified against an offline root, or it doesn't run.
No user tracking
We never see the commands your users run, and we don't profile people.
The architecture
Not a trust-us page. Every claim below maps to how the software is actually built.
Apache-2.0 · runs in your infra
Read it, audit it, fork it, self-host it. The code that touches your users' data is a normal dependency your security team can review, running under your control, on your schedule.
default-deny · per-origin grants
It can't read a file, reach a host, run a subprocess, or open the browser unless your user granted exactly that to the server it's talking to. Storage is isolated the same way.
offline root key · SHA-256 pinned
The client trusts one public key compiled into it. Every release is signed and pins each artifact by hash. Anything that doesn't verify doesn't run, and a server you connect to can never push code.
direct connection · we're not in it
The client talks to your server directly, so we never see commands, input, or output. We record connection and licensing metadata (server URL, IP, client version) and count installs, not people.
wss · your existing login
No separate credential store: the CLI authenticates through your web app, with your sessions and your policies, because the command line is another view of the server you already secure.
one conformance suite · every implementation
Ruby, Go, and Elixir servers and the client replay the same recorded sessions byte-for-byte, so a client upgrade never surprises a production deployment.
For your security review
What runs on our servers?
The open-source Apache-2.0 server, as a normal dependency of your app. Code your team can read and audit.
Can it read arbitrary files on user machines?
No. Filesystem, network, and browser access are denied unless explicitly granted per origin.
Can a server we connect to push code to the client?
No. Updates are vendor-signed and verified against an offline root; the client fails closed.
Do you see our users' commands or data?
No. The client talks to your server directly; we're not in that path.
Do you track individual users?
No. No user accounts, no profiles. We count installs, not people.
Is it safe for CI and AI agents?
Yes. The license check never blocks, gates, or prompts, and never changes an exit code.
How does authentication work?
Through your existing web app: your login and sessions, no separate credential store.
Is traffic encrypted?
Yes, over wss in production, secured by your own TLS.
The fine print
The legal and data commitments behind everything above.
Terminalwire · Legal
What you can expect, and what we commit to.
Terms →Terminalwire · Legal
Exactly what we collect, and what we never do.
Privacy →Terminalwire · Legal
The agreement for the client your users install.
Client EULA →Have a security questionnaire or need something for procurement? Talk to a human →
The practical part
Community is free for non-commercial use. Commercial CLIs start at $199/month, and the meter only counts clients that ran a command that month.