Welcome to Kumoto
Kumoto is a control plane for deploying and operating applications on servers you control. It gives your team one place to connect servers, model an application and its dependencies, and safely apply infrastructure changes.
You bring the server and your source code. Kumoto connects the server through its agent, keeps the desired state in a project draft, and records each deployment as it is applied.
How Kumoto works
- Connect a server that you administer.
- Create a project for an application or service.
- Add components for the application, databases, caches, scheduled work, and other dependencies.
- Review the draft before it changes the deployed infrastructure.
- Deploy and follow the rollout through stages, tasks, and logs.
This model lets you make infrastructure changes deliberately without treating a server as a collection of one-off manual changes.
Before you begin
To complete the first deployment, you need:
- an active Kumoto account with capacity for a project and server;
- a server you can access over SSH with permission to run
sudo; - an application component to deploy; and
- a connected source-control provider for repository-backed applications.
Source control is not required to explore the dashboard or create a project, but it is needed when configuring a source-backed application component.
Core concepts
| Term | Meaning |
|---|---|
| Server | A machine connected to Kumoto with the Kumoto agent. |
| Project | An application and the infrastructure it needs. |
| Component | A deployable app, data service, cache, scheduled job, or Docker service. |
| Draft | A proposed version of a project that has not yet been deployed. |
| Deployment | The tracked rollout of a draft, including stages, tasks, and logs. |
Start with the quickstart.