Independent software by Adam Bobowski

Build software you understand and enjoy.

Stario is a philosophy of visible parts, explicit decisions, and direct tools. Server, Hypermedia, and Deploy are three ways to practice it. Use a tool, borrow an idea, or take the approach to another stack.

Explore the practices Read the Stario way

The practices

One philosophy. Three practices.

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.

Stario / Server

Keep HTTP, lifecycle, and telemetry visible from the first route to production.

Ox / Hypermedia

Put behavior beside the HTML it changes. Call the server only when useful.

Orbit / Deploy

Upload the project into a slot, then let its repository hooks run it.

Why it exists

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.

The goal is not to hide HTTP, the browser, or the server. The goal is to make their boundaries pleasant to work with.

Read the story

The Stario way

Take the ideas. Leave the tools.

Stario is one implementation of this philosophy, not a requirement. Apply the same principles with Go, Datastar, rsync, or whatever fits the work.

Read the Stario way