Get it

Nothing to sign up for

No account, no trial, no sales call. Pull the image, run it next to a PostgreSQL, and read the architecture while it starts. Everything on this page is free to run for private use.

Where this stands. The server is complete through milestone 0.7 and in active development; the browser interface is at preview stage. What is on this page is what is released — nothing is listed here that you cannot download today. The plan

The server

One image, both ways of running it

# One box
git clone https://github.com/Jersyfi/hubtask.git
cd hubtask
cp deploy/docker/.env.example .env
docker compose -f deploy/docker/compose.yaml up -d

# A cluster
helm upgrade --install hubtask ./k8s \
  -f ./k8s/values.yaml

What comes with it

Multi-architecture amd64 and arm64 from the same tag, so a small ARM box is not a second-class citizen.
Signed, with an SBOM The release pipeline publishes a signature and a software bill of materials with the image.
The web interface included It ships inside the binary; there is no second thing to deploy.
The migrator included Schema changes are applied by a job in the same image, forward only.

releases · checksums and signatures

The clients

Where each one runs

The web interface is part of the server, and the command line client is a release of its own. Both are here today; the installed applications for desktop and mobile are being built.

Client	Platforms	Notes
Web	Any current browser	Served by the instance itself, and included in the binary. Chromium, Firefox and Safari, current and previous major. It needs the network today; the browser client is designed for a best-effort cache rather than for full offline work.
`hubctl`	Linux, macOS, Windows	amd64 and arm64. Apple silicon and Windows on ARM built and published; the whole product from a terminal, and a pipe-friendly `--json`.

support-matrix.md · what is proven by a job

Not here yet: the installed applications. Desktop and mobile clients are planned as shells around the same interface, adding encrypted local storage, the system keychain, an updater and full offline operation. They are not released, so there is nothing to download and nothing claimed about them. Where they sit in the plan

First five minutes

From nothing to a completed task

# Sign in with a personal access token
echo "$TOKEN" | hubctl auth login --url https://tasks.example.org

# A hub, a collection, a task
HUB=$(hubctl container create --type HUB --name "Personal" | awk 'NR==2 {print $1}')
COL=$(hubctl container create --type COLLECTION --parent "$HUB" --name "Errands" | awk 'NR==2 {print $1}')
ITEM=$(hubctl item create --collection "$COL" --type TASK --title "Buy milk" | awk 'NR==2 {print $1}')

# Make it real
hubctl due set "$ITEM" --at 2027-01-10
hubctl remind add "$ITEM" --at -PT30M
hubctl item complete "$ITEM"

Source and releases The operations page

Running it for a business? Free, with everything — Hubtask is open source under Apache-2.0, for any use, offering it to others as a service included. No price exists, and none is asked. The terms