# Kyno

> Kyno deploys agent-built internal tools to isolated Firecracker microVMs and gives each workspace private HTTPS apps, role-based access, secrets, and persistent SQLite storage.

Kyno is a self-serve, single-host beta. Owners sign in with Google or an email magic link through self-hosted Better Auth, then create a company. It is designed for small internal web apps, not high-traffic, GPU, batch, or multi-region workloads.

Console login requests only `openid`, `email`, and `profile`. Workspace access
uses Owner, Admin, Editor, and User roles. Invitations, role changes, revocation,
and leaving are managed at the workspace level.

## Use Kyno

- Homepage: https://kyno.work/
- Pricing, limits, and application contract: https://kyno.work/pricing.md
- Dashboard: https://console.kyno.work/
- MCP endpoint: https://console.kyno.work/mcp

## Deployment contract

- Provide a root Dockerfile whose final process listens on `0.0.0.0:$PORT`.
- Store persistent data under `/data`.
- Use `DATABASE_URL` for the provisioned SQLite database.
- Only the root Dockerfile's final image runs.
- Apps may access the internet at runtime; direct SMTP and cloud metadata access are blocked.

MCP clients can deploy files or a public repository, redeploy an existing app at the same URL, manage variables and write-only secrets, inspect logs, and control app lifecycle.