ADoorYour data account Get your account

Keep feature flags and config agents can read

Feature flags, limits and agent settings that people, scripts and agents read, each with an owner and a history of who changed what.

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 Turn on new-billing-page for the staging environment only, and set the triage agent's max issues per run to 50.

ADoor Updated 2 entries in Config

Config

KeyEnvironmentValueOwner
new-billing-pagestagingonAli
triage-bot.max_issuesall50Kim

What you can ask later

  • “What’s on in staging and off in production?”
  • “Who changed the triage limit, and what was it before?”
  • “Which flags haven’t changed in six months and can go?”
  • “What config does the triage agent read?”

Who can see what

  • Agents and scripts read config with read-only keys.
  • Each owner edits their own keys (one grant per person).
  • Changes to production values go through a person: an agent can ask for more access, and you approve or deny.
  • The history keeps who changed each value and the old one.

How it compares with LaunchDarkly or a config file

LaunchDarkly and similar services are better for flags evaluated on every request in production, with SDKs, targeting rules and gradual rollouts. ADoor doesn’t publish latency figures and its SDK is still coming, so it isn’t a fit for that path today.

For settings people and agents change by hand, ADoor is a good home: agent limits, scheduled job settings and staging switches, with owners, a history and access per key.

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 config: Config (key, environment, value, owner, description).”
  3. Give agents and scripts read-only keys, and each owner edit access to their own keys.

Get your account

Questions people ask

Should my app read flags on every request?

For high-traffic paths, use a flag service. ADoor suits settings read by jobs, agents and scripts.

Can an agent change config?

Only with the access you give it, never more than the person who connected it.

How much does ADoor cost?

The free plan holds 3 tables and 100 rows, enough to start a list like this. Pro is $10 a month per workspace, with 1 GB of storage and no per-GB charges.

Can I get my data out?

Yes. Anything you can see downloads as CSV or JSON.

Updated October 20, 2026.

This page as Markdown