Two hundred and fifty-six applications. All of them yours.
The software people run their work and their lives on should not be rented, mined for data, or switched off when someone else changes their mind. So we are building the alternative — one application at a time, until there are 256 of them.
What every one of them has in common
Not a style guide. A set of promises we do not intend to break.
-
Yours to run
It installs on your own machine, with one command. No account to create, nothing phoning home, no seat you pay for.
-
Yours to read
Every line is open, and written to be read — because software you cannot inspect is software you are only trusting.
-
Yours to keep
Your data stays on your disk. Nothing we do later can take away the copy you are already running.
Shipping now
All six are installable today, and all six run entirely on your own hardware.
Paco
001Describe what you want built, and an agent writes it — in a sandbox on your own machine, on its own branch, ending in a pull request you review.
Read more →
Docket
002Customer support you host yourself. Every message in one place, nothing slipping through, and your customers’ words stay with you.
Read more →
Kanbanica
003Project management you host yourself. Workspaces, sprints, and tasks with real-time collaboration — no SaaS in the loop.
Read more →
Schduled
004Scheduling and bookings you host yourself. Share a link, set your availability, and let invitees pick a time — on your own server.
Read more →
Shapio
005A feedback and feature-voting board you host yourself. Collect ideas, let users vote, and track a public roadmap — under your own domain.
Read more →
Next.js Starter
006A production-ready Next.js starter template with TypeScript, Drizzle ORM + PostgreSQL, pgBoss job queues, and the DaisyUI design system.
Read more →
Brainer
007Indexes your code and your prose into one graph, so changing a function shows you the documentation and landing-page copy that just became a lie. Runs locally, no API key.
Read more →
Next
007250 to go. Each one replaces something you currently rent, and each one ships the same way: open, installable, and yours.
Every product, by these rules
The constraints we set ourselves are the same across all 256. They are why the set holds together as one system rather than a pile.
- Self-hosted
- Open source
- No account
- One command
How you install it
Each one installs the way that suits it, on hardware you control. Nothing here needs an account.
Debian and Ubuntu packages
One signed APT source serves every Stack256 package, so it is one line and one key however many of them you run. apt.stack256.org lists what is in it today.
# add the repository, once
curl -fsSL https://apt.stack256.org/stack256-archive-keyring.gpg \
| sudo tee /etc/apt/keyrings/stack256-archive-keyring.gpg > /dev/null
echo "deb [signed-by=/etc/apt/keyrings/stack256-archive-keyring.gpg] \
https://apt.stack256.org stable main" \
| sudo tee /etc/apt/sources.list.d/stack256.list
sudo apt update && sudo apt install paco
Container images
Products that ship as an image run anywhere a container does — Docker Compose, Coolify, Dokploy, Kubernetes. Each repository documents its own compose file.
docker pull ghcr.io/stack256org/kanbanica
docker pull ghcr.io/stack256org/schduled
docker pull ghcr.io/stack256org/shapio
Why 256
Because a handful of good open-source tools is a hobby, and a complete set is an alternative. Two hundred and fifty-six is enough to run a small company on without ever renting software again — and it is a number large enough that we cannot get there quietly, or alone. If you want to help, every repository is open.