Auteur Intelligence — Status
Last updated: 2026-11-06
In plain words. This is a static status page. It is not backed by an uptime monitor — the owner checks each component by hand and updates this page when something changes. The JSON snapshot has its own timestamp. If you suspect something is down and this page has not caught up yet, email hello@auteurintelligence.com.
1. Components
| Component | State | Last verified |
|---|---|---|
| Website (auteurintelligence.com) | Verification due | No current operational check recorded |
| Founding-beta application form | Verification due | No current operational check recorded |
| Auteur Cloud (hosted) | Limited staging; not publicly launched | 2026-11-06 (repository record) |
| Community (Skool) | External; verification due | No current operational check recorded |
Auteur Cloud (hosted) has a limited staging deployment on Hetzner. The public paid service has not launched. This status does not assert whether customer data has entered staging. See the Privacy Policy's §2, How Auteur runs for what that means today.
Community (Skool) is a separate company's service, included with every Auteur seat (see the community page). We report what we can see as a member; we do not operate it, and an outage there is Skool's to fix, not ours.
2. Incident history
No incidents have been recorded since this page was published. When something breaks, we will add an entry here with the date, what was affected, and when it was resolved.
3. How this page is updated
This page is updated manually, by the owner, until an automated check replaces the "last verified" dates with something that runs on its own. There is no external uptime vendor behind it.
A machine-readable snapshot of this page is published at
/api/status.json, so a client can poll it instead of scraping this
page. It is a separately dated manual snapshot, not a live endpoint. Check its update timestamp
when using it.
4. Incident ownership and update cadence
During an incident, the platform owner is the incident lead until a named backup accepts the handoff. The lead posts the first notice here, acknowledges incoming support reports, and updates this page at least every 60 minutes while customer impact continues. If this site cannot be published, hello@auteurintelligence.com is the authentication-independent fallback. The incident record must name the affected audience, the next update time, and the operator who acknowledged the handoff; resolution includes a final status update.
5. Related pages
- Support — how to reach us if something here looks wrong.
- Privacy Policy