English
dashdot Hosting
Watch live CPU, memory, storage, and network usage on a clean, self-hosted resource dashboard.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- mauricenino/dashdot:latest
- Default port
- 3001
How dashdot works
dashdot gathers operating-system information and renders it as a reactive web dashboard. Upstream documentation covers CPU usage and model details, memory utilisation, mounted storage, network throughput and totals, and supported NVIDIA GPU information. Environment variables can adjust appearance and which widgets are visible.
The standard Docker installation is designed to inspect its host by mounting the host filesystem at /mnt/host and running with elevated container privileges. Those settings expose information that an ordinary isolated web container cannot see. The catalogue row declares neither the host-root mount nor privileged mode.
Key dashdot features
Because the catalogue template does not provide the upstream host-access settings, the hosted dashdot page must not be described as a complete view of the underlying hosting node. It can report only the information visible to its own container, and storage or hardware widgets may be absent, incomplete, or limited to container-level data.
dashdot is a current-status dashboard rather than a replacement for alerting, long-term time-series retention, log analysis, distributed tracing, or incident response. No agents are installed on other machines, and the hosting package does not provide a Prometheus stack, notification service, external probes, or access to shared-host metrics.
Who uses dashdot
Operators use dashdot for a quick at-a-glance view of a small machine, lab server, or dedicated environment. It is useful when a visual status page is enough and the deployment can expose the required host interfaces. On shared application hosting, that second condition is intentionally constrained.
Infrastructure teams that need accurate node-level telemetry, alerts, history, service checks, or multi-server dashboards should use a monitoring product designed for those requirements. dashdot’s visual presentation does not compensate for missing access to the system being measured.
Self-hosting dashdot: requirements and cost
The dashboard itself has modest application requirements, but visible statistics depend on what the container can inspect. Browser viewers, refresh activity, enabled widgets, and any available hardware polling shape load. PostgreSQL and MariaDB are Not required, and the catalogue defines no persistent metrics volume because dashdot is not a historical database.
On AvaHost, dashdot uses Plan 1 at €2. The hosted dashdot package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The AvaHost package supplies the dashdot web container and normal platform services, but the catalogue does not mount the host root or grant privileged mode. Treat the page as a container-visible dashboard, not a view of AvaHost hardware or the customer’s other services. No alerts, historical metrics backend, agents, or external monitoring targets are included.
F.A.Q
dashdot starts at €2 on Plan 1. The dashboard application is lightweight, so the entry plan covers ordinary browser viewing. Refresh frequency, concurrent viewers, enabled widgets, and the amount of system information available to the container influence load, but the hosted template is not a full node-monitoring deployment.
No such claim is made. Upstream Docker instructions mount the host root and use privileged mode to collect host statistics. The AvaHost catalogue template includes neither setting, so dashdot can access only container-visible information. Storage, network, GPU, or hardware details may therefore be incomplete or unavailable.
The dashboard can be attached to a custom domain with automated HTTPS. This protects traffic between the browser and the hosted page, but it does not grant the container additional access to host metrics. Keep the distinction clear when sharing the URL with staff or using screenshots in operational documentation.
dashdot is presented as a current system dashboard, and the catalogue defines no historical metrics database. AvaHost applies application updates and schedules platform backups, but there is no promised time-series archive to restore. Use a separate monitoring system when alerts, historical charts, audit records, or long-term capacity analysis are required.