Custom Agents
AI Agent Operations
Hosting, monitoring, backups and updates for the agents we build.
Available now · Human approval · Complete audit trail
The operational problem
Handover is the beginning of an agent’s operating life
Models, APIs, credentials and business rules change after deployment. An agent can appear available while approvals are stuck, a connector is refusing unexpected calls or a backup has never been restored.
Agent Operations assigns ownership to runtime health, refusals, backups, restore tests, approved updates and monthly evidence. The service runs with us or in your environment, under the boundaries defined during the build.
Operating scope
What has to be owned after launch
Runtime health
Availability, scheduled work, queue state and dependency failures are observed.
Approval flow
Waiting, rejected and expired approvals remain visible instead of looking like silent downtime.
Refusals and errors
Expected safeguards are separated from new failure patterns that require investigation.
Backup and recovery
Configuration, state and required data are backed up with recorded restore evidence.
Controlled change
Updates are tested, approved and reported with the previous version and rollback path known.
Operating method
How an agent remains observable and recoverable
- Define service ownershipEnvironment, contacts, support boundary, dependencies and escalation path are agreed during onboarding.
- Instrument the operating statesHealth, queues, approvals, refusals and external dependencies become observable signals.
- Back up what recovery needsThe recovery set and retention are defined from the agent’s actual state and configuration.
- Test restoreA backup is not reported healthy solely because a job completed. Restore evidence is recorded.
- Approve and verify updatesChanges run through tests and the agreed approval before deployment, followed by health checks.
- Report the monthOne operating summary shows what ran, failed, refused, changed and was restored.
Example report
Health, refusals and changes stay together
Illustrative monthly operations report — no customer runtime data
- Agents
- 3
- Uptime
- 99.9 %
- Refused operations
- 14 (all expected)
- Backups
- Daily, restore tested
- Updates
- 2 applied, approved
Reliability judgement
The rules behind managed agent operations
Healthy means the workflow can complete
A running process is insufficient if its queue, approval or connector dependencies are blocked.
Expected refusals are positive evidence
A blocked out-of-scope action demonstrates the boundary works; a new refusal pattern still deserves review.
Backups require restore evidence
Recovery confidence comes from a tested restore path, not a green backup icon.
Updates remain customer-controlled
Material changes are explained and approved before deployment into the operating service.
Fixed start
What the one-week onboarding delivers
- Ownership and escalation mapNamed service owner, TechOne contact, support boundary and dependency owners.
- Monitoring baselineHealth, queue, approval, refusal and dependency signals configured for the agent.
- Backup and restore planRecovery scope, retention, procedure and evidence requirement documented.
- Update workflowTest, approval, deployment, verification and rollback stages agreed.
- First operations reportThe monthly format and evidence sources established during onboarding.
Fit
When managed operations are—and are not—the right model
A good fit
- The agent was built or accepted with tests, a runbook and known operating boundaries.
- Your team wants one accountable owner for routine monitoring, backup and updates.
- The runtime can expose health, logs and controlled deployment operations.
Not the right fit
- The agent has no accepted specification, tests or ownership baseline.
- The expectation is unmanaged model changes with no approval or rollback.
- The environment cannot provide supported monitoring, backup or recovery access.
Where the human approves
You approve each update. The AI works through a fixed list of allowed operations; every approval and result is logged.
Operations questions
Questions a service owner should ask
Can the agent run in our environment?
Yes. The operating model can run in your environment or with TechOne, depending on access, ownership and compliance requirements.
What counts as uptime for an agent?
The definition includes the workflow’s ability to accept work and reach its expected approval or result, not only whether one process is running.
How are refused operations reported?
They are grouped by expected policy refusal, invalid request and new anomaly so operators can distinguish a working safeguard from a developing problem.
Are updates automatic?
Material updates are tested and presented for the agreed approval before deployment. Emergency handling and rollback are defined during onboarding.
How often are restores tested?
The frequency is agreed from recovery requirements and operating risk. The report records the latest restore evidence, not merely the backup schedule.
Experience behind the service
Built from operating our own agent systems
The service uses the same operational disciplines TechOne applies to its own agent and product systems: deployment controls, monitoring, service management, backups, restore testing, TLS and approved updates.
Technical stewardship: David Máj, Founder & Technology Consultant. Last reviewed 24 September 2026.