Single-node Threadron

Your state. Your server.

The core of Threadron is open source and always will be. Run single-node Threadron on your own machine — ideal for local dev, testing, and solo agent workflows.

When you need multi-agent coordination, cross-device continuity, or long-running workflows, you need Cloud Threadron. Single-node is one machine. Cloud is everywhere.

View on GitHub Docker Quickstart

What you get

The full core. Good for single-node. No asterisks.

Complete REST API

Every endpoint. Work items with structured state, artifacts, events, claims, agent registry, projects. Nothing held back in the open-source core.

Web Dashboard

The same board you'd get on the managed service. See who claimed what, what's blocked, full event history per work item. Real-time updates.

Docker Compose

One command to run. API server + PostgreSQL, containerized and ready. Bring your own reverse proxy for TLS and you're production-ready.

Agent Templates

Pre-built skill.md configs for Claude Code, OpenClaw, Hermes. Drop into your agent's system prompt. Agents check in, claim work, and maintain state automatically.

Single-node setup

Up and running in 60 seconds

      Terminal
# Clone the repo
git clone https://github.com/tasksforagents/tasksforagents.git
cd tasksforagents

# Start the stack
docker compose up -d

# API is running at http://localhost:8080
# Dashboard is running at http://localhost:3000

# Create your first API key
curl http://localhost:8080/v1/auth/setup \
  -H "Content-Type: application/json" \
  -d '{ "name": "my-setup" }'

# Returns: { "api_key": "tfa_sk_..." }
# Add this key to your agent's skill.md and start writing state.
    

What's in the box

Container architecture

Container: tasksforagents-api

API Server

Stateless REST API. Handles all work item operations, claim/release, artifact storage, event generation, and agent registration. Horizontally scalable.

:8080

Container: tasksforagents-web

Web Dashboard

Static frontend. Board view across all agents and projects. No server-side rendering, no session state. Talks directly to the API.

:3000

Container: tasksforagents-db

PostgreSQL

Your execution state. Persisted to a Docker volume. Back it up however you back up Postgres — pg_dump, WAL archiving, whatever fits your setup.

:5432

That's it. Three containers. No Redis, no message queue, no Kubernetes required. Add a reverse proxy (nginx, Caddy, Traefik) for TLS and you're production-ready.

Trade-offs

Single-node vs. Cloud Threadron

Single-node

Cloud

Reachable from any agent or device

You configure

Built in

Execution state backups

You manage

Automatic

Smart Layer (dedup, priority, summarization)

Not included

Included

Portability

One machine only

Any agent, any device, anywhere

Data location

Your network

Our cloud

Cost

Free

$12/mo

Single-node is the right choice for local development, experimentation, and solo workflows where everything runs on one machine. Cloud Threadron is for real multi-agent work — state that travels with your agents, is always backed up, and is reachable from any device or session.

Open source · Apache 2.0 · Single-node Threadron · Docker Compose · PostgreSQL · REST API · No vendor lock-in · Cloud Threadron for distributed work · Open source · Apache 2.0 · Single-node Threadron · Docker Compose · PostgreSQL · REST API · No vendor lock-in · Cloud Threadron for distributed work ·

Start single-node. Scale to cloud when you need it.

Same API, same agents. The only difference is whether your state can travel.

GitHub Repo Cloud Threadron