Kyno documentation
Connect Kyno to Codex, Claude Code, or another MCP coding agent. Ask it to deploy your app. Share the private URL with your team.
Kyno is an MCP-first deployment service for small internal web apps. Your coding agent sends the source, Kyno builds it in an isolated microVM, and the running app gets a private HTTPS URL.
The shortest path
Section titled “The shortest path”- Connect your coding agent.
- Open the project you want to deploy.
- Ask the agent: “Deploy this app to Kyno and share it with
person@example.com.” - Open the URL returned by Kyno.
The agent can prepare a missing Dockerfile, read the project’s environment requirements, send variables and write-only secrets, and deploy the app for your workspace.
Important: Kyno is a self-serve beta for small internal tools. It is not a high-availability, multi-region, GPU, batch, or high-traffic platform.
What Kyno provides
Section titled “What Kyno provides”- One Firecracker microVM for each running app.
- A private URL at
https://<app-id>.apps.kyno.work. - Workspace invitations with Owner, Admin, Editor, and User roles.
- Runtime variables and encrypted, write-only secrets.
- A persistent SQLite database and a 1 GB data disk.
- Logs, redeployment, start, stop, and destroy controls through MCP.
Where to go next
Section titled “Where to go next”- Deploy an app for the normal agent workflow.
- Invite workspace members for roles, revocation, and leaving.
- App sleep and wake for inactivity, automatic sleep, and wake-up behavior.
- Security model for the trust boundary and current limits.
- Limits and compatibility before deploying a larger project.