One of a billion, 11:08. One camera move through a field of real screens, narrated by Sue, PractiCAI's Mission Coordinator. Performance audio courtesy of Billy Gilmore and The Grass Is Dead, Suwannee Roots Revival, 2026.
StellarView is in alpha, and this is the statement that goes with it.
It is a platform that builds a company’s whole software operation and then runs it. The cloud, the pipeline, the board, the tests, the documentation and the training films come out of one record, and the same record keeps running after the build is done (1:12).
The film above is the release statement in its own words. Read the rest of this page if you would rather check it than watch it.
The rule the film was made to
Everything Sue says is somewhere in the screens. Each line names the screen that proves it, and the camera goes to that screen while the line is spoken. A line with no screen behind it is a line we had not earned, so it was cut. Two numbers got through without a screen, and they are in the rough list below.
The screens in the field come from StellarView running and from the products it built. We counted them before we said the number out loud, and our first count was too high. Hashing the screens by content found seventy-two duplicates. Counted properly across the repository, there are 391 distinct captured screens (3:48). The film tells you it caught us inflating the count (3:55), because it did.
What it does
It opens any codebase as rings (1:47). A ring pulses where the work is: files nobody has committed, pull requests still open, code named by an issue somebody is working on. It reads the repository while you look at it.
It has three faces for three people (1:26). The Human Interface is where almost everybody works. The JOEY interface underneath it is where the technical work happens. Mission Control is where the Conductor runs the lifecycle.
It builds real products. SprayPath is drone spraying for farms, run as a territory business, with its own cloud, pipeline, board, documentation and films (2:32). We wrote up its sprint in Cyborg SDLC part three.
It runs with people and agents on the same team. Our own team file has ten seats. One is a person, accountable for all of it. Nine are agents. Sue says it at 4:05.
It writes down what it stopped. When every model call is meant to go through Claude Code, a direct call to the metered API is stopped and written to disk, with a timestamp and the line of code that tried it. That file holds thirty-one refusals (6:49).
It made this film. The narration, the screens, the timing and the measurement were produced the way it produces a client’s training films (6:32).
How the film was made
The script is forty beats. Each beat is spoken in the house voice and measured, and the film’s length comes from the voice. A focus window is worked out for each screen from its beat’s timing. Then six browsers each render their own stretch of the film frame by frame, and their files are joined without re-encoding.
Our build log for the cut of 25 October records 19,891 frames, rendered in 858 seconds across the six streams. Splitting the render into six took the whole build from about forty minutes to about twenty. Every frame is a function of its frame number alone, so the same script and the same screens give the same film again.
Rendering runs on the CPU, on purpose. The GPU on the build machine started accepting draw calls and returning black frames. Software rendering is slower and it finishes.
What the alpha offers
We are not selling you StellarView. We are selling you the platform you intended to have (8:53). Your cloud, your pipeline, your board and your documentation, around the hardest thing you need built. StellarView comes with it at the end, as the thing that made it and the thing that keeps making it.
Then we demonstrate it to your people, train your team on it, and leave the platform with you to run (9:17). You own it afterwards. The price is the price of the product, and the building and the delivering come with it. We have not published a price, and this page does not invent one.
The Fleet is the part people underestimate (8:32). Accounts, networks, identity, container services, databases and the portal arrive as infrastructure as code, and the code goes with you.
What is rough, because it is an alpha
- The units that build a product still run as containers on our own machine. The screen behind Sue at 9:00 says so, on the row: a container on this machine, not started.
- At 6:35, while Sue says the film made itself, the screen behind her is our film-model viewer showing an error, because it was opened without a model.
- Two numbers Sue speaks have no screen that shows them. At 4:05 she says the team has ten seats, and at 6:49 she gives the count of stopped calls on disk. Both are true: our team file has ten seats, and the file of stopped calls has thirty-one lines. The camera is on other screens when she says them.
- We have not published a price.
Doubt it, ask for a demo, or dare us
The film ends on one request with three ways to answer it (10:40).
Doubt it. The more you dig, the more real it gets (10:00). A demonstration gets thinner the harder you look. Pick any number on this page and ask where it came from.
Ask for a demonstration, and we will show you the running thing.
Or dare us, with the project nobody has started.
We say in the film that we know of nothing else that stands up the whole operation around the code (10:21). If you know of one, show us. We mean that.
Bring your documents at practicai.org/get. The longer argument for building the whole thing is in Show HN: we breed the whole horse.