avuru obs v0.3.0 is tagged. v0.2 secured the read side — login, roles, per-project grants, SSO. v0.3 closes the write side and turns the project into something you actually administer.

v0.3.1 is a patch: it fixes the chart's image defaults, which never pointed at the images the release workflow actually publishes. Nothing else changes — no schema migration, no API or configuration surface.

The green module reported energy only where the hardware exposes RAPL — which excludes the overwhelming majority of public-cloud VMs. An opt-in TDP estimator now models CPU power from utilization on those nodes, so a fleet that runs entirely on cloud instances stops seeing an empty /green.

Until now, a gateway believed whatever project a sender claimed. Now you can issue per-project ingest API keys and have the key decide instead — with a default that changes nothing until you are ready.

Projects are no longer only a deployment setting: admins can create, rename and delete them directly in Settings → General, and the switcher updates to match — while the built-in default and config-defined projects stay read-only.

You can now explore a live avuru obs without installing anything: one click on "Try the demo" signs you in as a read-only viewer against a running multi-service app, with real data across every module.

avuru obs now ships secure by default: the hub requires login, users carry fixed roles — Admin, Editor, Viewer — granted per project, and enterprise SSO works with any OpenID Connect identity provider (Keycloak, Microsoft Entra ID, Okta, Google, Dex) — in open source, not behind an enterprise tier, and with no auth proxy to deploy.

avuru obs is AGPL-3.0, and the whole licensing story now lives in one place — what it asks of you (almost nothing), why the project chose it, and how it stays sustainable without gating features behind a paid tier.

avuru obs v0.2.0 is tagged. v0.1 proved the wedge — a live service map in under five minutes, zero app changes. v0.2 makes that install one a real team can run every day: secure by default, modular by design, and four new modules that turn the data you already collect into triage, status and accountability.

The new green module turns the pod→service map you already run into per-service energy (Wh) and carbon (gCO2e) — the numbers ESRS E1 / CSRD and internal sustainability targets ask for, without a spreadsheet estimate or a SaaS that wants your telemetry. Energy is measured by CNCF Kepler (from the CPU's RAPL counters); avuru obs already knows which pod is which service, so it attributes joules to the services on your map. Self-hosted, zero app changes, no external API.