renar v0.1.0
the oss core

Free means
the whole box.

The free build is not a demo with the good parts greyed out. It is the complete single-box product: the full read/write/exec/pty surface, accounts, grants, plugins, and the audit ledger — under AGPL-3.0-only, forever.

01

What's in the free build

everything a single box needs
One root, whole surface

Read, write, exec, terminal — the complete capability ladder on one served root, with per-account grants and step-up re-proof on the dangerous rungs.

Accounts and credentials

Engine-local accounts with passkeys, password + TOTP, and PAM import; sliding sessions; API tokens for scripts. Secrets hashed, never cleartext.

The ledger

Hash-chained, mutations-scope audit log. Every write verdict that matters, in a chain whose tampering is detectable.

Plugins

The full out-of-process plugin contract — signed packages, Landlock cage, default-deny scopes — exactly as the Enterprise build runs them.

Trash, history, events

Deletes are reversible; edits keep shadow history; listings and tails stream live over SSE under an admission budget.

Shares

Expiring read-only links with an optional unlock password — /s/<secret>/…, hashed at rest, revoked from the manage page. Free, like doors should be.

The WebDAV mount

/dav/<label>/ — Class 1 plus exclusive LOCK, riding the same grants, trash, history and ledger as the browser. Mount it in your file manager; edits land in the same chain.

Media previews

Video and audio render inline with honest fallbacks; images and PDF as before. No plugin, no converter service, no CDN.

Any tier declared

Tier is posture, not pricing: an OSS install may declare T0 through T4. Only a signed license can cap a tier.

02

The license, said plainly

AGPL-3.0-only

The whole tree — both editions, one codebase — carries AGPL-3.0-only. We chose the AGPL precisely because network use should confer the same freedoms as distribution; if you serve it, its users hold the source rights the license grants.

What that means in practice: run it, study it, change it, self-build it — including the Enterprise edition against your own issuer key. The commercial ladder (see pricing) applies to the licenses we sign, not to your freedom to compile. We think that honesty is worth more than a no-compete clause a rebuild routes around.
Public source hosting is decided at launch. The repository URL will stand here the day the domain goes live — we will not link a placeholder into the wild.
03

Where it stands

0.1.0 — the spine, complete

Every phase below is built, tested, and running in the current tree — each closed with its evidence in the tracker.

P0 — hardening

Content-attack baseline: escaping, CSP, symlink policy, request caps.

P1 — the auth spine

In-binary hybrid-PQ TLS acceptor, accounts (passkey/TOTP/PAM), sliding sessions, step-up, grants, the hash-chained ledger.

P2 — write path

PUT/DELETE/rename/mkdir, trash, uploads, editor profiles — riding grants and the ledger.

P3 — terminal & exec

argv-only exec allowlists, tmux-backed PTY, session recording, the guarded capability.

P4 — find & measure

Content search, du scans and the cleaner, live refresh, metrics.

P5 — plugins

Out-of-process SDK, Landlock/seccomp cage, signed packages, reference plugins.

P6 — fleet

Signed envelopes, fleet cards, the verifier set, offline revocation, break-glass.

P7–P8 — auto-render · pipeline

Schema-driven panels, the plugin gallery tooling, and the five-stage CI gate that re-proves it all.

  • Write-shares — the bit is reserved in the format; no edition mints it, by decision.
  • LSP-backed linting — deliberately last; the editor profiles carry highlighting today.
  • Office-document previews — video and audio render inline today; office formats stay behind an optional converter until it earns its place.
04

Build it yourself

one command, offline-friendly
console — from the source tree# the free build (default features)
$ cargo build --release -p renar

# the enterprise edition
$ cargo build --release -p renar --features enterprise

Releases also ship as signed artifacts you can verify before installing — the shipped binary carries its own verifier. The full walk-through, including the hardened systemd unit, is in the docs.