Monitor what can break.Know where to look.

Monitor vendor status, website and API uptime, heartbeats from scheduled jobs, and domain and SSL/TLS expiry in one workspace, with configurable team alerts. Statusfield is a software product developed and operated by Cuadrolabs LLC.

Use vendor monitoring to follow incidents a third-party provider reports. Use uptime monitoring to check whether your own public HTTPS website or API returns the response you expect. Use a heartbeat to detect a cron job, backup or sync that stops checking in after successful work. You can combine them in one Statusfield workspace and route their alerts to the people responsible.

Choose your vendors in Statusfield, select supported components or regions, and connect an alert destination. Set rules for the status changes you want to receive. Statusfield brings official incident details and recovery updates into one workspace, so you can investigate without checking each status page separately. Vendor reports do not test your own account or application.

Yes. A provider’s status page may be green while your own URL fails because of an application error, account restriction or configuration issue. An uptime monitor requests your public HTTPS URL and checks its response time, expected status code or range, and optional text or JSON body rules. This can surface a failing response independently of vendor reports; it does not identify the cause or verify a complete login or checkout.

Use a heartbeat monitor. Set how often the job should finish and how much extra time to allow, then add its check-in URL after your job’s success checks. After the first check-in starts monitoring, a missed deadline can trigger your configured alerts. Send /fail to report a known failure without waiting for the deadline. Your code must verify the work: a received ping alone does not prove a usable backup or correct data.

Have your monitoring process send a heartbeat to Statusfield after it completes its checks. If the process stops, Statusfield can detect the missing check-in outside that process and alert through your configured destination. Use a destination that remains available when the monitored system fails. Detection still depends on Statusfield running and the alert channel delivering the message.

Yes. A Statusfield status board shows selected workspace monitors through a shareable link. It can give a client or internal team a focused view without a workspace seat. It is a monitor-backed status view, not a tool for writing and publishing incident announcements. Your team handles client communication. Access protection and branding depend on your plan.

Yes. Create separate monitors for domain registration expiry and SSL/TLS certificate expiry, then configure reminder windows and alert destinations. Your team or existing automation handles renewal.

Capacity is measured in monitors: each selected vendor component or service-wide monitor, uptime check location, SSL expiry monitor, domain expiry monitor or active heartbeat uses one monitor unit. Checking one URL from three locations uses three units. Selecting multiple vendor components can also use multiple units.

Direct subscriptions may be enough if you follow a few vendors and their notifications work for you. Statusfield helps when you want one place to choose relevant components, configure alert rules, and route updates to the people responsible. You’re paying for control over that workflow.

You choose which components and status changes trigger notifications. Follow the regions you use where the vendor supports them, and leave statuses you don’t need without an alert rule. Existing vendor subscriptions stay separate: once you’ve verified your Statusfield setup, review those subscriptions to avoid duplicate notifications.

Yes. Set a destination for each status you want to follow. For example, send major outages to PagerDuty, partial outages to Slack or Microsoft Teams, and degraded-service updates to email. You configure the rules; Statusfield doesn’t decide urgency for you. Available channels and destination limits depend on your plan.

Choose from 7,000+ services in the catalog. Where a vendor reports component or regional status, you can follow those specific dependencies. Check the vendor’s catalog page for available components before setting up your monitors.

Statusfield fits technical founders, small engineering teams and lean IT teams that need vendor incidents, website or API checks, scheduled-job signals and renewal dates in one workspace. It is especially useful when updates need to reach different people or channels. MSPs can share selected monitors on status boards. Keep your APM, logs and browser tests for deeper investigation and complete user journeys. Check vendor coverage and plan limits before choosing a plan.

Basic costs $5/month billed monthly, or $50/year billed annually ($4.17/month equivalent). Starter costs $20/month billed monthly, or $200/year billed annually ($16.67/month equivalent). Pro costs $60/month billed monthly, or $600/year billed annually ($50/month equivalent). Team costs $150/month billed monthly, or $1500/year billed annually ($125/month equivalent). Prices are in USD. Choose by monitor capacity, alert destinations and team access. There is no permanent free plan for new customers.

Pro is our recommendation for small engineering and IT teams coordinating checks, on-call alerts and incident reviews. At $60/month, it combines 40 monitor units, 10 alert destinations and 4 workspace seats with PagerDuty routing, API and MCP access, reports and priority support. Share monitoring responsibility, send relevant changes to chat or on-call, and bring recorded history into your reviews. Reports require at least 30 days of workspace monitoring history. Basic covers a small email-only setup; Starter adds chat and API/MCP access. Team expands capacity to 90 units and 8 seats.

Basic costs $5/month and includes 5 monitor units, unlimited email notifications and 2 email destinations. Mix vendor components, public HTTPS checks, SSL expiry and domain expiry within that capacity. For example, one vendor component, one URL checked from two locations, one SSL certificate and one domain use five units. Slack and Microsoft Teams start with Starter at $20/month. Heartbeat monitoring is available with paid plans and eligible trials.

Logs help you investigate after you know something is wrong. Statusfield adds scheduled checks, missing-job signals and routed vendor updates so your team has a way to find out. Compare the subscription with the time you spend checking status pages, investigating stale data or answering repeated status questions. For illustration, at $60 per hour of team time, 60 minutes costs the same as one month of Pro at $60/month. Use your own costs and trial results to decide whether that tradeoff is worthwhile.

Self-hosted monitoring can fit a team that wants control and can maintain it. With Statusfield, you configure monitors and alert routes while Statusfield runs the hosted checks and maintains supported vendor status integrations. You do not need to host a polling server or maintain a parser for each supported vendor. Compare that ongoing work with the subscription, then check that the available regions, rules and channels cover your needs.

Start with one problem you currently discover too late: a vendor incident, a failing public URL or a scheduled job that stops checking in. Check vendor component coverage, inspect an endpoint response and send a labeled test alert to the person who would act. If heartbeat access is available, use a disposable job to test a missed check-in and recovery after its first signal. Keep production jobs running. For a team workflow, evaluate Pro with the people who share monitoring responsibility. Check your required monitor units, locations, destinations and seats before choosing the plan. A delivery test checks the destination; also verify the monitor's routing rules.

Yes. Send a labeled test alert during setup or test a configured destination from Integrations. Confirm that it reaches the intended inbox or channel before relying on it. You can also review available incident history without waiting for a new outage.

Keep application-level monitoring too. Vendor status monitoring follows official status updates, and endpoint checks test publicly reachable HTTPS URLs. A reachable endpoint does not prove that every authenticated workflow or transaction succeeds.

Eligible first-time customers can try a paid plan for 30 days without a credit card. Add the vendors or public HTTPS endpoints you want to monitor, then test your alert destinations. Continued monitoring afterward requires a paid subscription. Review your selected plan and price before checkout; you can cancel from your account.

Email support@statusfield.com with your questions. We can help you understand component coverage, routing rules, integrations, and which plan fits your team.

Yes. Schedule a demo to walk through Statusfield and discuss your team’s monitoring and routing needs.