We moved DCon off a third-party SaaS (ThingsBoard Cloud, Professional Edition — per-device billing, ~$100–300/mo) onto a DCon-owned, DCon-branded custom monitoring platform running on our own infrastructure — with a capability no standard tank-monitoring vendor has: live hazard-risk fusion.
DigitalOcean droplet (Ubuntu 24.04) running Docker. Dedicated box, isolated from all other DCon systems.
Neon — managed serverless PostgreSQL 17. Our own project, our own dcon schema. No vendor lock-in.
Node/Express API + zero-framework single-page ops UI, fully DCon-branded. Containerized, one-command deploy.
The entire ThingsBoard tenant was copied read-only into our own Postgres. ThingsBoard is never written to and still runs in parallel. An hourly cron keeps our data current.
The platform reads SignalCommand's signal database read-only, scoped to weather / energy / cyber, US-only, all severities — so operators watch threats escalate. Each signal deep-links into SignalCommand's live map.
Everything is version-controlled in a private GitHub repo with infrastructure-as-code, so a fresh operator can reproduce the whole stack from scratch. Nothing lives only on a laptop.
js2733/dcon-rmc (private) — site + platform/platform/dcon-app — the custom platformplatform/infra — Docker Compose, bootstrap/backup/upgradeplatform/scripts — export · import · repoint · telemetryFleet KPIs, plus per-site dashboards — radial gauges, alarm tables, mini-maps and trend charts (the native replacement for ThingsBoard's per-site dashboards).
Colored topographic map with GPS-plotted sites; device grid with type filters, search, live analog/relay/signal readings.
Real threshold alarms computed from telemetry (e.g. analog-high vs. configured limit), trend analytics across any device and metric.
Live weather/energy/cyber hazard feed with escalation view and one-click deep-links into SignalCommand's map.
Fleet composition by hardware/profile — CBW controllers, drilling rigs, oil-blending, and more.
Authenticator-app MFA (TOTP), self-hosted, encrypted transport, private by default.
DCon Platform reads SignalCommand's hazard signals (read-only) and surfaces them against our sites — weather, energy, cyber, US, all severities, escalation-ordered, deep-linked to the SC map.
DCon telemetry surfaced inside SignalCommand as a licensed "DCon Network" map layer/tab that customers subscribe to — a revenue channel using SignalCommand's existing tiering. Additive; no SC change until approved.
Net effect: DCon becomes the only tank-monitoring platform that pairs live asset telemetry with real-time hazard intelligence — "which of your sites is about to be hit, and by what."
| Phase | Capability | Value |
|---|---|---|
| next | Public exposure behind Cloudflare Access (SSO + MFA) at app.dcon-rmc.com | Customers & field staff log in from the marketing site |
| next | Per-customer isolation / RBAC — customers see only their sites; staff see the fleet | Multi-tenant SaaS you can sell |
| then | Direct device ingestion (MQTT) → retire ThingsBoard entirely | Full ownership, no interim engine |
| then | Alerting — Email / SMS / voice on out-of-parameter + hazard proximity | Matches the brochure promise; prevents spills |
| then | Geofenced hazard-to-site matching + auto-dispatch | "Hailstorm 40 min from Wagner → page operator" |
| later | Reporting/exports, audit logs, mobile, SLA/HA (multi-node + backups) | Enterprise procurement & security checklist |
app.dcon-rmc.com → droplet + auto-HTTPS) or Cloudflare Tunnel (no open ports)? — required to wire the marketing-site login.We turned a rented, per-device SaaS into a DCon-owned platform — same views and management, but ours: cheaper, more secure, and doing something competitors can't. The data is liberated into our own database, the stack is reproducible from Git, and the differentiator (hazard fusion) is already live.