How-to guides

Step-by-step guides for the common workloads people run on a Krova Cube. Each one assumes a Cube exists and walks through a single outcome — install, configure, deploy, automate. The interactive REST API reference at /docs/api and the SDK / CLI / MCP entry points at /developers cover programmatic control of every guide below.

All how-to guides

• Deploy PostgreSQL on a Cube — Install PostgreSQL 16 on a Cube, create a database and user, then connect two ways — an SSH tunnel while you develop, and an IP-allow-listed TCP port mapping for a deployed app.
• Run a Node.js app — Run a Node.js app on a Cube as a systemd service that survives reboots, and serve it on your own domain over HTTPS.
• Install Dokploy — Run a self-hosted PaaS on a Cube — Docker Swarm, Traefik and automatic TLS — including why the URL the installer prints does not work on a Cube.
• Deploy an app with Dokploy — Deploy an app through Dokploy and give it a domain — the HTTPS switch to leave off, and the port the Krova mapping has to use.
• GitHub Actions runner — Self-host a GitHub Actions runner on a Cube as a systemd service — outbound-only with no published ports, and the three steps whose error messages do not describe the actual problem.
• Snapshot and restore — Snapshot a Cube, restore it when something goes wrong, and know when you need a Backup instead — the copy that outlives the Cube.
• Back up and bring back — Create a Backup that outlives a Cube, redeploy an identical Cube from it, and move a Cube between spaces with its .cube archive.
• Manage Cubes from Claude — Connect Krova to Claude, Cursor or any MCP client so you can manage Cubes in conversation — including the environment variable beyond the API key.