BYOH · Bring your own hardware

Deploy on hardware you already own.

Tenkai turns any server you own into a deployment platform, from a cloud VPS to the Raspberry Pi on your shelf. Push your code, get HTTPS, databases, and rollbacks. The machine stays yours.

Free for one server. No credit card.

The enrollment command registers a Raspberry Pi with Tenkai. Tenkai then connects over SSH and sets it up: SSH connectivity, Security baseline, Cluster network, Execution runtime, Cluster registry, Edge router, Target telemetry. The server is then ready.
  • 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.

01

Enroll a machine you have

Run one command on any Debian or Ubuntu server, even the one behind your home router, and Tenkai sets up the rest.

02

Or let Tenkai create one

Connect your Hetzner Cloud, DigitalOcean, or Scaleway account, pick a server type, and Tenkai creates it ready to deploy, at your provider’s usual price.

03

Grow it into a cluster

Start with one server and grow into a cluster that keeps your apps online when a machine dies, even across providers.

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 apps run on your hardware or your provider account, with no markup on CPU, memory, or bandwidth.
Flat plans, not per server
You pay one price per team, so adding a server or a teammate never changes your bill.
Your machine stays yours
Your machine keeps running if you leave Tenkai, and your apps keep serving even when Tenkai is down.

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, so your server keeps its resources for your apps.

  • Start with 2 GB of memory

    A 2 GB server leaves about 1.4 GB for your apps, and a worker you add later runs fine on 1 GB.

  • Builds stay in their share

    Tenkai builds on your server within about a quarter of its CPU and memory, so a heavy build never slows your live apps.

Memory of a first server
  • 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
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.

Tenkai builds the release of a web application, starts it and checks its health, then switches traffic from the live release to the new one.
  1. Artifact01

    Tenkai builds your code on your server, or pulls your image.

  2. Health02

    It starts the new release next to the live one and checks its health.

  3. Route03

    Traffic switches to the new release, and the previous one stays ready for a rollback.

Agents

Deploy from your editor. Approve with one click.

Connect your coding agent to Tenkai. It sets up the project and asks to deploy, and you only leave your editor to approve.

  1. Connect once01

    Add Tenkai’s MCP server to Claude Code, Codex, Cursor, or any MCP client.

  2. Your agent does the work02

    It creates the project, deploys it, and reads the logs when a build fails.

  3. You approve what ships03

    Every deployment and every new server waits for your approval, so nothing ships without you.

An agent pushes a repository to Git, then creates a project and a web application in Tenkai through MCP. When it asks to deploy, Tenkai returns a link, and the deployment only starts once the user approves it there.

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’re on and reads what it needs to answer.
Diagnoses failed deployments
It names the cause and the fix on the deployment’s page.
Nothing changes without you
Every action waits for your click, and Hako never sees your secrets.

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

A team member asks Hako why their blog answers errors since this morning. Hako reads the blog and its logs, then answers that the release of 09:40 expects a table that its migration did not create.

The platform

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

Deploy from Git

Build with your Dockerfile, or straight from source without one.

Or ship an image

Deploy an image from Docker Hub or GHCR, including your private GHCR images.

Workers and scheduled jobs

Keep a queue consumer running, or run a command every night.

Managed databases

Run PostgreSQL, MySQL or Valkey, already connected to your app. MariaDB is coming soon.

Encrypted backups

Back up your databases every day to a bucket you own, encrypted with your own key.

S3 buckets

Host S3-compatible buckets on your own cluster for uploads and exports, and bind one to an app in a click.

Domains with HTTPS

Every app gets an HTTPS address, and your own domains get their certificates automatically.

High availability

Run three managers and your apps keep answering when a server fails.

Environments

Every project starts in production, and you can add a staging beside it in a click.

Pull request previews

Each pull request gets its own environment, and Tenkai cleans it up when you merge.

Secrets

Sensitive values stay hidden, and you choose who can reveal them.

Rollbacks

Roll back to an earlier release in one click.

Server metrics

Follow each server’s CPU, memory, disk, and network over the last week.

Logs and terminals

Read your logs and open a terminal in a container or on a server, from your browser.

Server upkeep

See the updates each server waits for, and install them when it suits you.

Marketplace

Install apps such as Umami and draw.io in a few clicks.

No proprietary runtime

Built from parts you already trust.

Tenkai runs Docker, Traefik, and WireGuard on your server, so nothing there is a black box and you inspect it with the tools you know.

  • Runtime

    Docker

  • Routing & HTTPS

    Traefik + Let’s Encrypt

  • Cluster network

    WireGuard

Pricing

One price per team. Any number of apps.

Your servers run as many apps and databases as they can hold.

Billing interval

Free

For your personal team

0 €/mo

  • 1 server
  • 1 member
  • 10 Hako questions a month
Start for free

Hobby

For side projects

9 €/mo

  • 3 servers
  • 1 member
  • 200 Hako questions a month
  • CrowdSec protection
Choose Hobby

Pro

For a small team

24 €/mo

  • 10 servers
  • 5 members
  • 500 Hako questions a month
  • CrowdSec protection
  • Authorized keys check
  • Host exposure check
Choose Pro

Team

For a company

49 €/mo

  • Unlimited servers
  • Unlimited members
  • 2,000 Hako questions a month
  • CrowdSec protection
  • Authorized keys check
  • Host exposure check
  • Activity logs
Choose Team

Prices exclude tax. VAT or sales tax is added at checkout.

Plug it in. Deploy to it.

Create your account, enroll your first server, and deploy. Free for one server, no credit card.

Start for free