Sign inSign up

You ship the workflow, and Dome runs the agent.

Nightly ticket triage, the Monday report, the agent a GitHub webhook starts. Describe the job and say when it runs. Dome runs it under your rules and records every call.
Talk with our teamStart from a template
What teams run

Work that runs itselfon a schedule, on an event, or on demand.

Triage tickets overnight

At 2am the agent reads new Zendesk tickets, tags them and routes each to its queue, and support starts the day with a sorted inbox.

Answer a GitHub webhook

When an issue opens, a signed webhook starts the agent, which labels it, finds duplicates and drafts a reply.

Write the Monday report

Monday at 8am Chicago time, the agent pulls last week's numbers and posts the summary to Slack before standup.

Draft the incident timeline

A PagerDuty alert starts the agent, which gathers the logs and deploys around the page and drafts the timeline.

Reconcile invoices hourly

Every hour the agent matches new invoices against the ERP and flags what doesn't line up. Finance reviews the exceptions.

Run an ops task by hand

Rotate a report, rerun a backfill, or clean up a queue with a run by hand, under the same rules as any scheduled run.
What you don't build

Dome runs the infrastructurebehind every agent.

Agent infrastructure

Dome runs the agentic loop, with no workers or queues for you to keep alive.

Credential handling

Dome mints and stores the agent's credential, out of reach of your code and your team.

Scheduling

Schedules use cron in any IANA time zone, and missed runs follow the catch-up policy you set.

Retries and queuing

Infrastructure failures retry as required, and a trigger that fires past the concurrency cap is queued rather than dropped.

Governance

Every tool and model call goes through the agent's gateway, under the same rules, guards, and quotas as any other agent.

The audit record

Every run lands in the audit trail with its trigger, steps, tool calls, and tokens.
How it works

From templateto first run.

  1. Start from a template

    An agent template config describes the app: its agents, models, gateway, tools, rules, quotas, and triggers.

  2. Choose who runs each agent

    For each agent, Dome runs it or you do, and the same rules apply either way.

  3. Say when it runs

    A schedule in your time zone, a signed webhook, or a run by hand.

  4. Read every run

    Each run is recorded with its trigger, steps, tool calls, and token counts, and suspending the agent stops it.

dome — bash
dome managed-agents create \  --name nightly-triage \  --system-prompt "Triage new tickets each night." \  --model prod-reasoning \  --gateway prod-gateway
dome triggers create \  --name nightly --kind schedule \  --cron "0 2 * * *" --timezone America/New_York \  --target nightly-triage
dome managed-agents run nightly-triagedome managed-agents runs
Related

Where managed agentsfit in the platform.

Agent Factory

For platform teams: templates, a managed runtime, shared gateways and pools, one audit trail.

Agent Runtime

The product detail: triggers, the held credential, retries and the run record.
Next steps

Talk with ourFDE team.

Or start free, and run your first managed agent today.
01

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
Book a call with our FDE team
02

Start free

No card required to start. Pick a template and run it.
Start free

Put your first agent to work.

Read the docsStart from a template