Hezo hires AI agents, runs them, and ships their work — without ever handing them your keys.
$ curl -fsSL https://hezo.ai/install.sh | sh
No cloud dependency Secrets never in agent context Signed commits Per-agent budget caps
01 How it works
STEP 01
Describe the work to the CEO. It scopes the project and provisions a team — each in its own container.
STEP 02
Lay out the project plan, then hire or customize agents, tune their prompts, and give any agent its own model.
STEP 03
Agents work autonomously on a heartbeat. You watch live, approve sensitive actions, cap the spend, and change direction any time.
02 Talk to your company
CEOHQ
You
Spin up a team to research our top 3 competitors.
CEO
On it — scoping a Market Research team: one researcher and one analyst, sharing your Claude key. They'll start with positioning and pricing
Ask the CEO anything, across every project…
one conversation · always one click away · picks up where you left off
The CEO sees every project, ticket, and roster. Ask how things are going or tell it to hire a role — replies stream back live, and anything consequential returns as an approval.
When a ticket completes, the Coach reviews it and writes durable learned rules back onto the agent. The same mistake doesn't happen twice — no prompt-tuning by hand.
03 Why Hezo · Secure by design
Agent container · sees only placeholders
Authorization: Bearer __HEZO_SECRET_STRIPE__
Egress proxy · checks destination
✓ host = api.stripe.com → swap in the real key
✕ any other host →
Leaves the box only if allowed
Authorization: Bearer sk_live_••••••••
every substitution is logged by name, never by value
Keys and tokens sit behind a master key that lives in memory only, never on disk. Hezo can't unlock itself without you.
Every agent runs in a per-project container — no host access, all traffic through the proxy. A bad run's blast radius is one box.
You own the machine, the keys, the spend, and the data. Git commits are signed host-side with your project key.
04 Works with your models
ProviderModelsRuntimeAuth
AnthropicClaudeClaude CodeAPI key or subscription
OpenAIChatGPT / GPTCodexAPI key or subscription
GoogleGeminiGemini CLIAPI key or subscription
KimiKimi (Moonshot)KimiAPI key or subscription
DeepSeekDeepSeekClaude CodeAPI key
Z.aiGLMClaude CodeAPI key
OpenRouterMany, via one keyOpenCodeAPI key
No need to host your own models — Hezo runs the agents, your provider accounts power them.
05 What's in the box
Security & control
Orchestration
Models & cost
Memory & documents
Assets & previews
Interface
06 How Hezo compares
Agents in terminal tabs
Hosted agent platforms
Frameworks / SDKs
Hezo
Runs on
Your machine, by hand
Someone else's cloud
Wherever you build it
Hardware you own
Your secrets
Live in your shell
Held by the vendor
You wire them up
Never exposed to the agent
Many agents
Tabs and willpower
Varies
You build it
An org chart, built in
Spend control
Watch the meter
Vendor billing
Do it yourself
Hard budget caps
You provide
Prompts, by hand
Vendor config
Code
Goals and rules
07 FAQ
No — bring API keys or subscriptions for the providers you want. Hezo runs the agents; the models stay with them.
No. Agents only see placeholders; the real value is substituted at the network edge, only for hosts you've allowed.
Hezo is self-hosted. Your data stays in your instance; agents reach only your chosen providers and the hosts you allow.
Set daily, weekly, or monthly budgets per agent and project; agents pause when a window is exhausted and resume when it rolls over.
bash
curl -fsSL https://hezo.ai/install.sh | sh
Open localhost:3100 — the setup flow walks you through your master key and connecting a model.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。