Spotcraft / Showcase / Sokobanko
Sokobanko
The classic box-pushing puzzle in the browser. Play at once, no sign-up, and your best results are saved.

What it is
Sokobanko is Sokoban: push every box onto a goal, and you can't pull. It has 159 levels that unlock in order, played with the keyboard or by dragging the board. You play in the browser, and when you solve a level the server replays your moves before it saves your best.
What Spotcraft does for it
Guest accounts
A visitor becomes a guest of the server's user pool on their first solved level, with no sign-up. The pool answers on sokobanko.app itself and its cookie lasts a year.
Database schema
Levels and results live in the schema app_sokobanko of Spotcraft's Postgres. Spotcraft runs the image's migrations before a new version starts.
Deploys from CI
Merging to main builds the image, then CI calls the app's deploy hook. The hook's token can change the tag and nothing else.
Nightly backups
At 03:00 UTC the schema and the app's settings go to Cloudflare R2, kept for 30 days.
No downtime
A new version starts next to the old one and takes traffic once its health check passes. A version that never turns healthy never gets traffic.
Analytics without cookies
One call to spotkit's analytics() loads the instance's tracker. It counts visits without cookies, and Your data has a switch to turn it off.
Its own domain
sokobanko.app took over its DNS records from the dashboard, behind a Cloudflare Tunnel, and www redirects to it.
Hardened container
A read-only filesystem, a non-root user, 512 MB and one CPU, and security headers from Caddy.
By the numbers
From the Spotcraft dashboard.
- Memory
- to come
- of a 512 MB limit
- Uptime
- to come
- over 30 days
- Deploy
- to come
- from the deploy hook to live
- Image
- to come
- compressed, amd64
The story
Sokobanko began as a question more than a game. Sokoban’s rules fit in one sentence, which leaves room for the product questions: can people play with zero clicks, keep their progress without signing up, and can the server trust a result the browser sends?
The answer to the last one shaped the whole app. The game runs in the browser, so every move is instant, even on a phone. When you solve a level, the browser sends your moves and the server replays them with the same rules code before it saves your best. A forged result has to be a real solution, and that is just playing the game.
The first version ran as a demo on another host. On 8 November 2026 it was rebuilt for Spotcraft 0.2 and went live at sokobanko.app: a plain Postgres database instead of a hosted one, guests from Spotcraft’s kit, a distroless read-only image, and CI that pushes it to Docker Hub. The first deploy never turned healthy, because the app was added without a database. The message said so, and ticking the box fixed it.
It has grown with Spotcraft since. Releases go out from CI through the deploy hook, with no downtime. On 19 November it moved into the server’s user pool with the dashboard’s Move button, and guests kept their progress and their cookies. One rule makes all of that safe: migrations only ever add, so an older version can always run on a newer database.
Stack
Nuxt 4
Vue pages, rendered on the server, and the API that checks solutions.
PixiJS 8
Draws the board, with a camera that follows the player on big levels.
Drizzle ORM
Levels, results and migrations in Postgres.
@kodentuzo/spotkit
Reads the guest from the user pool's session.
Tailwind CSS 4 and Spotstrap
The look, in light and dark.
TypeScript rules package
The same game rules in the browser and on the server.

