Same software. Our time, in a contract.
The product does not change. What you are buying is deployment into your environment, development against your requirements, and someone who has to answer the phone.
Scoped per engagement.
Enterprise deployment
Installed into your environment, against your identity, network and compliance constraints rather than around them.
Custom integrations
Connecting Dialout to the systems you already run — internal registries, CI, ticketing, or a CLI we do not support yet.
Custom development
Features built for your workflow, in the open-source codebase, so you are not maintaining a fork.
Priority support
A named contact and a response time in writing, rather than a queue.
Migration assistance
Moving from whatever combination of scripts, dashboards and tunnels you are running today.
Security review
A walkthrough of the auth model, per-route authorization, encryption at rest and the deployment surface, with your security team in the room.
Architecture consulting
How to run it at your size — where the WebSocket process lives, how agents are provisioned, what to firewall.
SLA
Availability and response commitments, in a contract.
You can evaluate all of it first.
Nothing is behind a sales call. Install it, run it on your own machines, and read the authorization code — it is the part that matters most and it is all in the repository. Come to us when you have a question that needs an answer with a name attached to it.
If your security team needs to review it before it touches a developer machine, the security policy in the repository is written for exactly that read.
Tell us what you are running.
How many machines and people, where you would host it, and whether there is a security review to get through. Those three answers decide the shape of the engagement, so having them up front saves a call.
You get a copy of what you send. A person replies, usually within one working day.