Kloudlite Documentation
Kloudlite runs development workspaces and application environments on Kubernetes regions you control, and connects the two over the network. You edit in a workspace. The application runs in an environment. An intercept routes one service's traffic to your workspace, so a change is observed without a build, a push, or a deploy.
Every object is reachable three ways with the same semantics: the web console, the kl-connect CLI on your machine, and the /v1 HTTP API. Agents use the API and ssh; people use whichever is closest to hand.
Get started
Create a workspace, connect to it, and run something in under five minutes.
Quick startSign in, create a workspace, ssh in, run a service.AuthenticationTokens, ssh keys, and what each one may do.
What you get
| Object | What it is |
|---|---|
| Workspace | A running sandbox with your source tree, a Nix toolchain, and ssh access. One per change you are making. |
| Environment | Your application: a set of services with their data, owned by you or a team. |
| Snapshot | A point-in-time copy of a workspace's tree or an environment's data. Restore, clone, or keep it. |
| Connection | A workspace in a session on an environment resolves its services by name. An intercept delivers one service's traffic to the workspace instead. |
| Git and images | Repositories at git.khost.dev and an OCI registry at cr.khost.dev, under your handle or a team's. |
Interfaces
| Surface | Where |
|---|---|
| Console | https://dev.kloudlite.io |
| API | https://dev.kloudlite.io/v1, bearer token — see Authentication |
kl-connect | On your machine: sign in, list workspaces, ssh, write ~/.ssh/config — reference |
kl | Inside a workspace: kl build, kl push — reference |
| Git | [email protected]:{owner}/{repo} with the ssh key on your account |