Integration · Build & run
Zones, cache and edge health.
When a site is slow or erroring, Brigham.ai checks the edge first and tells you what it sees.
What it reads
01
Zones
Which domains are on your account and how they are set up.
02
Cache
What is cached, what is not, and what changed.
03
Edge health
Errors and origin problems seen at the edge.
Scopes and access
- Connects as
- Each person, their own account
- Access
- Read-only by default
- Reads
- Zones, cache settings, edge health
- Writes
- Changes, as a separate grant
- Needs approval
- Purging cache, changing rules or DNS
- Visibility
- Private to the person unless connected as org-shared
- Availability
- Available
Yours to connect, yours to revoke.
Each person connects their own accounts from the Connections page. Every connection can be revoked on its own, and every connection starts read-only. A write scope is a separate, explicit grant.
- Credentials are encrypted at rest and referenced by id. They never appear in model context, logs or tool results.
- Each agent gets its own connection grants.
- Tool results from outside sources are untrusted data. They cannot approve anything.
Ask it
- ›“Is anything erroring at the edge right now?”
- ›“Why is the marketing site not caching HTML?”
- ›“Which zones changed settings this week?”
Questions, answered.
Can Brigham.ai change DNS or rules?
Not by default. Those are separate grants, and changes need approval.
Keep reading.
Hosting & deploysBrigham.ai reads app status, deploys and logs from your hosting platform. Deploying and rolling back are sensitive actions that need approval.Read →
EngineeringBrigham.ai triages, reproduces, branches, tests and opens the pull request. Production deploys always wait for a person. Estate health stays read-only.Read →
DashboardsLive views of pipeline, traffic, deploys and operations, split by brand or entity. Built from connected systems, within each person’s access.Read →