Give the agents you build for clients a place to run. cloudrun provisions a Hermes runtime and gives you a canvas for configuring its agents, connected apps, channels and schedules.
Bring your workflow expertise. Start with one client use case, connect the services it needs, and test the complete job before handing it over.
Hermes available today. View hosting pricing
What you can configure
Open an agent from the project canvas to work with its instructions, skills, tools, integrations and chat. Give the next operator a clear starting point.
Connect supported services through Integrations. Add instruction packs through Skills and toolsets or MCP servers through Tools. Test each connection against the client's agreed permissions.
Automations let you choose a prompt, cron schedule and delivery destination. Start with a bounded task such as preparing a draft report for review.
Channels support connections such as Telegram, Slack and email. Use the channel that suits the client's workflow and verify who can contact it.
From setup to useful work
Write down the input, expected output, actions that need approval and the person responsible for failures.
cloudrun provisions the project's first Hermes engine and a default agent. Open that agent on the canvas.
Add the instructions, required integrations and tools. Send a representative request in chat and inspect the result.
Configure the required channel or schedule, then verify the result arrives at the intended destination.
Record account ownership, operating responsibilities, acceptance evidence and the offboarding procedure.
A resource you can use today
Record account ownership, permissions, expected results and recovery steps. Use the client-agent launch checklist to decide what is ready and what still needs a test.
Reusable worksheet. No signup required.
Make the next decision
A useful offer begins with a specific deliverable: a draft inbox response, a prepared research brief or an internal report. Agree on the inputs, review step, delivery location and support responsibilities before broadening the agent's scope.
Before you get started
You can use the documented Hermes project workflow to configure an agent for a client use case. Decide who owns the organization, connected accounts and model account before setup. Then validate the access arrangement for the people involved.
A profile is not a separate machine or operating-system security boundary. The documented runtime boundary is the engine's box. For separate clients, plan and test separate deployment and credential boundaries, including organization access.
Read the isolation guideYour agency defines the client service, validates the workflow and agrees on ownership, billing and support with the customer. Use your own commercial process for client invoices and branding. The setup described here covers hosting and agent configuration.
Account for hosting, model usage, connected services and the time required to operate the workflow. Build the estimate around the actual workload and the support you agree to provide.
Use the agent cost guideDefine the state you need to recover and test the procedure before making a commitment to a client. A configuration template is not a complete backup.
Review backup and recovery limitsYour first project
Create a project, configure the job and test its first result. Use that evidence to decide what your client can depend on.