ADoorYour data account Get your account

Keep an incident log

What broke, when, who handled it, what caused it and what you did about it. During the next incident, an agent can check whether it has happened before.

Use cases All use cases

For builders

How to connect ChatGPT and Claude to the same data How to give an AI agent safe, scoped access to data A database for vibe-coded apps, with access built in

AI and engineering

Keep a daily work log Keep a prompt library for Claude, ChatGPT and Cursor Let agents build on each other’s findings Run a task queue for your agents Share agent traces across a team Share research notes Track eval results over time Start an experiment tracker Keep a model training log Keep feature flags and config agents can read Keep bug reproductions and test cases Record deploy and release history Keep an inventory of API keys and services Start a dataset registry Collect standup notes from assistants Keep an incident log Log benchmarks and latency measurements Track GPU and compute spend Start a labeling and annotation queue

Personal

Keep a side-project idea backlog Start a habit tracker Start a reading log Track what you’re learning Track subscriptions Start a budget tracker Start a movie and TV tracker Start a home inventory Keep a plant care log Keep a car maintenance log Plan your travel Keep a tasting journal Track a collection Keep notes on the people you know Track job applications Keep a vocabulary list Track important documents Keep a food log Start a training log Keep a log of your own numbers Keep a schedule of what is due and when to refill Start a recipe collection Keep a list of things to buy Share a pet care log Keep a daily journal Keep gift ideas and birthdays

Business

Track consulting time Track freelance clients and invoices Track fundraising Start a lightweight issue tracker Back an internal tool Store a customer-facing app’s data Plan a content calendar Collect customer feedback and feature requests Manage event attendees and sponsors Report from many sources Start a customer list Track sales deals Keep a customer support log Track hiring Start an employee directory and onboarding checklist Track inventory Track orders and suppliers Start an asset and equipment register Track partners and resellers Track contracts and renewal dates Keep a price list and build quotes

Collaborative

Split expenses Share a research reading list Plan an open-source project roadmap Build a shared world-building bible Plan a house renovation Start a shared household list Share a household chores rota Keep a family schedule Track kids’ activities Plan a trip with friends Plan a wedding or party Run a book club Run a sports team or club Run volunteer and community sign-ups Run a student group project Start a neighborhood tool-lending list Share a weekly meal plan Write babysitter and caregiver handover notes Plan a shift schedule Plan a carpool rota Share a packing list Coordinate help for a parent

An example

@ADoor Incident: API latency spike from 14:02 to 14:31, about 8% of requests timed out. Cause: a missing index after the 1.42 migration. Follow-up: add a migration check for index coverage.

ADoor Added 1 entry to Incidents and 1 to Follow-ups

Incidents

IncidentStartImpactCause
API latency spikeOct 20 14:02~8% timeouts, 29 minMissing index after 1.42
Login errorsOct 3 09:15SSO users, 12 minExpired certificate

What you can ask later

  • “Have we had an incident like this before?”
  • “Which follow-ups are still open?”
  • “What was our total downtime this quarter?”
  • “Which incidents were caused by migrations?”
  • “Chart incidents per month by cause.”

Who can see what

  • On-call engineers add incidents and timeline updates.
  • Everyone in engineering reads every incident.
  • Customer success reads the impact and status fields, without internal notes.
  • An alerting script opens an incident entry through the HTTP API.

How it compares with incident.io or PagerDuty

During the live response, use incident.io or PagerDuty: paging, escalation, status pages and Slack channels per incident.

The long-term memory is where ADoor helps. Postmortems and follow-ups are structured and searchable, an agent can check past incidents during a new one, and plain SQL answers trend questions.

How to start

  1. Sign in to ADoor, then add it to an assistant like ChatGPT, Claude, Grok or Cursor through MCP.
  2. Tell it: “Set up an incident log: Incidents (title, start, end, impact, severity, cause, owner), Timeline and Follow-ups.”
  3. Give customer success read access to impact and status, and your alerting script access to open entries.

Get your account

Questions people ask

Can it page on-call?

No. Use your paging tool, and log the incident here.

Can an agent help during an incident?

Yes. It can read past incidents and suggest likely causes.

What does ADoor cost?

It’s free for up to 3 tables and 100 rows. Pro is $10 a month per workspace, with 1 GB of storage and no per-GB charges.

Does it work with Claude and Grok too?

Yes. ChatGPT, Claude, Grok and Cursor all connect through MCP with a sign-in, and each gets its own access that you can narrow or remove later.

Updated October 20, 2026.

This page as Markdown