licenseMIT

Your app belongs
on
your servers

The platform layer that makes them feel like a PaaS.

install with one command
$curl -fsSL https://tako.sh/install.sh | sh
ask Codex, Claude, or another agent

Move this project to tako.sh.

Takosophy

Full control. A real server, a real runtime — what runs locally runs in production.

Unapologetically opinionated. No config rabbit holes — Tako picks the defaults so you can ship.

Built for the impatient. Every step is optimized to get your code live fast.

Three commands and you're live

  1. tako init

    Detect runtime, create config

  2. tako dev

    Develop locally with HTTPS

  3. tako deploy

    Build, upload, rolling update

Development

Develop against the whole platform.

tako dev brings the production platform with it: workflows, channels, image optimization, secrets, and the same routing model your app uses after deploy.

Development docs →

Deploy

Fast rolling deploys to your VPS.

PaaS-style release safety on servers you own.

tako deploy gives you health-gated traffic switches, zero-downtime rollouts, and rollback without moving off your VPS.

Deployment docs →
Tako deploy targetsOne Tako deploy command branches to VPS targets in AWS Tokyo, Vultr Amsterdam, and Hetzner Ashburn.$tako deployAWSap-northeast-1TokyoVultramsAmsterdamHetznerus-eastAshburn, VA

Platform

Your VPS becomes the platform.

Your VPS stays yours. tako-server adds the platform layer: TLS, routing, processes, logs, secrets, rollbacks, and scale-to-zero workers without hiding SSH or the machine.

The same server runs the app primitives agents usually have to provision elsewhere: secrets, env vars, workflows, channels, image optimization, storage, cache, and backups. They stay available from code, so an agent can wire the feature in the repo instead of assembling extra services.

How Tako works →
// src/server/database.ts
// typed secret reads, no env files
import { tako } from "tako.sh";

export function connectDatabase() {
  return createClient({
    // read the one value you need; never log the bag
    url: tako.secrets.DATABASE_URL,
    ssl: tako.isProd,
  });
}

Ready for serious load

Bar chart comparing clean HTTPS 200 responses per second: Tako at 12.5k, Caddy at 5.2k, and Envoy at 4.7k.Clean HTTPS 200 RPShigher is betterTako12.5kCaddy5.2kEnvoy4.7k
full report →

Tako can handle heavy traffic even on modest hardware: one small VM served 12.5k HTTPS 200 RPS at 5k concurrency, with zero client errors up to 20k concurrency. In the same public run, it outpaced Caddy and Envoy under heavy HTTPS load.

Stop configuring.
Start shipping.