Menu
Pricing
Pricing that scales with your monitor count
Choose the number of monitors you need, then add status pages, alerts, Ruby ticketing, MCP/API access, and managed support as your service portfolio grows.
Pricing
Pricing that stays as honest as our status pages.
Not on this plan: Faciotech-run incident coordination (that's Managed).
Find your plan
Team fits 22 monitors at 1-minute checks. Team (GH₵ 149)
| What you get | Starter | Team | Managed |
|---|---|---|---|
| Monitors | 10 | 50 | Scoped by quote |
| Check cadence | 5 minutes | 1 minute | 1 minute or agreed cadence |
| Public status pages | 1 | 5 | Client-specific |
| Alerts | Email plus configured routes | Routed through Faciotech support | |
| Response help | Self-serve | Support-assisted | Faciotech incident coordination |
Want Faciotech to run it for you?
Managed monitoring scoped to your stack, with incident coordination by our team.
Make the next step useful
Put pricing that scales with your monitor count into an operating workflow
Connect the guidance to a real service, a named owner, a tested notification path, and a customer-safe communication plan.
What to do next
- Pick a monitor count first instead of forcing your team into a rigid package.
- Scale from free checks to production monitoring, API/MCP access, and managed support.
- Use a custom Government plan when sovereign hosting, private probes, or data residency is required.
Keep the implementation honest
- Start with one customer-facing service, verify the alert path, and publish only the service impact that customers need to understand.
- Do not publish credentials, internal addresses, server paths, or provider configuration.
- Verify the workflow in staging before it becomes part of a production monitoring or communication path.
Product evidence
A real reliability workflow, not a promise deck.
FTStatus earns trust with a product you can inspect and a setup you can test before it becomes part of a customer-critical service.
View live demoA live public experience
Open a real FTStatus status page and inspect the same component, incident, maintenance, and subscription flow your customers will use.
A testable operating loop
Create a monitor, run the check, verify the alert path, publish customer-safe impact, and retain the incident timeline.
Honest capability boundaries
Live, operator-assisted, managed-only, and planned workflows are labelled so buyers can scope the service without hidden assumptions.
Before you choose
Questions buyers ask before setup.
Clear scope now prevents surprise costs, noisy alerts, and public status pages that expose the wrong detail later.
What is pricing that scales with your monitor count for?+
Choose the number of monitors you need, then add status pages, alerts, Ruby ticketing, MCP/API access, and managed support as your service portfolio grows.
What is the safest first step?+
Pick a monitor count first instead of forcing your team into a rigid package. Keep the initial scope small enough to test end to end.
Can Faciotech help implement this?+
Yes. Faciotech can help scope the workflow, configure supported checks and routes, and document the operating handoff when included in the service scope.
Start with monitoring customers can trust.
Begin free with the checks that matter most, then add status pages, alert routes, and Faciotech-managed monitoring as reliability grows. No credit card to start, and local support when you need it.