FAQ

No. By default you get 33 container‑image scans per day — no e‑mail, no forms.

If you later need more, send a blank message to token@stella-ops.org. Our bot sends back a signed JWT that lifts the limit to 333 scans per day. Paste it into your .env as STELLA_JWT and restart the stack.

The quotas protect our public registry and update servers from abuse. 33 scans cover a solo‑dev workflow; 333 cover most SME pipelines. When you hit 90% of daily scan quota in one UTC day the UI shows a gentle reminder and the scan window slows down (throttling) but never blocks.

• If you never request a token: we store your IP address in access logs for 7 days for abuse detection, then hash it.
• If you request a token: we keep the e‑mail + salted token‑ID hash for 7 days, then keep only the hash for quota validation.
• No analytics, no cookies, no localStorage writes on the scanner side.

It’s self‑hosted by default — a Docker Compose bundle spins up Redis, MongoDB and the scanner API on your own node. A managed SaaS option is not on the current public road‑map.

Yes. Download the signed Offline Update Kit (OUK), copy it via USB, then run stella ouk import <file>. The JWT token works offline too — validation happens locally.

In the alpha/beta line plug‑ins are loaded at start‑up only (no hot‑plug support). Each module is a compiled .NET 10 DLL that implements an interface such as IStellaScannerModule or IResultSink.

A signed marketplace and start‑up hot‑load are planned for the v1.0 release.

Yes — see the CI recipes section. Jobs surface the scan result and fail on high‑severity issues.

The Road‑map shows milestones: v0.1 α (late 2025), v0.2 β (Q1 2026), v0.3 β (Q2 2026), v0.4 RC (Q3 2026) and v1.0 GA (Q4 2026).

• GitLab Issues for bugs & feature requests.
• #stellaops on Matrix for real‑time chat.
• Commercial SLA is not planned; community support only.