renar v0.1.0
partners

Three ways
to stand on Renar.

Renar grows by being extended, deployed, and integrated — and each channel is a contract, not a favor. Here is what each partner shape gets and what it promises.

01

Plugin publishers

the .renarp contract
Your code, your signature

A plugin is a sidecar process in any language speaking JSON-RPC over a Unix socket. Packages are .renarp files with a length-prefixed Ed25519 signature — your key, your release cadence, verified by installs before the manifest even parses.

Caged by default

Default-deny filesystem and exec scopes, render and answer budgets, a Landlock + seccomp cage between fork and exec. Your plugin cannot misbehave its way into the host — which is exactly why operators will install one.

The reference set

Git panel, journalctl explorer, container panel, log viewer ship as reference plugins — patterns to fork, not moats to respect. The panel schema means your plugin renders as a first-class surface.

02

On-prem deployers

your keys, your licenses

Consultancies and platform teams that install Renar for their customers can issue their own licenses against their own issuer key — [license] issuer_public_key plus your own signing ceremony. The entitlement ladder stays enforceable with no vendor connection: offline verification, live re-presentation, witnessed clocks. You become the licensing authority for your installs, deliberately and on the record.

The ceremony is documented, not secret. docs/CEREMONY.md in the source tree covers key generation, baking, registry, and rotation — the same runbook we use, because on-prem partners run the identical machinery.
03

Integrators and resellers

a channel with real leverage

Every surface keeps a JSON twin, the API speaks bearer tokens with ledgered mint and revoke, and /metrics feeds Prometheus — so Renar slots into the monitoring, backup, and identity stacks your customers already run. Resellers carry the signed release channel and support surface to markets we do not reach alone.

Channel terms publish at launch. The partner program, margins, and the contact address stand here when the domain goes live — nothing is promised before it is offerable.