ADoorYour data account Get your account

Record deploy and release history

What shipped, where, when, by whom and from which commit. Your CI job writes each deploy, and anyone can ask what changed before an incident.

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 What went to production this week, and did anything get rolled back?

ADoor Read 9 entries from Deploys

Deploys

VersionEnvCommitStatus
v1.42productiona3f9c21Rolled back
v1.42.1production7d1e044Live
v1.41production52bb7e0Replaced

What you can ask later

  • “What’s live in production, and from which commit?”
  • “What changed between v1.40 and v1.42?”
  • “How many deploys did we do per week this quarter?”
  • “Which releases were rolled back, and why?”
  • “Chart deploys per week and rollbacks this quarter.”

Who can see what

  • A GitHub Actions job writes each deploy with short-lived access, 15 minutes by default, and no stored secret.
  • Engineers read the history.
  • Customer success reads release notes, without commit details.
  • An incident agent reads recent deploys to check what changed.

How it compares with GitHub Releases or your CD tool

The release itself (tags, artifacts, approvals and rollbacks) stays in GitHub Releases and your CD tool.

Across services and environments, ADoor keeps the shared record, with release notes for non-engineers, asked about in plain words or plain SQL.

How to start

  1. Open an assistant like ChatGPT, Claude, Grok or Cursor and connect ADoor through MCP.
  2. Tell it: “Set up deploy history: Deploys (version, service, environment, commit, by, at, status, notes), then add the GitHub Actions sign-in.”
  3. Give customer success read access to release notes, without commit details.

Get your account

Questions people ask

How does GitHub Actions sign in?

Through workload identity: the job proves who it is with its GitHub token and gets access for 15 minutes, with no stored secret.

Can other CI systems write?

Yes, through the HTTP API with a key.

Do I have to pay?

Not on the free plan, which holds 3 tables and 100 rows. Pro is $10 a month per workspace, with 1 GB of storage and no per-GB charges.

What if I want to leave?

Export each list as CSV or JSON and take it with you.

Updated October 20, 2026.

This page as Markdown