All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Status Page System
Start now
More

Features

Industries

Reference

More

Status Page System · Available now

Keep service status and incident communication together.

Status Page System keeps the operational record of services, their public components, incidents, incident updates and audience-specific public messages in one place. A service owner defines the service; an incident coordinator records an interruption, identifies the affected service and asset, and assigns a person to investigate.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen incidents
Status Page System · Incidents

Open incidents

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
API latency rose in west regionPayment processing
16 Oct
Upload retries increasedAdmin console
26 Oct
Add
Medium2
Sign-in requests timed outPayment processing
27 Oct
Reporting jobs stopped processingReporting dashboard
04 Nov
Add
High1
Billing callbacks were delayedPayment processing
22 Oct
Add
Critical1
Search results lagged updatesCustomer sign-in
23 Oct
Add
API latency rose in west regionIncidents · INC-79775
Low
StatusOpen
ServicePayment processing
Assigned toClara Nguyen
Opened at16 Oct
Public update approvedINC-79775 · API latency rose in west region

Communications Reviewer approves the incident-linked message before publication.

Waiting for Communications Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
13
Roles with set permissions
6
Reports and dashboards
8
Features

Status your team can explain

Every feature works on the same records. Pick one to see the screen your team works in.

Services and components

Keep service ownership and visible component status connected.

  • Service ownership
  • Component status
  • Operational context
  • Services
  • Public components
  • Incidents
  • Changes
Explore services and components
OverviewActive services
Status Page System · Services and components

Active services

Services

New
Service nameCriticalityStatusOwner
Customer sign-inLowActivePavel Novak
Public APIMediumActiveTaro Sato
Payment processingHighActiveClara Nguyen
Notification deliveryLowActivePavel Novak
Reporting dashboardMediumActiveElena Voss
6 of 6 records
Customer sign-inServices · SRV-52586
Low
StatusActive
OwnerPavel Novak
Example screen with sample data
Process

From interruption to customer update

