ops.iuhui.site

Managed ops for overseas servers, Web3 nodes, and Docker services

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.

Linux Docker Prometheus Grafana Uptime Kuma Web3 Nodes
Coverage Servers / Nodes / Bots / Panels
Alert Channels Telegram / Lark / WeChat
Deliverables Health Reports + Dashboards
Launch Advice Monitor First, Then Manage

Who Needs This

For teams that already run services, but do not have steady ops coverage

01

Unwatched overseas servers

Disk usage creeps up, swap goes weird, ports stay exposed, and outages are noticed too late.

02

Docker services drift offline

Bots, panels, APIs, and scheduled jobs run in containers without unified monitoring or restart rules.

03

Web3 nodes need constant care

ETH, BTC, EVM, Sui, and Aptos nodes need version upgrades, disk monitoring, and RPC health checks.

04

Small teams lack a full-time SRE

You do not need a full-time ops hire, but you do need alerts, reports, and someone watching the basics.

What You Get

Reusable ops packages instead of one-off firefighting

Server Managed Ops

System checks, basic hardening, Docker status, disk/CPU/memory monitoring, monthly reports, and basic incident handling.

Web3 Node Managed Ops

Sync status, RPC latency, disk growth, client upgrades, abnormal logs, restart strategy, and alert routing.

Monitoring & Alert Setup

Prometheus, Grafana, Node Exporter, Alertmanager, Uptime Kuma, status pages, and notification webhooks.

Node Health Live demo mock
88% Sync
64% Disk
92% Uptime
Docker
RPC
Alerts

Pricing

Clear monthly plans, priced in USD

The first 5 trial clients can start at a discounted rate. Standard pricing applies after the trial period.

Server Check

$49 one-time

A low-risk entry point before monthly managed ops.

  • Read-only server inspection
  • Disk / load / service / port report
  • Docker container status review
  • Basic risk summary
  • Recommended plan and next steps
Starter Ops

$99/mo

For one personal server or lightweight Docker workload.

  • 1 server included
  • Basic system health checks
  • Docker service status checks
  • Basic alerts and monthly report
  • Email / async support
Web3 Node

From $499/mo

For individuals and projects running ETH, BTC, EVM, Sui, Aptos, or similar nodes.

  • Node sync incident handling
  • RPC health checks
  • Disk growth monitoring
  • Client version upgrades
  • Dedicated alerts and monthly reports

Add-ons

Monitoring setup $199-$499 one-time. Extra server +$39-$59/mo. Extra Web3 node +$199-$399/mo. Emergency work $49-$99/hr.

Payment

Monthly plans are prepaid. Early clients can pay by PayPal invoice, Wise, USDT, or local transfer where available.

Boundaries

No private-key custody, no fund management, no profit guarantees, and no 24/7 on-call SLA unless contracted separately.

Plan Helper

Not sure which plan fits?

Use server count, node usage, and dashboard needs to get a rough recommendation. Final pricing depends on actual service complexity.

Recommended Plan Pro From $249/mo

Workflow

From first check to monthly managed ops

Step 1

Scope

Confirm server count, OS, Docker services, node types, alert channels, and security boundaries.

Step 2

Read-only Check

Run basic checks and report disk, load, services, ports, failed units, and recent logins.

Step 3

Monitoring Setup

Install Uptime Kuma / Prometheus / Grafana / Alertmanager and wire alerts to Telegram or Lark.

Step 4

Monthly Ops

Run scheduled checks, alert handling, basic incident response, version upgrades, and renewal reminders.

Automation

Delivery should be scripted, not improvised

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

Start with one server health check

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.