Managed hosting operator
≈ $15M revenue (approx.) · 3,000+ hosted accounts · a 24/7 operations team
Host-panel and DNS operations agent
Account provisioning, DNS changes and site deployments through approval-gated connector tools, with each user's own panel credentials scoped to that user and every action in the audit log.
- Organization
- Managed hosting operator
- System
- A commercial hosting control panel with a broad API
- Runs on
- The operator's own tenancy
- Scope
- Operations agent with approval-gated actions
Where they started.
Routine hosting operations, account provisioning, DNS changes and deployments, were done by hand through the control panel, one screen at a time. The operator wanted the speed of an agent without the risk of an agent deleting a zone or an account on its own.
What was built.
- A first-party MCP connector for the control panel exposing the operations staff actually perform, with each user's own panel credentials scoped to that user.
- Reads and routine changes run directly; destructive or exposing calls pause in the approval queue for a human.
- Deploying a static site becomes a sentence: build, upload, extract, verify, with the agent reporting what it did.
- Every action, approved or denied, recorded in the audit log.
What changed.
- Operations that took a sequence of screens take one request.
- No unattended destructive action is possible by construction.
- Credentials never shared between users or stored in a prompt.
- The connector pattern reused for the operator's other systems.
Panel credentials and customer account data cannot pass through a third-party model. The connector holds them in a vault and the model only ever sees the request it composed.
The operator's own tenancy
Components involved.
More like this.
Healthcare receivables agency
≈ $10M revenue (approx.) · ~60 employees · national client base
- Use Case:
- Placement-file intake automation
- Results:
- Placement files arriving in any layout are normalized into the agency's existing upload format, with a human approval queue before anything reaches the system of record. A one-and-a-half-person manual job becomes a review step.
Healthcare receivables agency
≈ $10M revenue (approx.) · ~60 employees · regulated healthcare receivables
- Use Case:
- Protected-health-information send gate
- Results:
- Every outbound file that carries protected health information is checked against the placement it belongs to and held for human approval, with an audit trail of who released what, and when.
Regulated outbound contact center
≈ $40M revenue (approx.) · ~250 agents · three sites
- Use Case:
- Compliant voicemail lane beside the existing dialer
- Results:
- A voicemail lane leaves a message specific to each account, in a consented agent voice, at a volume no floor can match, and shares one attempt ledger with the dialer so contact limits stay enforced in one place.
Have one like it?
Every spotlight started as a conversation about a process nobody liked doing, under a data-locality constraint.