The Nuxt server loads fine.
The API subdomain SSL expired three weeks ago.
Vue and Nuxt agencies configure client domains across Vercel, Netlify, and custom VPS hosts — each with independent SSL certificates and CNAME delegations. Nuxt SSR server routes, API subdomains, and staging environments carry separate certificates that expire independently from the client-facing domain. Merlonix monitors every layer so you know before the client does.
No credit card either way — start free, or trial the full workspace.
- Check cadence (Agency)
- 1 min
- SSL pre-expiry alert
- 30 days
- Encrypted DNS lookups
- DoH
- Vendors watched
- 11
Where Vue and Nuxt agencies get caught out
Three failure modes specific to Vue and Nuxt client deployments.
Vue and Nuxt agencies managing client applications across Vercel, Netlify, and custom VPS hosts deal with Nuxt SSR server SSL, staging subdomain expiry, and API CNAME drift that standard uptime monitoring does not catch.
Nuxt SSR server SSL is separate
Nuxt SSR runs a Node server with its own SSL, independent from the client-facing CDN domain
Nuxt agencies deploying client applications in SSR mode run a Node.js server — on a VPS, DigitalOcean App Platform, Railway, or Render — fronted by a CDN or reverse proxy. The CDN layer has its own SSL certificate tied to the client domain CNAME. The Nuxt server has a separate SSL certificate tied to the server hostname or a direct subdomain. When the server-side certificate expires or the CNAME pointing to the server drifts after a host migration, the CDN frontend can continue to serve cached responses while the live Nuxt server behind it is unreachable. Standard uptime monitoring checking the public URL will show the site as up while the Nuxt server is broken.
Staging subdomain SSL expires unnoticed
Client staging subdomains carry independent SSL that agencies stop watching after launch
Vue and Nuxt agencies configure staging environments during development: staging.clientdomain.com pointing to a Vercel preview deployment, a separate Netlify branch deploy, or a VPS environment. The staging subdomain has its own CNAME delegation and its own SSL certificate. After the client site launches, the staging environment stays live but stops receiving active attention. Staging SSL certificates expire on their own schedule — often 90 days for Let's Encrypt — and the CNAME delegation breaks when preview deployments are cleaned up or the host changes. Clients occasionally use staging URLs for internal review. When the certificate expires, the browser warning is the first notification the agency receives.
API CNAME drift after VPS migration
Vue SPAs calling client API subdomains break when a VPS migration drops the CNAME record pointing to the new server
Vue agencies configure client API subdomains — api.clientdomain.com or data.clientdomain.com — pointing to a VPS, DigitalOcean droplet, or cloud instance running a backend API. When clients migrate hosting providers or upgrade their VPS, the old CNAME record pointing to the original server IP is sometimes left in place or updated to a new value that does not match the new server's expected hostname. The Vue SPA continues loading from CDN cache. API calls to the subdomain begin failing with SSL handshake errors or DNS resolution failures. The frontend appears to load correctly while every data request returns an error — a failure mode that takes longer to diagnose than a total site outage because the symptom is partial and the cause is invisible to browser-based uptime monitoring.
How it works
SSL and DNS monitoring across every environment your Vue and Nuxt clients use.
Merlonix monitors CNAME integrity and SSL health for Vue SPA frontends, Nuxt SSR servers, API subdomains, and staging environments from a single dashboard — so agencies get full coverage without manual certificate tracking.
01
Add client domains, API subdomains, and staging environments
Verify ownership with a DNS TXT record on the apex domain. API subdomains and staging environments are added without additional verification. All environments — production, staging, API — are monitored from a single dashboard regardless of which hosting platform each uses. Under two minutes per client to get full coverage.
02
CNAME integrity checks on every monitoring interval
A DNS-over-HTTPS resolver checks every CNAME delegation on every monitoring interval — whether the target is Vercel, Netlify, a DigitalOcean droplet, or a VPS IP. When a client VPS migration drops an API subdomain CNAME, the alert fires within minutes. Staging subdomain CNAME breaks are caught the same way as production breaks.
03
SSL monitoring for Nuxt servers, API subdomains, and staging
Full SSL chain validation on every domain and subdomain independently. A Nuxt SSR server certificate expiry fires 30 days in advance — separate from the CDN domain certificate. Staging subdomain certificates are monitored on the same schedule as production. Domain registration expiry is tracked separately from SSL expiry for every domain.
04
Vendor status for Vercel, Netlify, and Cloudflare
Merlonix monitors Vercel, Netlify, and Cloudflare platform status alongside client SSL and DNS. When a Netlify deployment incident causes custom domain resolution failures across multiple Vue client portfolios, you see the vendor event before clients report individual symptoms.
What the numbers mean for Vue agencies
Monitoring built for multi-environment Vue and Nuxt client portfolios.
Vue and Nuxt agencies managing client portfolios across Vercel, Netlify, and custom VPS hosts need SSL and DNS monitoring that covers production, staging, and API subdomains — and catches breaks before clients notice.
< 10 min
Time from DNS change to alert — catches CNAME drift on API subdomains and staging environments before Vue SPA data calls start failing
30 days
SSL expiry warning lead time — covers Nuxt SSR server certificates, API subdomain certificates, and staging SSL independently
11 vendors
Upstream services monitored — Vercel, Netlify, and Cloudflare included for cross-client incident correlation on Vue portfolios
250 assets
Maximum monitored domains on the Agency plan — covers production, staging, and API subdomains across a full Vue and Nuxt client roster
Pricing
Flat monthly fee. Every environment and subdomain included.
No per-domain charges. No per-environment fees. Pick the tier that fits your Vue client count and add staging and API subdomains without billing surprises.
Starter
For individual Vue developers managing a small client portfolio.
$19/ month
- 15 monitored assets
- 3 seats
- 5 min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Team
For Vue and Nuxt agencies with production, staging, and API subdomains across multiple clients.
$79/ month
- 60 monitored assets
- 10 seats
- 1 min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Agency
For agencies with a full Vue and Nuxt client roster across Vercel, Netlify, and custom VPS hosts.
$199/ month
- 250 monitored assets
- Unlimited seats
- 1 min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Compliance
For regulated-vertical teams that need continuous, audit-ready evidence.
$699/ month
- 500 monitored assets
- Unlimited seats
- 1 min check cadence
- SSL + DNS + vendor monitoring
- Email + Slack alerts
Beyond uptime
More than a 200 OK on every client site
The same account also watches the infrastructure and reputation layers a standard uptime check never reaches — each a live check you can turn on.
Turn monitoring into revenue
Resell client-ready reports as your own
Monitoring doesn’t have to be a cost line. Package the branded report and white-label status page as a deliverable in your retainer — the tooling underneath stays invisible, so to the client the work is yours.
Reports under your brand
Hand each client a polished SSL, DNS, and security report carrying your agency’s name and logo — not ours.
Status pages on their domain
Publish a live status page at status.theirbrand.com with automatic TLS and no “Powered by Merlonix” badge.
Your margin to keep
You pay one add-on cost and package it into the retainer you already bill. The markup — and the margin — are yours.
Common questions
Frequently asked questions
Do I need DNS or registrar access to my clients’ domains to monitor them?
No. Merlonix monitors from the outside in — it probes each domain’s public SSL certificate, DNS records, WHOIS/registration data, and HTTP responses the same way a browser or DNS resolver would. You add an asset by its hostname; no access to the client’s registrar, DNS provider, or servers is required.
What does Merlonix actually check on each site?
Every monitored asset gets continuous SSL-certificate (expiry, issuer, and chain changes), DNS-record, domain-registration/expiry, and uptime monitoring by default. You can also enable infrastructure and reputation checks a standard uptime monitor never reaches — security headers, DNSSEC/DANE, domain-hijack/registrar-lock, blocklist, and cron/heartbeat monitoring — each a live check you turn on per asset.
How often does it check, and how do alerts reach me?
Checks run on your plan’s cadence — as often as every 1 min on Team and above, and every 5 min on Starter. When a certificate, DNS record, registration, or response changes, you get an alert by email and Slack. Alerts fire on real state changes between definitive checks, not on a transient blip.
How much does it cost, and is there a free option?
Yes — there is a free $0 plan (no credit card) to watch a small number of assets, and paid plans start at $19/mo (Starter). You can also start a 14-day full-workspace trial with no card. See the pricing grid above for the assets, seats, and check cadence on each tier.
Know when a Nuxt server certificate breaks before the client's Vue app stops loading data.
Add your first Vue or Nuxt client domain in under two minutes. Production, staging, and API subdomains are covered from the same dashboard. 14-day trial, no card required.