Six decisions that make Luminax feel unlike the rest

Anyone can wire a model to a file writer. The difference shows up in the parts nobody demos: what happens when you close the tab, when a tool fails, when the model is wrong about its own success — and how far the product travels after it builds.

1. The run belongs to the server

Close the tab, switch device, lose signal. The run keeps going, because the browser was never driving it. Come back and the transcript replays exactly, including every tool call and capture in the order they happened.

2. Append-only truth

Every event is written once and never mutated. That is why tool cards, screenshots and reasoning survive reloads instead of dissolving into a summary — the UI folds a log, it does not trust a snapshot.

3. Completion is proven, not announced

A model saying "done" is a claim. Luminax requires evidence — the preview answered, the build passed, the change is visible. Turns end on proof.

4. Real eyes on real pages

Deep page study with interaction, scroll and follow-through, rather than a single hero screenshot. It is why design references translate instead of approximating.

5. Model routing per task

Different work wants different models: fast ones for edits, careful ones for architecture, visual ones for design. Routing is automatic and the cost is shown per message, in credits, honestly. The same Gateway is available to the apps you build — frontier and open-weight families, plus voice, transcription, audio and music — with no keys for you to hold.

6. One project reaches the whole market

Website, mobile app, store submission and the launch material all come out of a single project. Most builders hand you a web app and wish you luck; here the same conversation produces the app on your phone, the store listing, the product video and the page people land on.

7. Exit is a feature

Real repository, standard framework, no proprietary runtime. If you ever want to leave, the door is not locked — which is the only reason to believe anything else on this page.

The measure of a builder is not the first reply. It is the fortieth message on a Tuesday, when the project is real and the stakes are yours.