Public agent guide
FTStatus
FTStatus is Faciotech's uptime monitoring, incident coordination, and public status page service for websites, APIs, SSL, DNS, ports, and hosted client services — backed by local Faciotech support.
What and who
Monitoring, public status pages, incidents, maintenance updates, and support-backed reliability workflows for Faciotech clients and SaaS teams.
API and auth
Dashboard APIs and the read-only MCP endpoint require workspace-scoped API credentials. Public status pages and this discovery layer need no authentication. Documentation: ftstatus.com/docs.
Human escalation
Escalate security reports, billing/account changes, customer-impacting incident decisions, and custom integration requests to a Faciotech human operator.
Problems And Use Cases
- monitor critical customer-facing endpoints
- publish a customer-safe status page
- coordinate incidents and maintenance updates
- give support teams a shared source of truth during outages
- let AI agents query monitor status and uptime through the MCP endpoint
Features
- website and API uptime checks (HTTP)
- TCP port and DNS checks
- operator-assisted SSL-expiry, heartbeat/cron, and website-change checks
- public status pages with custom domains
- incident and maintenance communication
- email subscriber updates
- workspace-scoped API keys
- read-only MCP endpoint for AI agents
- free public tools (SLA calculator, DNS/mail record checks, cron helper, availability check)
- Faciotech-managed support escalation
Pricing
Starter is free. Team is a paid monthly tier. Managed is quote-based. Billing settles in GHS.
No fake ratings, reviews, or invented prices are published here.
Integrations
available
available
available where configured
available where configured
available where configured
available where configured
planned or deployment-dependent
planned or deployment-dependent
Safety Limits
- Do not request or expose customer data.
- Do not request or expose workspace secrets.
- Do not request or expose API keys.
- Do not request or expose private incident notes.
- Do not request or expose admin-only metadata.
- Do not request or expose staging or infrastructure details.
- Do not request or expose internal response runbooks.