Tako

Tako helps you ship apps to your own servers without turning deployment into a part-time job.

Why Tako exists

Deploying used to feel simple: upload files, refresh, done.

Tako is an attempt to bring that feeling back, but with modern guardrails:

• fast local development
• smooth deploy flow
• app up and serving traffic quickly, without platform drama

You get:

• a CLI (tako) for local dev + deployment
• a remote runtime/proxy (tako-server)
• a local development daemon (tako-dev-server)
• a JavaScript/TypeScript SDK (tako.sh)

Prerequisites

• Rust toolchain (stable)
• Bun (for SDK/examples/website tooling)
• just (optional, but useful for repo tasks)

Quickstart

From the repo root:

bun install
git config core.hooksPath .githooks
cargo build
cargo test --workspace
# Full matrix: Rust workspace + SDK tests + Docker e2e fixture test
just test

Run CLI help from source:

cargo run -p tako --bin tako -- --help

Run the Bun example with Tako local dev flow:

just tako examples/js/bun dev

Format Rust + repo files:

just fmt

Run lint checks:

just lint

Run full local CI flow (format, lint, tests):

just ci

Repo Layout

• tako/: CLI crate (tako) and local dev daemon binary (tako-dev-server)
• tako-server/: remote runtime/proxy crate (tako-server)
• tako-core/: shared protocol types
• tako-socket/: shared Unix socket JSONL transport helpers
• sdk/js/: tako.sh SDK package
• examples/: runnable examples
• e2e/: deploy e2e fixture apps used by Docker integration tests
• scripts/: install/check helper scripts
• website/: Tako website + installer endpoints
• docker/: internal Docker tooling for build/debug workflows

Deploy E2E Fixture Test

Run Docker-based deploy e2e for fixture apps:

just e2e e2e/fixtures/js/bun
just e2e e2e/fixtures/js/tanstack-start

Release Workflow (Maintainers)

Use the release module entrypoints:

just release tako
just release tako-server
just release sdk
just release tako-core
just release tako-socket

Release tags are signed (git tag -s). Ensure local Git tag signing is configured before running release commands.

Each command is a full flow for that component:

• release tako: cargo publish -p tako + versioned release notes + GitHub release asset upload (tako-*)
• release tako-server: cargo publish -p tako-server + versioned release notes + GitHub release asset upload (tako-server-*)
• release sdk: release notes + npm publish from sdk/js
• release tako-core: shared crate release + cargo publish -p tako-core
• release tako-socket: shared crate release + cargo publish -p tako-socket

Recommended full release order:

just release tako-core
just release tako-socket
just release tako-server
just release tako
just release sdk

release tako and release tako-server enforce a guard: if tako-core or tako-socket source changed since the last shared crate release tag, they fail with instructions to release shared crates first. release tako and release tako-server also require authenticated GitHub CLI (gh auth login) to publish release assets used by https://tako.sh/install and https://tako.sh/install-server.

Release notes are written under dist/release-notes/. tako and tako-server notes use git-cliff with cliff.toml, focusing on user-facing Features and Bug Fixes. Notes generation is path-filtered per component (--include-path) so only relevant commits are included.

Docs

User docs live in website/ (source pages: website/src/pages/docs/).

Component-focused docs:

• tako/README.md
• tako-server/README.md
• tako-core/README.md
• tako-socket/README.md
• sdk/js/README.md

License

Tako source code is licensed under MIT (/LICENSE).