BYOH · Bring your own hardware

Deploy on hardware you already own.

Tenkai turns a server you own into a deployment platform: a cloud VPS, a bare-metal box, or the Raspberry Pi on your shelf. Push your code, get HTTPS, databases, and rollbacks. The machine stays yours.

Start for free What can I bring?

Free for one server. No credit card.

root@raspberrypi: ~

$ curl -fsSL https://tenkai.cloud/enrollment/tk_8f2c… | sh ▍

✓ Created the tenkai user

✓ Authorized Tenkai automation access

✓ Registered raspberrypi with Tenkai

Server setup

Enrollment pending

Waiting for you to run the enrollment command

Architecture: arm64
System: Debian 12
CPU: 4 cores
Memory: 2 GB

Raspberry Pi 4 & 5
arm64
Mini PCs & old laptops
x86_64
Bare-metal servers
x86_64 or arm64
Hetzner Cloud
provisioned for you
DigitalOcean
provisioned for you
Scaleway
provisioned for you

Bring your own server

Any server can join. Even the one you haven’t bought yet.

Tenkai doesn’t run your apps on its machines. It prepares yours, whether you plugged it in yourself or asked a provider for it.

Enroll a machine you have

Run one command as root on any 64-bit Debian or Ubuntu server the internet can reach, even behind your home router. It creates a tenkai user, authorizes Tenkai’s key, and registers the server. Tenkai sets up the rest over SSH.

Or let Tenkai create one

Connect your Hetzner Cloud, DigitalOcean, or Scaleway account and pick a server type. Tenkai creates it in your account and enrolls it on boot. The provider bills you, at its own price.

Grow it into a cluster

Add servers of the same CPU architecture to a cluster, even at different providers. Tenkai links them over a private WireGuard network and keeps your databases on the workers.

Your hardware, your bill

Pay for servers once. Not for every app you put on them.

A platform on top of your own hardware means one small box can run several apps and their databases.

Tenkai never resells compute: Your hardware or your provider account runs your apps. There is no markup on CPU, memory, or bandwidth.
Flat plans, not per server: Plans are priced per team. Adding a server or a teammate never changes your bill mid-month.
Your machine stays yours: Removing a server from Tenkai leaves the machine running, unless you ask Tenkai to delete it. Your apps keep serving traffic if Tenkai is unreachable.

Footprint

A small server is enough.

Most self-hosted platforms run their own dashboard and database next to your apps. Tenkai keeps them on its side, so your server’s memory goes to what you deploy.

No control plane on your server
Tenkai’s dashboard, database, and job queue run on our side. Your server runs your apps, an edge router, and a registry.
Start with 2 GB of memory
A first server with 2 GB leaves about 1.4 GB for your apps, or about 950 MB when it also builds from Git. A worker you add later runs no builds and no router, so 1 GB is enough.
Builds stay in their share
When you deploy from Git, Tenkai builds on your server, in about a quarter of its CPU and memory. A heavy build leaves your live apps alone. Docker images need no build, and a cluster that only deploys them can give that share back to its apps.

Memory of a first server

Build from a Git repositoryTenkai keeps a share of the server for builds. Without it, the server deploys container images only.

2 GB server
System and Docker: 358 MB, Tenkai: 224 MB, Your apps: 1.4 GB.
4 GB server
System and Docker: 460 MB, Tenkai: 224 MB, Your apps: 3.3 GB.
8 GB server
System and Docker: 665 MB, Tenkai: 224 MB, Your apps: 7.1 GB.

System and Docker: 256 MB and 5% of the memory, at most 1 GB
Tenkai: 224 MB for the edge router and the registry
Builds: A quarter of the memory, from 512 MB to 2 GB, for the apps you deploy from Git
Your apps: Everything else

Why Tenkai keeps these shares

Deployments

A release takes traffic once it is healthy.

Push a commit and watch Tenkai build it, check it, and switch to it. If a step fails, the live release keeps serving.

Artifact01
Tenkai builds your Dockerfile or your source on your server, or copies your image into the cluster registry.
Health02
It starts the new release next to the live one and checks its health.
Route03
Traefik switches traffic to the new release. The previous one keeps serving until then, and stays for a rollback.

Agents

Deploy from your editor. Approve with one click.

Connect your coding agent to Tenkai over MCP. It sets up the project and asks to deploy. The only time you leave your editor is to approve.

Connect once01
Create an agent token in Tenkai and add its MCP server to Claude Code, Codex, Cursor, or any client that speaks Streamable HTTP.
Your agent does the work02
It creates the project and the web application, deploys, and reads the logs when a build fails. Your code reaches Tenkai through Git or an image, never through MCP.
You approve what ships03
Every deployment and every new server waits for your click on a Tenkai link. Nothing ships or costs money without it.

agent: ~/blog

> Ship this repo to my Raspberry Pi ▍
⏺ git push origin main
└ Pushed 3f9c2a1
⏺ tenkai · create_project
└ blog, running Production on home-lab
⏺ tenkai · create_resource
└ Web Application from github.com/you/blog
⏺ tenkai · deploy_resource
└ confirmation_required → tenkai.cloud/agent-confirmations/7c1e…
⏺ tenkai · deploy_resource
└ deployment_queued
⏺ tenkai · get_deployment
└ succeeded · 3f9c2a1 takes traffic

Hako · 箱

Meet Hako. It knows your servers.

The agent built into Tenkai. Ask it why a deployment failed, which server is full, or what changed last night.

Ask from any page: Hako knows which page you asked from, and reads what it needs to answer.
Diagnoses failed deployments: It names the cause on the page of the deployment, with the fix.
Nothing changes without you: Every action waits for your click. Variable values never reach it.

10 questions a month on Free, 200 on Hobby, 500 on Pro, 2,000 on team.

The platform

Everything you’d expect from a PaaS, on a server you control.

Deploy from Git

Build with your Dockerfile, or without one from source. Builds run on your own server.

Or ship an image

Deploy public images from Docker Hub or GHCR, or private GHCR images, pinned to their digest.

Managed databases

PostgreSQL, MySQL and Valkey, with their connection URL handed to your app. MariaDB is coming soon.

Encrypted backups

Back up PostgreSQL, MySQL and Valkey every day to a bucket you own, encrypted on your server with a key you can download.

Domains with HTTPS

Every app gets an HTTPS hostname. Point your own domain at it and Tenkai issues and renews its certificate.

Environments

Every project starts in production. Add a staging beside it, empty or as a copy with empty databases and no secrets.

Secrets

Sensitive values stay hidden, and only members allowed to reveal them can.

Rollbacks

Every deployment keeps its release, so you can roll back to an earlier one.

Server metrics

Follow the CPU, memory, disk, and network usage of each server over the last week.

Logs and terminals

Follow the logs of a container, or open a terminal in it or on its server, from your browser.

Server upkeep

See the package updates each server waits for, then install them and reboot when you choose.

Marketplace

Install apps such as Umami and draw.io into a project, without writing their configuration.

No proprietary runtime

Built from parts you already trust.

Tenkai installs Docker, Traefik, and WireGuard on your server and drives them over SSH. Its agent only reports the health of the server, and you can remove it. Nothing runs there that you couldn’t inspect with the tools you know.