• Web
  • Server & AI

ZoneHelm

A SaaS product that lets agencies and technical teams monitor the web, DNS, TLS and mail infrastructure behind their clients’ domains from one workspace.

Year
2026
Status
Live · My own product
ZoneHelm panel: domains needing attention, 14-day HTTPS trend and recent outages

ZoneHelm is my own product, built to end the chore of checking a domain's health across separate tools. I handled every step myself: product design, interface, API, monitoring workers, billing and server setup. Once a domain is added, its DNS records, HTTP/HTTPS responses, TLS certificate, mail configuration and the subdomains visible in certificate logs come together in one context.

Architecture

The project is a pnpm monorepo of five separate processes: the marketing site, the customer panel and an MFA-protected admin console are built with Next.js; the API is written with Fastify and Zod. Heavy work is pushed to a BullMQ queue and runs in a dedicated worker process. The data layer is PostgreSQL 17 with Drizzle ORM. DNS, web/TLS, mail, passive discovery and the Cloudflare integration live in separate packages, each testable on its own.

Monitoring

HTTPS checks run every five minutes by default and a full scan every twelve hours. Three consecutive failures open a single incident and two successes resolve it; a retried job is never counted twice. The web check re-validates DNS on every redirect and pins the request to the verified public IP, closing off SSRF. On the mail side it inspects MX, SPF, DMARC, SMTP/STARTTLS, PTR and DKIM selectors. Subdomains are discovered passively from Certificate Transparency logs.

Alerts and Sharing

Outages, recoveries, DNS changes and certificate warnings are delivered to email, Discord and Telegram channels. Channel secrets are encrypted with AES-256-GCM and never appear in API responses. Agencies can publish a public status page for selected domains, and PDF and Excel reports plus scheduled email digests are available.

Commercial Layer

A free tier, three paid plans and add-ons for extra workspaces and status pages are enforced as quotas in the API. Payments run through iyzico, with VAT calculation, payment notices and an invoice queue managed from the admin console. Before launch I prepared Playwright desktop and mobile browser tests, integration tests, encrypted backups and rollback runbooks.

Architecture

Components and the flow between them.

ZoneHelm · ArchitecturePanel → Fastify API; Status page → Fastify API; Fastify API → BullMQ / Redis; BullMQ / Redis → Monitor worker; Monitor worker → DNS · TLS · Mail · CT (Probe); Monitor worker → PostgreSQL; Fastify API → PostgreSQL; Monitor worker → Email · Discord · Telegram (Alert)ClientServiceDataOutsidePanelStatus pageFastify APIBullMQ / RedisMonitor workerPostgreSQLDNS · TLS · Mail · CTEmail · Discord · Telegram
ZoneHelm dashboard on a laptop at night
ZoneHelm dashboard on a laptop at night