Definition · examples · use cases

Self-hosted AI agent platforms, explained.

A self-hosted AI agent platform runs your agents on hardware you control — your laptop, a VPS, your VPC, or on-prem. Here's what the term actually means, which platforms deliver it, and when it's the right call.

Grounded in public docs · September 2026

Definition

What "self-hosted AI agent platform" means

Three properties separate a genuinely self-hosted platform from a managed one.

  1. The runtime lives on your machine. Agents run in an environment you provision, not on a vendor's cloud.
  2. Your configuration is code you own. Agents, skills, and memory are versioned files in your repo, not settings in someone's product.
  3. Secrets and data stay in your perimeter. Credentials are stored where you control them, and model calls go to providers you chose with your own keys.

Examples

Platforms that actually self-host

server-side

Kortix (Suna)

Runs from Docker on your own hosts (kortix self-host start). Org-scale agents in isolated sandboxes, work landing through a change request you approve.

  • Elastic 2.0 (source-available).
  • VPC or on-prem.
  • Self-host free.
local-first

OpenWork

A desktop app where your files stay on your machine and prompts go only to the LLM provider you choose.

  • Open source.
  • macOS / Windows / Linux.
  • Desktop free.
workspace

Eigent

Packages a workspace you run locally or self-hosted, connecting cloud, gateway, or local models.

  • Open source.
  • BYOK or local models.
  • Self-host free.

Use cases

Who self-hosts, and why

marketing

Content and research pipelines

Run research, drafting, and competitive briefs on agents that stay on your infra — keeping briefs and source data inside your perimeter.

small business

Predictable cost, owned data

Self-hosting is free on all three platforms; you trade vendor fees for operating a box you already control.

engineering

Governed agent fleets

Org-scale specialist agents that share memory and land work only through reviewed change requests.

How to choose

The short checklist

  1. Confirm the license fits (OSI-open vs source-available).
  2. Pick hardware: laptop, VPS, VPC, or on-prem.
  3. Bring your own model keys or local models.
  4. Turn on the human gate — change requests or approvals.

Step-by-step self-hosting guide →