Hermes Business — Agent Deploy Platform

• What it is: concept/early-stage AI-SaaS: "turnkey agents for business". A client submits a request → an isolated VM (Hetzner) is provisioned with Hermes Agent + a Telegram bot configured for their business. Three layers: acquisition (landing + form), processing (internal Hermes agent + manager + Claude Code drive onboarding), production (one VM per client).
• Type / status / role: other (startup placeholder) / prototype (plan + design + boilerplate, product not yet built) / solo (3 user commits, 2 — Bobur).
• Activity period: initialized 2026-04-03 (5 commits total). Fresh, early-stage.

• Repo contents: BUSINESS_PLAN.md (25 KB, RU — funnel, pricing, deploy pipeline, monitoring), landing.pen (landing design in Pencil), shipkit/ (git submodule — SaaS boilerplate).
• shipkit (submodule `Dave93/hermes-shipkit`, private fork, 32 commits): Turborepo (Bun) — apps/web (Next.js 16), apps/api (Elysia.js), apps/admin; packages auth (Better Auth)/db (Drizzle)/cache (Redis)/ui (shadcn+Tailwind v4)/email (React Email+Resend). shadcn MCP, .claude/skills (deploy/dev/ui-ux/polar).
• Planned infra: Hetzner API (VM creation), provision → auth → Hermes config → launch + healthcheck (scripts in scripts/ — planned).
• Client data: clients/[company]/ with inquiry.md/profile.md/deploy.md/tickets/ (planned).

• 2098bb9 Initial commit: business plan for the Hermes agent deployment platform.
• 812df95 Added shipkit as a submodule (private fork).
• dda94ae Landing design (navigation, hero, CTA) in Pencil.
• c10f974 Project instructions (CLAUDE.md) + submodule update.
• 340072b Update shipkit: fullstack lead capture, landing improvements, favicon.
• Scope: 5 commits — this is a "wrapper" (plan + design + pointer to boilerplate), not the product itself.

There's no non-trivial code of its own in this repo (plan + design + submodule). The engineering substance lies in the architectural intent (per BUSINESS_PLAN.md/CLAUDE.md):

• Per-client deploy pipeline: Hetzner API → provision VM → auth setup → configure Hermes Agent → launch + healthcheck. Client isolation = VM. → A thought-through multi-tenant-via-isolation model (instead of a shared DB — a dedicated VM per client).
• AI in operations: Claude Code + internal Hermes agent drive client onboarding (processing layer). → On-trend model of "AI within the business process itself".
• The actual agent/deploy-script code lives outside this repo (Hermes Agent — a separate project; see the hermes cluster).

• Sessions found: 0 for the exact path. A local .claude/ exists.
• What was done with AI: the product by design is AI-agents-as-a-service; Claude Code is declared part of operations (onboarding). No transcripts for this repo.
• Pattern: ShipKit as a submodule + .claude/skills (deploy/dev/ui-ux/polar) — reusing the AI-ready boilerplate for a new startup.

• Shaped startup idea: business plan + design + ready boilerplate foundation.
• Demonstrates product thinking (funnel, pricing, deploy pipeline) + reuse of the user's own ShipKit.
• No product code yet — no metrics.