Unwatched overseas servers
Disk usage creeps up, swap goes weird, ports stay exposed, and outages are noticed too late.
ops.iuhui.site
Server health checks, node maintenance, monitoring alerts, and basic incident handling for solo builders, small teams, and Web3 projects. Less midnight firefighting, more visible and repeatable infrastructure.
Who Needs This
Disk usage creeps up, swap goes weird, ports stay exposed, and outages are noticed too late.
Bots, panels, APIs, and scheduled jobs run in containers without unified monitoring or restart rules.
ETH, BTC, EVM, Sui, and Aptos nodes need version upgrades, disk monitoring, and RPC health checks.
You do not need a full-time ops hire, but you do need alerts, reports, and someone watching the basics.
What You Get
System checks, basic hardening, Docker status, disk/CPU/memory monitoring, monthly reports, and basic incident handling.
Sync status, RPC latency, disk growth, client upgrades, abnormal logs, restart strategy, and alert routing.
Prometheus, Grafana, Node Exporter, Alertmanager, Uptime Kuma, status pages, and notification webhooks.
Pricing
The first 5 trial clients can start at a discounted rate. Standard pricing applies after the trial period.
A low-risk entry point before monthly managed ops.
For one personal server or lightweight Docker workload.
For small teams with multiple services, dashboards, and weekly checks.
For individuals and projects running ETH, BTC, EVM, Sui, Aptos, or similar nodes.
Monitoring setup $199-$499 one-time. Extra server +$39-$59/mo. Extra Web3 node +$199-$399/mo. Emergency work $49-$99/hr.
Monthly plans are prepaid. Early clients can pay by PayPal invoice, Wise, USDT, or local transfer where available.
No private-key custody, no fund management, no profit guarantees, and no 24/7 on-call SLA unless contracted separately.
Plan Helper
Use server count, node usage, and dashboard needs to get a rough recommendation. Final pricing depends on actual service complexity.
Workflow
Confirm server count, OS, Docker services, node types, alert channels, and security boundaries.
Run basic checks and report disk, load, services, ports, failed units, and recent logins.
Install Uptime Kuma / Prometheus / Grafana / Alertmanager and wire alerts to Telegram or Lark.
Run scheduled checks, alert handling, basic incident response, version upgrades, and renewal reminders.
Automation
The first version can start with Linux inspection scripts and Docker Compose monitoring templates, then grow into Ansible-based automation.
#!/bin/bash
echo "===== System Info ====="
hostnamectl
uptime
echo "===== Disk Usage ====="
df -h
echo "===== Docker Containers ====="
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}" 2>/dev/null
echo "===== Failed Services ====="
systemctl --failed
Contact
Send your server type, running services, Docker usage, Web3 node status, and preferred alert channel. The first step is assessment, not rushing into managed ops.