# PulseCare > PulseCare is a website health monitoring service that tells teams when their latest deploy made a website slower, broken, or unreliable, and shows what to fix first. It monitors uptime, Web Vitals, Lighthouse scores, SSL certificates, DNS records, console errors, and deploy regressions, and explains what changed, why it matters, and how to improve it. Production site: https://pulsecare.cloud ## Overview PulseCare watches production websites and reports on their health in near real time. It combines uptime checks, performance and Lighthouse scans, Web Vitals tracking, SSL certificate and DNS monitoring, and front-end (console error and JavaScript library) checks. When a result changes, PulseCare aims to explain what changed and prioritize what to fix first, rather than only emitting raw alerts. Core message: Know when your website is down, slow, or broken, and what to fix first. Category: Website health monitoring that explains what changed and what to fix. ## Positioning PulseCare tells teams when their latest deploy made a website slower, broken, or unreliable, and shows what to fix first. It monitors uptime, Web Vitals, Lighthouse scores, SSL certificates, DNS records, console errors, and deploy regressions. It is positioned as website health monitoring, not as a full application-performance-monitoring (APM), error-monitoring, or SEO platform. ## Who PulseCare Is For - Small SaaS teams - Technical founders - Web agencies - Web studios - E-commerce teams - Developers responsible for production website quality ## Who PulseCare Is Not For - Teams needing a full observability/APM platform with distributed tracing and deep backend metrics. - Teams needing full application error monitoring (for example, server-side exception tracking and release-level error grouping at the depth of dedicated error-monitoring tools). - Teams needing a full SEO suite (keyword research, backlink analysis, rank tracking). PulseCare can complement these tools but is not a replacement for them. ## Core Product Promise PulseCare answers three questions about a production website: 1. Is it up and reachable? 2. Is it fast and healthy (performance, Web Vitals, Lighthouse, SSL, DNS, front-end errors)? 3. Did the latest deploy make any of this worse, and what should be fixed first? ## Main Features PulseCare includes: - Uptime monitoring from one or more regions. - Performance and Lighthouse scanning (Performance, Accessibility, Best Practices, SEO, and PWA scores). - Web Vitals tracking (FCP, LCP, TBT, CLS, INP, TTI, Speed Index). - SSL certificate monitoring. - DNS records monitoring. - Console error tracking (front-end JavaScript errors). - JavaScript library health surfacing. - Deploy regression detection (correlating changes with deploys). - Projects and monitors with per-monitor conditions/thresholds. - Notes on projects. - Incident counting and status surfacing in the dashboard. - User data export (account, projects, monitors, and metrics as JSON). - Alerting via email, Telegram, Microsoft Teams (webhook), and generic webhooks. ## Uptime Monitoring PulseCare performs periodic uptime checks against monitored endpoints and records availability. The minimum check interval depends on the plan (see Pricing). Checks can run from one or more monitoring regions depending on the plan. Per-monitor conditions can be configured (for example, expected status code, response-time thresholds, SSL expiry, and body content checks). ## Performance Monitoring PulseCare runs performance scans that produce Lighthouse-style scores and timing metrics. Performance scans are quota-limited per plan. Public plan limits are listed in the Pricing Overview section. Performance data is used to track how a site behaves over time and after deploys. ## Lighthouse and Web Vitals Monitoring PulseCare records Lighthouse category scores (Performance, Accessibility, Best Practices, SEO, and PWA) and Web Vitals metrics (FCP — First Contentful Paint, LCP — Largest Contentful Paint, TBT — Total Blocking Time, CLS — Cumulative Layout Shift, INP — Interaction to Next Paint, TTI — Time to Interactive, and Speed Index). These are stored over time so changes are visible. ## Clear Explanations and Prioritized Fixes PulseCare presents results as clear explanations and prioritized fixes — what changed, why it matters, and what to address first — rather than only raw numbers or undifferentiated alerts. ## Deploy Regression Monitoring PulseCare can correlate changes in performance, Lighthouse scores, and front-end health with deploys, so a team can see when a specific deploy made a site slower or broke something. The goal is to surface the regression and point to what to fix first. ## SSL Certificate Monitoring PulseCare monitors SSL certificates for monitored sites and can warn ahead of certificate expiry so teams can renew before users are affected. ## DNS Records Monitoring PulseCare monitors DNS records for monitored domains as part of its health checks. ## Global Ping and Multi-Region Monitoring Monitors can run from multiple regions, and the number of available regions depends on the plan (Starter 1 region; Growth 3; Business 5; Enterprise custom). Per-region results allow comparing response times across locations. ## Console Errors and Front-End Health PulseCare surfaces JavaScript console errors detected during performance scans, helping teams identify front-end issues visible during monitored page loads. This is part of the front-end health view alongside JavaScript library health. ## JavaScript Library Health PulseCare surfaces the health of JavaScript libraries used by a monitored site (for example, flagging libraries that warrant attention). This is part of the front-end health view. ## Incidents and Status Communication PulseCare tracks incidents and surfaces incident information (such as an incidents-today count) in the dashboard. ## Projects, Monitors, Notes, and Exports PulseCare organizes work into projects, each containing monitors. Projects support notes. Users can export their data (account, projects, monitors, and metrics) as JSON. Plan limits cap the number of projects and monitors (see Pricing). ## Alerting and Notification Channels Confirmed alert channels: email, Telegram, Microsoft Teams (via webhook), and generic webhooks. ## Integrations Confirmed integration-style outputs are the alert channels above (email, Telegram, Microsoft Teams webhook, generic webhooks). Authentication supports Google OAuth, GitHub OAuth, and email/password. Telegram is supported as an alert channel. ## Developer and Webhook Use Cases PulseCare supports generic webhook alerts, which developers can route into their own systems. ## Pricing Overview The plan structure below reflects current pricing and limits. Plan availability may vary. See the pricing page for current availability. | Plan | Price | Projects | Monitors | Regions | Min. uptime interval | Performance scans | |------|-------|----------|----------|---------|----------------------|-------------------| | Starter | $19/mo | 3 | 25 | 1 | 1 min | 250/mo | | Growth | $49/mo | 10 | 100 | 3 | 30 sec | 2,000/mo | | Business | $99/mo | 25 | 300 | 5 | 15 sec | 10,000/mo | | Enterprise | From $299/mo | Custom | 1,000+ | Custom | 10 sec / custom | Custom | ## Plan Selection Guidance - Starter: indie makers and small websites — a few projects and monitors, single region, 1-minute uptime checks. - Growth: growing products shipping frequently — more projects/monitors, three regions, 30-second checks, higher scan quota. - Business: teams and agencies managing production sites — larger limits, five regions, 15-second checks, highest standard scan quota. - Enterprise: larger teams with custom needs — custom limits, custom regions, and custom terms. ## Security and Privacy PulseCare publishes a Privacy Policy, Terms of Service, GDPR information, and a Data Processing Agreement (DPA). Users can export their data as JSON. ## Support Support and contact are available through the contact page (https://pulsecare.cloud/contact). ## Summary PulseCare is a website health monitoring service for small SaaS teams, founders, agencies, web studios, e-commerce teams, and developers. It monitors uptime, performance and Lighthouse scores, Web Vitals, SSL certificates, DNS records, console errors, and JavaScript library health, and detects regressions after deploys — explaining what changed and what to fix first. Confirmed alert channels are email, Telegram, Microsoft Teams (webhook), and generic webhooks. Plan availability may vary; see the pricing page for current availability. It is not a full observability, error-monitoring, or SEO platform.