Platform
What our own products run on
Three programs carry everything we ship: the one we write applications in, the one that puts them on the network and keeps them there, and the one that works through what each repository needs next. All three were built here, and how a studio builds what it depends on is the most honest thing you can learn about how it would build yours.
What we run
The platform under our own products
Oxid is on PyPI under Apache 2.0; hive ships as a signed binary for Linux and macOS; agent runs on our own machines and nowhere else. They are on this page because everything we ship stands on them.
Full web applications in pure Python. No JavaScript, no bundler, no node_modules.
oxid.optersoft.com- Python
- Rust
- WebAssembly
The constraint
A team that knows Python should not need a second language, a Node toolchain and a bundler to put an interface in a browser — and every one of those is one more thing a student has to learn before writing the first useful page.
What we built
A fine-grained reactive framework, and underneath it a Python runtime of our own: a bytecode virtual machine written in Rust, compiled to WebAssembly, with the reactive core as native types inside it — and, on the same runtime, the server that renders each page per request. Prerendering writes each route as finished HTML and the browser hydrates it, so a page with nothing interactive on it downloads no runtime at all.
What it does for us
It is what our web applications are written in and what Academy teaches web development with; the site you are reading is built with it, and not one of its pages fetches a line of JavaScript. Apache 2.0, on PyPI —
pip install oxidis the whole install. It was called Frontage until October 2026.The constraint
A studio this size cannot staff a platform team, and cannot absorb downtime either. Every deploy had to become safe enough to do casually — on a weekday, mid-afternoon, without a maintenance window.
What we built
Zero-downtime deploys through graceful fork/exec restarts, TLS terminated in-process, per-VM hardening, and a tier-aware DoS stack in front of the fleet. One gateway fronts every product we run.
What it does for us
Runs everything on this page and every app on the fleet. It ships as a signed binary at hive.optersoft.com, for Linux and macOS; the source is ours and stays that way.
Agent
Our autonomous coder: it works a repository's task list and leaves a branch to review.
- Rust
- Claude
- git
The constraint
A two-person company keeps more repositories than two people can keep current, and most of what each one needs next is written down already — a bug, a version to bump, a page to correct. We wanted that list worked without anyone sitting at it, and without ever letting an unreviewed change reach a branch that ships.
What we built
agent reads a repository's task list, takes the most important task and works it with Claude, starting on a small model and moving to a stronger one only when a turn makes no progress. When the repository's own checks pass it leaves a branch for a person to review, then takes the next task. It runs on our own machines, and a guard in front of every command it issues decides what it may touch.
What it does for us
It is how our repositories keep moving while we teach, write and take on client work — and the way of working that Academy's courses on AI are built on.
Start on it with us
Tell us what you are building and which of this you want to adopt. You hear back from the people who wrote it.
Get in touch