Managed agents
A managed agent gets its own isolated machine, and Alfe keeps it online around the clock. You don’t supply a server, install anything, or supervise a process. Create one from the dashboard, choose a size, and Alfe does the rest.
Managed vs self-hosted
Section titled “Managed vs self-hosted”Every agent is one of two hosting types:
| Managed | Self-hosted | |
|---|---|---|
| Where it runs | An isolated machine Alfe provisions | Your own machine or server |
| Who keeps it online | Alfe | You |
| Setup | Create it in the dashboard | Create it, then run alfe setup |
| Hosting cost | Included in your plan, or an add-on | No Alfe hosting charge; your own infrastructure costs apply |
| Lifecycle controls | Start, stop, reboot, recreate, upgrade | You manage the process |
Both are full agents. Each has its own identity, memory, credentials, integrations, and model configuration. The difference is where the runtime lives and who keeps it alive. See Core concepts for the shared building blocks.
When to use a managed agent
Section titled “When to use a managed agent”Choose managed when you want:
- An agent that stays online without a server of your own.
- Automatic recovery after a reboot or crash.
- Updates, backups, and monitoring handled for you.
- A clean, dedicated environment per agent.
When to use a self-hosted agent
Section titled “When to use a self-hosted agent”Choose self-hosted when you want:
- The agent on hardware you already control.
- Direct access to files, networks, or devices on your own machine.
- To use a provider CLI login you already have on that machine.
- To develop on your laptop before making an agent always-on.
Next steps
Section titled “Next steps”- Create a managed agent from the dashboard.
- Choose a size for the workload.
- Learn each status and power action in Lifecycle & status.
- Operate an agent from a terminal with Managing from the CLI.