The machine,
as a market.
Every server fleet has operators, and every operator still drops to a terminal for half their work. Renar's bet is that the terminal and the file tree become first-class web surfaces — with the security model as the product. This page states the thesis and the model; the numbers that belong here will be supplied, never invented.
The thesis
why this, why nowWeb consoles today are hand-built dashboards — each panel a project, each aging on arrival. Renar is a rendering engine for the machine: the filesystem, processes, and any CLI tool become live HTML through one engine, one plugin contract, and a terminal fallback that makes every tool renderable at once.
The reason incumbents amputate exec and shell is that making them safe is hard. Renar's capability architecture — grants, step-up, recording, a hash-chained ledger — turns the dangerous rungs into the selling point regulated buyers actually need.
One static binary, one in-house pure-Rust crypto tree, no CDN, no telemetry, signed everything. For buyers whose procurement asks "what is in your dependency chain," the answer is short enough to read.
The model
open core, signed valueOne AGPL-3.0 codebase. The free build is the complete single-box product — generous on purpose, because an install that runs the free build is an install that knows how to run the paid one. Revenue is the ladder above it: signed builds, the update channel, support, and the multi-box surface — fleet, directory verifiers, recording, full-scope ledger — sold per install, on-prem, with ceilings and tier caps in the signed license itself.
The facts
supplied, never inventedThis section is deliberately unfinished. The following publish the day they are true and reviewed — nothing stands here on projection:
Look closer
the product is the deckThe strongest diligence artifact is the product itself: