AppsStatus Page

Autessa Status Page

Status page software that keeps customers calm.

Autessa Status Page is a hosted status page and changelog that works from day one. Customers see live component status, 90 days of uptime history and every incident update. Your team posts incidents and maintenance from one console, release notes draft themselves from merged pull requests, and a person approves them before they go live. Because it runs in Autessa, you can shape every part of it to how your company works.

Start free
  • Status page
  • Incident communication
  • Scheduled maintenance
  • Component status
  • Uptime history
  • Incident history
  • Changelog
  • Release notes
  • AI changelog
status.yourcompany.com
SAMPLE
All systems operational
Updated Nov 3, 2026, 9:41 AM PST. This page refreshes every minute.
Web app
Sign in, dashboards and settings
Operational
90 days ago2 of 90 days with an incident or maintenanceToday
API
REST API and webhooks
Operational
90 days ago1 of 90 days with an incident or maintenanceToday
Payments
Checkout and invoices
Operational
90 days agoNo incidents in 90 daysToday
Latest release notes · Nov 2Approved
Bulk export for reports
Drafted from 14 merged pull requests. Approved by a person.

The short answer

What is Autessa Status Page?

Autessa Status Page is status page software with incident communication, scheduled maintenance, uptime history and a built-in changelog. It is one product with two halves: a public status site for your customers and Status Admin, a staff-only console for your team.

A status page is the public page that tells customers whether your service is working. Autessa's answers in one sentence, then shows each component, the last 90 days, and the full story of every incident. Next to it lives your changelog, the public record of what you shipped, drafted for you each night and never published without a person's approval.

Autessa runs its own status and changelog on it. See Autessa's own status page.

For your customers

The public status site

  • Live status banner, refreshed every minute
  • Status for every component
  • 90-day uptime bars
  • Incident pages and monthly history
  • Public changelog

For your team

Status Admin

  • One-click component status
  • Report and update incidents
  • Schedule maintenance
  • Edit and approve release notes
  • Reviewers and repositories

What makes it different

A status page that cannot lie by accident

Every status page can post an incident. These are the things Autessa Status Page does that most do not.

Smart component restore

Resolving one incident never hides another

When you resolve an incident, its components go back to Operational, except any component that another open incident or maintenance still affects. Status Admin tells you which stayed.
  • On by default, and easy to untick
  • The same check runs when maintenance completes or is canceled
  • Reopening an incident puts its components back
How smart restore works →
Resolving "Delayed webhook deliveries"SAMPLE
  1. Resolved update posted
    Affected: API, Notifications. Restore box ticked.
  2. Other open events checked
    "Database upgrade" is in progress and affects API.
  3. Notifications → Operational
    Nothing else affects it.
  4. API stays Under maintenance
    Still affected by the open maintenance window.
  5. Confirmation
    "Update posted. 1 component(s) stay affected by another open event."

AI changelog drafts

Release notes written overnight, for customers

Every night an AI writer reads the pull requests merged the day before in the repositories you chose, and drafts release notes in plain language: New, Improved and Fixed. Internal work, refactors and reverted changes are left out.
  • Runs at 1:00 AM Pacific, or on demand for any past day
  • Never names people, customers, internal systems or vulnerabilities
  • Keeps the original draft and the source pull requests for review
How drafting works →
Tonight, 1:00 AM PacificSAMPLE
  1. Yesterday: Nov 2
    No entry yet for that day.
  2. 23 pull requests merged in your organization
    14 in the repositories you switched on; 3 are automated dependency updates.
  3. AI writer drafts for customers
    Groups related changes, drops internal work, writes New, Improved, Fixed.
  4. Draft saved: "Bulk export for reports"
    State: Waiting for approval. Source pull requests attached.

Human approval gate

AI drafts. People publish.

No changelog entry reaches the public page until a person selects Approve and publish. The server refuses to show anything that is not approved. Unpublish, skip a day, or restore it, with every action stamped.
  • Confirmation with a safety checklist before publishing
  • A weekday 4:30 PM reminder email to your reviewers
  • The nightly job can only create drafts
How approval works →
Status Admin · Changelog · Nov 2, 2026
SAMPLE
Publish this entry?

It appears on the public changelog right away, under Nov 2, 2026. Your unsaved edits are saved first.

Check that it names no customers, people, internal systems or security details.

Not yetApprove and publish

Reviewer reminders

Autessa Status Page emails your changelog reviewers every weekday afternoon with the drafts waiting for approval, so release notes never pile up.

Repository selection

Autessa Status Page lets you choose exactly which repositories feed the changelog, through a read-only GitHub connection.

Access and audit trail

Autessa Status Page keeps writes in a staff-only console, lets the public page read only public fields, and stamps every post with who made it.

Product tour · for your customers

Every screen of the public status site

Always current, and readable by anyone without signing in.

status.yourcompany.com · Delayed webhook deliveries
SAMPLE
Delayed webhook deliveries
MajorResolved · Sep 30, 2026, 1:12 PM to 3:27 PM PDT · Lasted 2 hours 15 minutes
APIPartial outage
NotificationsDegraded performance
  1. Resolved3:27 PM PDT

    All delayed webhooks have been delivered and delivery times are back to normal.

  2. Monitoring2:40 PM PDT

    A fix is in place. We are watching delivery times and sending the backlog.

  3. Identified1:48 PM PDT

    We found a slow queue worker and are rolling out a fix.

  4. Investigating1:12 PM PDT

    Some webhooks are arriving late. We are looking into it.

status.yourcompany.com · Changelog
SAMPLE
November 3, 2026
Bulk export for reports
New
  • Export any report to a spreadsheet in one click.
  • Saved filters can now be shared with your team.
Improved
  • Dashboards load faster when you have many widgets.
Fixed
  • Dates in exported invoices now match your time zone.
Show older release notes

Product tour · for your team

Every screen of Status Admin

A staff-only console with sortable tables everywhere, plain confirmations, and who-and-when on every post.

ScreenWhat it does
OverviewWhat customers see right now, a status picker for every component, open incidents and maintenance, and drafts waiting.
ComponentsSortable list; add, edit, order, hide or remove each part of your service.
IncidentsSortable list by title, status, impact, affected, started and resolved.
Report an incidentTitle, impact, status, affected components with their severity, and the first update.
Incident detailFacts, Post an update, restore components, Fix wording and Edit details.
MaintenanceSortable list of windows; Schedule maintenance with start, end, components and notice.
ChangelogDraft a day, Write an entry, and every entry with its state, pull request count and approver.
Changelog entryEditor with live preview, original AI draft, source pull requests, Approve, Unpublish and Skip.
SettingsHow the changelog works, changelog reviewers, and the repositories that feed the drafts.
Status Admin · Overview
SAMPLE
Overview
Open status pageReport an incident
Some systems are affected
Components · change a status here and it shows on the status page at once
Web app
Changed Nov 3, 2:06 PM
Degraded performance
API
Changed Oct 30, 4:12 PM
Operational
Payments
Changed never
Operational
Active incidents
Slow responses in the web appIdentified Started Nov 3, 2:06 PM · Web app
Maintenance
Database upgradeScheduled Nov 8, 1:00 AM to 1:30 AM
Changelog2 waiting for approvalDrafts are never published until someone approves them.
Status Admin · Report an incident
SAMPLE
Incidents
Report an incident
It shows on the status page as soon as you post it.
Title
Slow responses in the web app
Impact
Minor
Status
Investigating
Web app · Degraded performance
API · Partial outage
Payments
Each component you pick changes to the status you choose here.
First update
We're looking into reports of slow page loads in the web app.
CancelPost incident

How it works

How does an incident play out on Autessa Status Page?

  1. Step 1

    Report it

    One form: title, impact, status, each affected component with its severity, and the first update. The page changes at once.

    Report an incident →
  2. Step 2

    Update it

    Investigating, Identified, Monitoring. A line at each step; fix any wording later without a second post.

    Incident updates and lifecycle →
  3. Step 3

    Resolve it

    Components go back to Operational, except those another open event still affects. The page shows how long it lasted.

    Smart component restore →
  4. Step 4

    Keep the record

    The incident joins the 14-day list, the monthly history and the 90-day bars, with its own page forever.

    Incident history →
Incident lifecycleSAMPLE
Incident status
InvestigatingLooking into itIdentifiedCause foundMonitoringFix in placeResolvedOver
Impact
NoneMinorMajorCritical
Maintenance lifecycleSAMPLE
Planned work
ScheduledAnnouncedIn progressUnder maintenanceCompletedRestored
Called off
ScheduledCanceledLeft out of history

The changelog, overnight

What happens between 1:00 AM and your morning coffee?

At 1:00 AM Pacific, Autessa Status Page reads yesterday's merged pull requests in the repositories you switched on, and an AI writer drafts customer-facing release notes. By morning the draft is waiting in Status Admin, with the source pull requests attached. A person edits it, approves it, and it appears on your public changelog.

  • One entry per day, never overwritten
  • Days with nothing merged get no entry
  • Draft any past day on demand, or write one by hand
  • Weekday 4:30 PM reminder to your reviewers
  • Read-only GitHub access through a sealed secret
Status Admin · Changelog · Nov 2, 2026
SAMPLE
Nov 2, 2026Waiting for approval
Drafted Nov 3, 1:02 AM · Edited Nov 3, 9:14 AM by jordan@yourcompany.com
Skip this daySaveApprove and publish
Not published. Edit the wording, then approve it. Customers never see a day nobody approved.
Wording
Bulk export for reports
### New
- Export any report to a spreadsheet in one click.
- Saved filters can now be shared with your team.

### Improved
- Dashboards load faster when you have many widgets.

### Fixed
- Dates in exported invoices now match your time zone.
Preview · how it reads on the status page
Bulk export for reports
New
  • Export any report to a spreadsheet in one click.
  • Saved filters can now be shared with your team.
Improved
  • Dashboards load faster when you have many widgets.
Fixed
  • Dates in exported invoices now match your time zone.
Changelog review for Tue, Nov 3
SAMPLE
From Status · To jordan@yourcompany.com

Hi Jordan,

2 drafts are waiting for approval: Oct 31 and Nov 2.

9 pull requests were merged today. They will make up the draft for Nov 3.

Open the changelog

This email only reminds. Nothing is published until someone approves it.

Everything inside

Every Status Page topic and feature

Everything the status page and changelog do, by topic.

01 / 05

Public status page →

Autessa Status Page gives customers one calm, always-current page that answers "is it me or is it you?" with a status banner, component status, 90-day uptime bars and every incident update.

02 / 05

Incident communication →

Autessa Status Page turns incident communication into three moves: report it, post updates, resolve it, with component status kept in step automatically.

03 / 05

Scheduled maintenance →

Autessa Status Page announces planned work before it happens and flips the affected components to Under maintenance only while the work is in progress.

04 / 05

Changelog and release notes →

Autessa Status Page drafts your changelog from the day's merged pull requests and never publishes a word until a person on your team approves it.

05 / 05

Status Admin and access →

Status Admin is the staff-only console where your team runs the status page, and the public page can only ever read what is meant to be public.

Use cases

Who uses a status page and changelog?

Engineering and on-call

Tell customers once, then get back to fixing it

Report an incident in one form while you investigate, post a line at each step, and resolve it with components restored for you. No one has to remember to turn the lights back to green.

Support and customer success

Send one link instead of a hundred replies

Point customers to the incident page, which updates itself, and to the history when someone asks what happened last month.

Product and engineering managers

Release notes that write themselves and wait for you

Every morning there is a draft of yesterday's changes, written for customers. Edit, approve, or skip the day; a weekday email says what is waiting.

Operations and platform teams

Plan maintenance so nobody notices

Announce windows ahead in everyone's time zone, flip components to Under maintenance only while the work runs, and close it out cleanly.

Security and compliance

An honest, dated record with a safe public side

Give reviewers 90 days of bars and a monthly history, keep the public page read-only by design, and know who posted every update.

Marketing

A steady stream of what is new

A public changelog next to your status, with the latest entry teased on the status page, and nothing published that a person did not approve.

Use cases by role and industry →

Integrations

What does it connect to?

GitHub, read-only, for changelog drafts; email for reviewer reminders; and Autessa apps, agents and AutessaDB underneath, so you can extend it like anything else you build in Autessa.

GitHubEmailAI AgentsAutessaDBAutessa apps
All integrations →

Security

Is the public page safe?

Yes. The public site is read-only and returns public fields only; Status Admin is staff-only and stamps every post with who made it; and AI drafts cannot publish. Autessa's security program is documented in the Trust Center.

Security and permissions →

Compare

Looking at other status page tools?

Fair, job-by-job comparisons with the status pages teams evaluate most.

Autessa vsAtlassian Statuspage →Autessa vsInstatus →Autessa vsBetter Stack →Autessa vsincident.io →

FAQ

Questions about Autessa Status Page

What is Autessa Status Page?

Autessa Status Page is status page software with a built-in changelog. Customers get a public page with live component status, 90-day uptime history, incident pages and release notes; your staff run it from Status Admin, where they post incidents, schedule maintenance, change component status and approve changelog entries.

What does the public status page show?

An overall status banner, current incidents, maintenance in progress and coming up, every visible component with its status and 90 days of daily bars, the last 14 days of incidents, a monthly history and the latest release note. It refreshes every minute and shows times in each visitor's own time zone.

How does the changelog get written?

Each night an AI writer reads the pull requests merged the day before in the repositories you chose and drafts customer-facing release notes in New, Improved and Fixed sections. A person edits the draft and approves it; only then does it appear on the public changelog.

Can an AI draft be published by mistake?

No. The nightly job can only create drafts. Only a person in Status Admin can approve an entry, and the public page checks approval on the server before showing anything.

Which incident statuses does it use?

Investigating, Identified, Monitoring and Resolved for incidents, with an impact of None, Minor, Major or Critical. Maintenance moves through Scheduled, In progress, Completed and Canceled.

What happens to components when I resolve an incident?

They go back to Operational automatically, unless another open incident or maintenance still affects them. Those stay as they are, and Status Admin tells you which were kept.

Who decides what customers read?

Your team. Status changes are posted in Status Admin, so what customers read is always what a person decided to tell them.

How do customers follow an incident?

The public page refreshes itself every minute, and every incident page has its own link you can share with customers in one message.

Can it run on my own domain?

Yes. The public status site is an Autessa app published on a domain you choose, such as status.yourcompany.com. Autessa runs its own status at status.autessa.com.

Does it work out of the box?

Yes. Add your components and your status page is live, with incidents, maintenance, history and a changelog ready to go. Because it runs in Autessa, you can shape it to how your company works: the components and wording, the repositories that feed release notes, who reviews them, and the look of the public page.

Who can post incidents and approve release notes?

Staff who can open Status Admin. Visitors to the public page can only read. Every incident, update and changelog entry records who created, edited or approved it, and when.

All systems operational

Give customers one page they can trust.

Live status, honest history, and release notes that write themselves but never publish themselves. Ready out of the box, and yours to shape in Autessa.

Start free

100% customizable, code and all

Make Autessa Status Page fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours