Sanaf AI
Start free
Server Monitoring

Instatus, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Instatus account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Server Monitoring
  • Connects with a key
  • 15 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Instatus is

Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.

You paste in a key from your own Instatus account. It is kept encrypted, and you can withdraw it from inside Instatus whenever you like.

How a run works

One message in, the work done in Instatus.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Instatus. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Instatus account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

15 tools it already has

What it can do in Instatus

These are the ready-made tools your AI employee already has in Instatus. It is not limited to them, but it never has to be taught these.

  • Add Incident UpdatePost a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when no
  • Add Maintenance UpdatePost a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and
  • Create ComponentCreate a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.
  • Create IncidentCreate an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and
  • Create MaintenanceSchedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notifystart, no
  • Get ComponentGet the current health and configuration of one component on an Instatus status page.
  • Get IncidentGet one Instatus incident with its affected components and update history.
  • Get MaintenanceGet one Instatus maintenance with its schedule, affected components, automation settings, and update history.
  • List ComponentsList components and their current health for one Instatus status page, including child components where present. Pass the response's nextcursor back unchanged to fetch another page
  • List IncidentsList incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
  • List MaintenancesList scheduled and historical maintenances for an Instatus status page.
  • List Status PagesList status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
  • Update ComponentChange a component's health or presentation on an Instatus status page.
  • Update IncidentEdit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-compo
  • Update MaintenanceFully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUSGETMAINTENANCE first and pr
Access, and who is in charge of it

You stay the boss of your Instatus account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Instatus account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Instatus is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Instatus and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Instatus

Can an AI employee really work inside Instatus?
Yes. It signs in to your own Instatus account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Instatus?
No. Nothing moves and nothing is replaced. Your records stay in Instatus, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Instatus account?
You paste in a key from your own Instatus account. It is kept encrypted, and you can withdraw it from inside Instatus whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Instatus?
It has 15 ready-made tools in Instatus today, among them Add Incident Update, Add Maintenance Update and Create Component. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Instatus and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Instatus and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Instatus?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Instatus is written down with what it did and when.