What works, what’s coming, what changed
The one page with the running commentary. Everything else on the site just describes the product; this is where the status lives, and it changes when reality does.
What works today
Catalog, list builder, knowledge
Browse units, build lists against a points cap, read rules notes. Running on our demo system while we sort out permission to publish the much bigger catalogue we’ve already built.
Your collection
Your models, with built and painted tracked per model. Stored in your browser; syncs to your account once it has two sign-in methods.
Game records
Results entered once and agreed by both players. Changes need both of you. Unfinished games get marked abandoned, not scored.
The game library
The list of game systems. If yours is missing, add it — a name and what kind of game it is will do. Systems are retired rather than deleted.
Inbox
Security alerts and requests that need an answer from you. That’s the whole list.
API tokens
Keys with scopes for your own scripts or AI assistant. Everything a key does is logged against that key.
Phase 1 — being finished now
- The pages for clubs, events and game logging — the machinery is live; the screens are being built.
- Photo galleries and uploads, and paint recipes — which paints went on which models.
- Game-system depth for maintainers: authoring your system's knowledge base and academy, formats that tournaments consume, richer scoring.
- MCP access — the token API is live; the connector for AI assistants is being built on it.
- Model identification from photos, for any system whose catalogue ships a labelled reference set.
- The catalogue standard growing an ecosystem: catalogues hosted by their communities, consumed here.
Phase 2 — being looked at, committed to nothing
- Native apps — iOS and Android, for photographing models and running events away from a desk. Second round of development, deliberately.
- Conventions — a collection of events under one banner: one venue, one weekend, many tournaments across many game systems.
- A Discord bot — honestly: no settled purpose yet. Maybe live event updates — round results and matchups posting to a club's server — maybe community links.If you would use one, say what for — this one genuinely depends on what people ask for.
What will not change between phases
Free, no ads, nothing sold, no tracking. Systems are never deleted — only retired, so nothing you logged ever breaks. And publishers get no special machinery because they need none: a games company maintaining their own system here uses the same doors as everyone else — which is exactly the outcome we are building toward.
What changed
In the order it changed, written for someone using the app rather than someone reading the code. Sahul is built on other people's work — see credits.
Version 0.4
6 changes- ChangedApp
Sahul has a new look — new colours, new type, a dark sidebar, and hand-drawn illustrations. This is where the public record starts; earlier versions were the workshop floor.
- ChangedApp
The navigation is organised around how you actually use the app: your profile (top-left, with the inbox bell beside it), then the game system you are learning, then Hobby (collection, purchases, photos), then Play (games, events, communities), then the game library.
- ChangedProfile
Your profile is your home page: things waiting on you, your stats, your clubs and events, your recent games. Account, security and API tokens live in Settings.
- ChangedGames
The games page shows your shared game records with the details that matter on each row.
- NewSettings
Download my data — one button, one JSON file, everything Sahul has of yours. Built on your machine; nothing is sent anywhere.
- ChangedSite
The front page is rewritten, About is new (including why it is called Sahul), and what-works / roadmap / changelog now live together on one page.
Found something still wrong? A wrong photo or a wrong points value is worth reporting even if it feels small — tell us, or use Report an issue inside the app.