Stario — software you understand and enjoy · StarioStario<br>Server<br>Hypermedia<br>Deploy<br>Blog<br>About

The practices<br>One philosophy. Three practices.<br>Each practice keeps a different part of software delivery in view: the server, behavior in the browser, and the path to production. They work independently. The ideas travel further than the tools.<br>01Stario / Server<br>Keep HTTP, lifecycle, and telemetry visible from the first route to production.

02Ox / Hypermedia<br>Put behavior beside the HTML it changes. Call the server only when useful.

03Orbit / Deploy<br>Upload the project into a slot, then let its repository hooks run it.

Why it exists<br>Software you can still understand.

I built Stario after years as a Python backend developer trying to find a calmer way to make complete web applications.<br>The goal is not to hide HTTP, the browser, or the server. The goal is to make their boundaries pleasant to work with.<br>Read the story

The Stario way<br>Take the ideas. Leave the tools.<br>Stario is one implementation of this philosophy, not a requirement. Apply the same principles with Go, Datastar, rsync, or whatever fits the work.<br>Read the Stario way

Made by Adam with Stario

Server<br>Hypermedia<br>Deploy<br>Blog<br>About<br>Theme

Made by Adam with Stario