RFC: OmaStat — Privacy-First Community Hardware & Ecosystem Intelligence Platform (Cloudflare Worker + D1)

[ozdil]

Summary & Vision

We would like to propose and contribute OmaStat (github.com/ozdil/omastat), an open-source, privacy-first community hardware survey and ecosystem intelligence platform designed natively for the Omarchy ecosystem.

As many in the community may know, the omastat.omarchy.org domain has long represented the missing piece of the puzzle: a community-driven, transparent counterpart to the Steam Hardware Survey, purpose-built for modern Linux desktops and Wayland environments.

We have fully implemented, tested, and simulated the complete serverless backend and interactive dashboard matching the exact tech stack of omacom/omarchy-plugin-marketplace (Cloudflare Worker + D1 SQLite). The repository is ready to be transferred to omacom or deployed under omastat.omarchy.org.

---

Why Omarchy Needs OmaStat: Strategic Long-Term Value

Beyond simply knowing "how many systems are out there," a community-owned hardware survey unlocks transformative capabilities for Omarchy:

1. Targeted Subsystem & Compositor Optimization (No More Guesswork)

   • Core maintainers and contributors can make data-driven decisions: What is the real GPU landscape (NVIDIA proprietary vs NVK, AMD RADV, Intel Arc/Xe)?
   • How widespread are multi-monitor setups, HiDPI (4K fractional scaling), and high refresh rate displays (144Hz–360Hz VRR)? Compositor polish and driver fixes can prioritize what users actually run.
   • Are users adopting ARM64 (e.g. Asahi Linux, SBCs), or can we safely raise the baseline to x86-64-v3?

2. The "ProtonDB / Steam Survey" Effect for Hardware Compatibility

   • Prospective users looking to buy a new laptop, GPU, or display can browse OmaStat to see which hardware configurations (Archetypes) deliver the best out-of-the-box performance and highest stability on Omarchy.
   • It transforms community telemetry into a crowdsourced hardware buying and compatibility guide.

3. Leverage with Hardware Vendors (OEMs) and Potential Sponsors

   • Approaching Linux-friendly vendors (Framework, System76, Lenovo, ASUS, etc.) with verified aggregate metrics (e.g., active daily systems, hardware demographic trends) opens doors for tier-1 OEM support, pre-installed Omarchy editions, and hardware loan programs.

4. Performance & Version Regression Tracking

   • As new Omarchy releases or kernel transitions land, OmaStat can track benchmark score trends (via plugins like omarank) and memory usage distributions across versions, catching silent performance regressions early.

5. Pioneering "Ethical Telemetry" in Linux

   • Mainstream Linux distributions frequently face backlash whenever telemetry is introduced. Omarchy can set the industry standard: 100% opt-in, zero tracking IDs, zero PII, verifiable client & server source code, and public SQLite aggregations.

---

Privacy Architecture: Zero-PII & ODG Compliance

In strict adherence to the Omarchy Developer Guide (ODG) and Marketplace Security Baseline:

• Local Battlestation ID (Strictly Private): Clients generate a deterministic salted hash (e.g. OMA-A8F7-EAA5) stored solely in local client state (~/.config/omarchy/omarank/state.json). It is never transmitted over the network.
• Build Archetype Signatures (Public Aggregates): Instead of device fingerprinting, clients transmit high-level archetype signatures (e.g. OMA-U7-ARC-31G-240H representing Core Ultra 7 + Intel Arc + 32GB RAM + 240Hz).
• Zero PII / Zero IP Logging: No MAC addresses, serial numbers, usernames, or IPs are stored in Cloudflare D1. Edge rate-limiting protects against abuse without persisting client identifiers.
• Payload Boundary: Payloads are validated against a strict JSON schema with an enforced 16 KiB size limit.

---

Architecture & Tech Stack

• Runtime: Cloudflare Worker (TypeScript) — zero operational cost, zero maintenance serverless architecture matching omacom/omarchy-plugin-marketplace.
• Database: Cloudflare D1 (SQLite) with pre-aggregated buckets (omastat_archetypes, omastat_submissions, omastat_metrics_summary).
• Dashboard: Lightweight interactive UI (src/dashboard.html) designed with Omarchy's dark theme palette, featuring real-time breakdowns of GPUs, RAM tiers, screen resolutions, refresh rates, CPU distributions, and benchmark percentiles.
• Client Integration: Seamlessly integrates with existing plugins such as ozdil.omarank (already published on the marketplace), with open REST endpoints (POST /api/v1/survey, GET /api/v1/stats) available for any community client or CLI.

---

Repository & Handover

The complete implementation, migration scripts, tests, and documentation are available at:
👉 https://github.com/ozdil/omastat

We are happy to:

1. Transfer the repository ownership to the omacom organization whenever the team is ready.
2. Assist with Cloudflare D1 binding, deployment, and DNS routing to omastat.omarchy.org.
3. Iterate on the schema, metrics, or UI based on feedback from maintainers and the community.

Looking forward to hearing thoughts, feedback, and ideas from the team and community!