Tell your people before they have to ask.
When email is down or the ERP is about to be patched, the worst part is the silence. TechStat gets the right message to the right people, in the channel they chose, from the first alert to the all clear, so your help desk stops answering "is it just me?"
- No passwords for the people you notify
- Email, Slack, Teams and webhooks
- Maintenance windows that run themselves
- A status page and calendar feed included
- Email & calendar Operational
- Financial system Scheduled maintenance
- Internet › Chicago office Partial outage
- VPN Operational
- Wi-Fi Operational
-
Identified · 10:42 AM
The provider has confirmed a fault on their side and is working on it.
-
Investigating · 10:15 AM
Some people in the Chicago office are seeing slow internet.
Meet people where they already are
From "something's wrong" to "everyone knows"
Three steps, none of them a project.
Add what you run
List your services (email, the ERP, the VPN, each office's internet) and nest them the way you think about them.
Post an event
Open an incident or schedule maintenance in under a minute. Say what's affected, how bad it is, and what people should do.
The right people hear about it
Everyone following those services is told on the channel they chose, and every update after that, until it is resolved.
Built for the way IT actually communicates
Not a generic notification tool: it knows what an outage, a maintenance window and a status page are.
Maintenance that runs itself
Schedule a window once. TechStat reminds people a day and an hour before, announces the start and the finish on time, and puts the work on their calendar. If it finishes early, one click ends it, and everyone is told.
- ScheduledEveryone told
- 1 day beforeReminder
- 2:00 AMWork starts
- 5:00 AMAll clear
The right people, not everyone
Restrict a service, or aim a single event, at a group. Payroll trouble reaches Finance, not the whole company.
Status you can trust
A service's status is worked out from what is really open, never typed in. Two incidents at once can't hide each other, and when the last one closes, the service returns to normal on its own.
A status page people actually use
Current status, history and upcoming work on one page, with an Atom feed and a calendar subscription for Outlook or Google Calendar. Anything restricted to a group never appears on it.
Employees just subscribe
An email address and one click to confirm. They choose the services and channels that matter to them, pause for a holiday, or unsubscribe, all from a personal link. Import your whole directory from a CSV.
Plugs into your monitoring
Let an alert open the event for you. Give each alert an id of your own and retries are safe: the same alert never creates two events, and "resolved" twice is harmless.
$ curl -X POST https://techstat.us/api/v1/events \
-H "Authorization: Bearer tsk_…" \
-d '{ "kind": "incident", "title": "Email is slow",
"services": ["Email"], "severity": "Partial Outage",
"external_id": "datadog-8841", "message": "Investigating." }'Careful where it counts
A message that goes to the whole company deserves care.
- Every change is in an audit log: who did what, when, and from where.
- Webhooks are signed so your systems can verify them, and URLs are checked so nothing can be pointed at your internal network.
- API tokens are shown once and stored only as a hash.
- Two-factor authentication and passkeys for everyone who posts.
- Each organization's data is kept strictly apart from every other's.
Clear messages, in the channel people chose
Plain language, what is affected, and a link to the whole picture. The same event, three ways. (Example messages.)
Slow internet in Chicago: Identified
The provider has confirmed a fault on their side and is working on it. Video calls may drop; wired connections are unaffected.
Affected: Chicago office
See the status pageChoose what you hear about · Unsubscribe
The provider has confirmed a fault on their side and is working on it.
- Affected
- Chicago office
- Status
- Partial outage
{
"type": "incident.identified",
"organization": "Acme Corp",
"event": {
"title": "Slow internet in Chicago",
"status": "Partial Outage",
"services": ["Chicago office"]
},
"message": "The provider has confirmed…"
}Questions, answered
Who is TechStat for?
IT and operations teams who need to tell their own company what is happening: employees, managers, and partner teams. It is built for internal communication, so people follow the services they depend on and hear about nothing else.
Do my employees need an account?
No. They subscribe with an email address, confirm it, and manage everything from a personal link: which services to follow, which channels to use, pause, or unsubscribe. No passwords to forget. Only the people who post events and run the setup have logins, with two-factor authentication and passkeys.
Which channels can people choose?
Email, Slack, Microsoft Teams, and signed webhooks for your own systems. Text messages are built and waiting on US carrier registration, so they are off for now.
Can we keep some things from some people?
Yes. Put people in groups, then restrict a service to a group or aim a single event at one. Anything restricted never appears on the public status page or in its feeds, and cannot change what that page shows.
Can our monitoring open events for us?
Yes. Create an API token and let Datadog, CloudWatch, a script or your CI open, update and resolve events. Give each alert an id of your own and retries are safe: the same alert never creates two events.
Is single sign-on available?
Not yet; it is planned. Today staff sign in with a password plus a second factor, and employees never sign in at all.
Can I try it?
TechStat is in early access. Write to support@techstat.us and we will get you set up.
The next outage is coming. Make it the one people barely noticed.
Say it early, say it clearly, and let your help desk get on with its day.