Hi everyone,
We’re the team behind Mushee, and we’re building Sia Sentinel, a monitoring and reliability dashboard for the Sia network. Sentinel discovers hosts, tracks signals like uptime and latency, and presents those insights in a clear dashboard with transparent reliability scoring so developers and operators can quickly understand network health.
Demo: Sia Sentinel
Repository: Sia Sentinel Repo
Website: mushee
Introduction
Project Name:
Sia Sentinel
Name of the organization or individual submitting the proposal: Mushee
Describe your project.
Sia Sentinel is an operational dashboard for the Sia network focused on host reliability visibility.
After looking more closely at the current ecosystem, we think the right direction for Sentinel is not to replace existing host benchmarking or scoring tools, but to build a cleaner monitoring surface around reliability signals that are often harder to understand at a glance.
The project focuses on discovering hosts, tracking operational signals such as uptime, latency, and incident history, and presenting those signals in a more accessible dashboard for developers, operators, and community members.
The goal is to make it easier to quickly see what is healthy, what is degrading, and what may need attention across the network.
Rather than introducing a new canonical host scoring model, Sentinel is intended to improve visibility, usability, and monitoring workflow around host reliability.
How does the projected outcome serve the Foundation’s mission of user-owned data?
User-owned data depends on storage infrastructure that people can trust.
One part of that trust comes from transparency. If developers and users can more easily understand the operational health of the network, see when hosts are unstable, and track reliability signals over time, it becomes easier to make informed decisions about the infrastructure they rely on.
Sia Sentinel supports that by improving visibility into host health and network reliability. The project is meant to make Sia easier to observe and understand, which helps strengthen confidence in the underlying storage layer that user-owned data depends on.
Are you a resident of any jurisdiction on that list?
No
Will your payment bank account be located in any jurisdiction on that list?
No
Grant Specifics
Amount of money requested and justification with a reasonable breakdown of expenses:
Requested amount: $10,000
Budget breakdown:
- Engineering and development: $7,000
- Design and interface work: $1,500
- Infrastructure and hosting: $1,000
- Testing, documentation, and maintenance: $500
Most of the funding would go toward building the monitoring pipeline, dashboard interface, and open-source project setup.
What is the high-level architecture overview for the grant? What security best practices are you following?
Sia Sentinel is planned as a lightweight monitoring and dashboard application made up of three core parts:
1. Host discovery and data collection layer
The system maintains a registry of hosts and collects operational signals such as uptime, latency, and status changes through scheduled checks and network data sources.
2. Storage and processing layer
Collected data is stored in a database and used to generate host status views, incident history, and simple reliability summaries that can be surfaced in the dashboard.
3. Dashboard and interface layer
A web interface presents host reliability information, operational signals, and incident visibility in a format that is easier to understand and explore.
Planned stack:
- Frontend: Next.js
- Backend/services: Node.js
- Database: PostgreSQL
- Monitoring jobs: scheduled workers / cron-based checks
Security practices include:
- open-source development for transparency
- secure handling of secrets through environment variables
- sanitized API inputs
- rate limiting where appropriate
- careful separation between public dashboard views and internal monitoring logic
The project will avoid unnecessary complexity in the first version and focus on a simple, auditable implementation.
What are the goals of this small grant? Please provide a general timeline for completion.
The goal of this small grant is to build the first working version of Sia Sentinel as a host reliability visibility tool.
Month 1
- host discovery and registry setup
- basic monitoring checks for uptime and latency
- database schema and initial data collection pipeline
Month 2
- dashboard views for host status and network health
- incident history and status-change visibility
- initial reliability summaries and host detail pages
Month 3
- public deployment
- documentation
- open-source cleanup and community feedback
The main goal is to deliver a usable first version that improves visibility into host reliability and network health.
What are your plans for this project following the grant?
Following the grant, the plan would be to improve monitoring coverage, refine how operational signals are surfaced, and make the dashboard more useful as a practical observability layer for the Sia ecosystem.
Possible follow-up work may include:
- multi-region monitoring checks
- better incident tracking and historical views
- public APIs for developers
- deeper integrations with other ecosystem tooling
The long-term goal is to make Sentinel a useful operational visibility layer for the Sia network.
Potential risks that will affect the outcome of the project:
The main risks are:
- overlap with existing tools if the scope is not kept focused
- changes in network APIs or data sources
- scaling monitoring jobs as coverage increases
To manage these risks, the project will stay focused on usability and operational visibility rather than trying to replace existing scoring or benchmarking systems. The implementation will also be modular so that data collection and dashboard features can evolve without requiring a full redesign.
Development Information
Will all of your project’s code be open-source?
Yes.
All code developed for Sia Sentinel will be open-source.
The project may use standard third-party open-source libraries and frameworks such as Next.js, Node.js tooling, and PostgreSQL-related packages.
Any third-party code used will follow the relevant open-source licenses.
Leave a link where code will be accessible for review.
Repository:
Do you agree to submit monthly progress reports?
Yes
Contact info
Email:
[email protected]
[email protected]
[email protected]
Any other preferred contact methods
X / Twitter: https://x.com/mushee_io
