Menu
Resource · Resources
FTStatus roadmap
A public product roadmap showing what FTStatus is building now, what is coming next, and where customers can request or vote on improvements.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Show shipped, in progress, planned, and under-review product work.
Collect customer feedback for monitors, integrations, MCP tools, and government deployment needs.
Keep public commitments careful: no dates unless Faciotech has approved the delivery window.
Monitor
Live and shipping
Track production-ready capabilities such as core monitors, public status pages, monitor-count pricing, Ruby chat handoff, affiliate pages, and the first FTStatus MCP/API surface once released.
Response time · 24h
182 msAlerting
In progress
Show active work on Watchdog dashboards, private probes, logical-location quorum, Ruby ticket summaries, knowledge hub automation, additional alert channels, and richer admin workflows.
Monitor
Planned and requested
Group future items by Monitoring, Status Pages, Alerting, MCP/API, Government/Sovereign Server, Billing, Affiliate, and Reporting. Each item should have a short summary, target customer, status, and a feedback button.
Response time · 24h
182 msStatus pages
Feedback policy
Customers can request features, vote on planned work, or ask Ruby to open a ticket. FTStatus should avoid promising delivery dates until a feature is approved for release, security reviewed, and scoped by Faciotech.
Make the next step useful
Put ftstatus roadmap 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
- Show shipped, in progress, planned, and under-review product work.
- Collect customer feedback for monitors, integrations, MCP tools, and government deployment needs.
- Keep public commitments careful: no dates unless Faciotech has approved the delivery window.
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 ftstatus roadmap for?+
A public product roadmap showing what FTStatus is building now, what is coming next, and where customers can request or vote on improvements.
What is the safest first step?+
Show shipped, in progress, planned, and under-review product work. 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.
Related pages
Continue building the monitoring workflow.
Put it into practice.
Start free with FTStatus monitoring and branded status pages, wire up the alerts your team needs, and lean on Faciotech support when reliability gets serious. No credit card to begin.