Service incident to public update ships ready to use. One step needs a named approval before the work moves on: Public update approved (Communications Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Service defined

    Name the service and the person responsible for it.

    API latency rose in west regionINC-79775 · Service Owner
    Service definedBy Service Owner

  2. Component listed

    Show the customer-facing part of that service.

    API latency rose in west regionINC-79775 · Service Owner
    Component listedBy Service Owner

  3. Incident opened

    Record the effect, priority and investigator.

    API latency rose in west regionINC-79775 · Incident Coordinator
    Incident openedBy Incident Coordinator

  4. Incident investigated

    Keep attributed findings with the incident.

    API latency rose in west regionINC-79775 · Incident Coordinator
    Incident investigatedBy Incident Coordinator

  5. Public update approved

    The Communications Reviewer checks the wording and audience.

    API latency rose in west regionINC-79775 · Communications Reviewer
    Public update approvedBy Communications Reviewer
    ApprovalCommunications Reviewer approves the incident-linked message before publication.

  6. Update recorded

    Retain the message and publication time with the incident.

    API latency rose in west regionINC-79775 · Communications Reviewer
    Update recordedBy Communications Reviewer

Start with Incident response

Inside a record

Connect monitoring and delivery

Open any incident to see its incident updates, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Status, Service, Assigned to and Opened at.

  2. 2
    Incident updates

    Each line is linked to this incident.

  3. 3
    Who works on it

    Service Owner, Incident Coordinator and Communications Reviewer, each with their own permissions.

  4. 4
    Process stages

    Incident opened and Incident acknowledged, with the role that acts.

  5. 5
    Approvals

    Public update approved, with who decides.

Open incidentsAPI latency rose in west region
Status Page System · Incidents

API latency rose in west region

Payment processing · Low

Log activity
1
Record details
StatusOpen
ServicePayment processing
Assigned toClara Nguyen
Opened at16 Oct
2
Incident updates

API latency rose in west region

NameOccurred atUpdate text
Sign-in alert acknowledged13 OctOn-call engineer acknowledged the alert.
API traffic shifted15 OctTraffic moved to the healthy pool.
Payment queue drained23 OctPayment queue depth is falling.
Incident updates
6
3

Who works on it

  • Service OwnerManage Services, public components, Assets
  • Incident CoordinatorManage Incidents, incident updates
  • Communications ReviewerManage public updates
4

Process stages

  • Incident openedIncident Coordinator
  • Incident acknowledgedIncident Coordinator
5

Approvals

  • Public update approvedCommunications Reviewer
    Approved
Example screen with sample data
Approvals

Review the message before it goes out

A message reviewer should check incident facts and audience before publication; a change decision should happen before implementation.

OverviewApprovals
Status Page System · Overview

Approvals

Signed in as Communications Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-81964API latency rose in west region
    Payment processingRequested by Admin
    Low3dActions
  • CHN-99289Sign-in requests timed out
    Public APIRequested by Admin
    Medium1dActions
  • CHN-40589Billing callbacks were delayed
    Reporting dashboardRequested by Admin
    High5dActions
  • CHN-63018Search results lagged updates
    Public APIRequested by Admin
    Low6dActions

Who approves what

DecisionApprover
Public update approvedThe Communications Reviewer checks the wording and audience.Communications Reviewer
Approve public updatesCommunications Reviewer
Approve ChangesChange Manager
3 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Status Page System to the work that is theirs. Pick a role to see what it starts with.

Admin

Configures users, people and service ownership.

  • Manage Users, People, Services
  • View integration receipts

Roles and permissions

Reports

Read the service history

Review component condition, incident timing and communication history.

Overview
Status Page System · Overview

Status Page System dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Incidents by status

How far records got this quarter

StageReachedStep
Open45
Acknowledged1840%
Investigating528%
Resolved120%

Number of incidents by status

Sample counts per stage

100
-10Open
0Acknowledged
10Investigating
-30Resolved
-10Closed
Example screen with sample data
  1. 01Component status by service

    Group component status under each service to locate current degradation.

  2. 02Incident priority and status

    Compare priority with the current incident state and assigned person.

  3. 03Incident acknowledgment and resolution

    Compare opening, acknowledgment and resolution dates by service.

  4. 04Public update chronology

    Read publication times and audiences alongside their linked incidents.

  5. 05Planned change windows

    Review scheduled start and end dates by service and risk.

  6. 06Request completion

    Compare request dates, due dates and completion dates with status.

  7. 07Problem investigation

    Group current problem states by service and owner.

  8. 08Integration receipt outcomes

    Review received, applied, rejected and failed events by provider.

All reports and dashboards

Who it's for

Built around your service operations

See how Status Page System fits your kind of team.

SaaS platforms

Explain service interruptions across a customer-facing product.

Managed IT services

Coordinate status for services operated by an IT team.

Internal service teams

Give staff a shared record for service interruptions and notices.

Controls

Keep incident and public facts aligned

Each stage of service incident to public update names the role that acts and the status it records, so a change is never anonymous.

OverviewService incident to public update
Status Page System · Process

Service incident to public update

Each stage, the role that acts and the status it records

Process stages
9
Approval steps
1
Roles involved
3
Tables touched
6
Incident acknowledged
Incident Coordinator
StatusOpen → Acknowledged
RecordsIncidents
Incident investigated
Incident Coordinator
StatusAcknowledged → Investigating
RecordsIncident updates, Incidents
Incident resolved
Incident Coordinator
StatusInvestigating → Resolved
RecordsIncidents
Service incident to public update
  1. Start
    Incident acknowledgedOpen → Acknowledged
    Incidents
  2. Step
    Incident investigatedAcknowledged → Investigating
    Incident updates
  3. Approval
    Public update approvedCommunications Reviewer
    Public updates
  4. Step
    Incident resolvedInvestigating → Resolved
    Incidents
  5. Step
    Incident closedResolved → Closed
    Incidents
Example screen with sample data

See each stage in detail

AI agent

An assistant for the on-duty team

Give your team a grounded way to inspect incidents and prepare updates.

It can

  • Incident Coordinator: Summarize open incidents by service, priority and assigned person before a handoff.
  • Service Owner: Compare component condition with incidents and planned changes for the same service.
  • Communications Reviewer: Draft a concise message from a named incident and its recorded updates for human review.
  • Change Manager: Show the scheduled window, risk and rollback plan for changes awaiting review.

Stays with a person

  • A person decides whether a component state represents the actual service condition and whether a public message is ready.
  • The agent should identify the supporting records and ask for that decision.
  • It should not treat a receipt outcome as proof of service recovery or publish wording solely because it can draft it.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Status Page System
  • Monitoring source
  • Public destination
  • Subscriber delivery
  • Event source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Services and components4
  • Incidents5
  • Public communication5
  • Changes and maintenance4
  • Requests and problems5
  • Assets and receipts4
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Map services

    Agree on service names, criticality and owners. Identify the components customers should recognize.

  2. Set access

    Link People to Users and test the intended work of each role before using production incidents.

  3. Load context

    Add representative assets and current service references. Review change and request status meanings with their owners.

  4. Connect communication

    Choose the public destination, monitoring source and subscriber channel. Check the audience and review handoff.

  5. Rehearse a case

    Open an incident, acknowledge it, record an update, review public wording, record publication and close after recovery.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Status Page System.

All questions
How do I get started?

Click Get started, then use Proto to configure Status Page System for your business. Start with a service owner, a customer-facing component and a rehearsed incident.

What does a component represent?

A component is the visible part of a service that customers recognize. It carries its own current status and display order while linking back to the operating service.

How do we record an incident?

Choose the affected service and asset, set priority, assign a person and record the opening time. Add acknowledgment, investigation updates and resolution as the work progresses.

Where do public messages go?

A public update is linked to an incident and records its audience, reviewer and publication time. Choose the public destination and subscriber channel during implementation.

How do we handle maintenance?

Use a change with scheduled start and end, risk and rollback plan. Review the change before implementation and check the visible component condition during the window.

Can we track requested work?

Yes. Service requests link a requester and service to requested, due and completion dates and a decision state.

How do we investigate recurring problems?

Open a problem for the service, assign an owner and retain the problem statement and root cause as the investigation develops.

What do integration receipts tell us?

They show the provider event identifier, received time and handling outcome. Check the service and incident separately before changing customer status.

Who reviews public wording?

Assign a Communications Reviewer to check the incident facts and intended audience, then record the approving person with the update.

Set up Status Page System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appStatus Page System

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.