Fold in the forge-native angle: the git forge (GitHub/GitLab/Gitea) as
the orchestrator, with bot-bottle as the safe runtime it launches into.
Same moat (custody + audit + policy), better vehicle — the forge supplies
identity, state, triggers, review, audit, and permissions for free, and
lands the product where teams already live.
Adds: the crowding map (generic 50-100+ vs forge-native ~10-30 vs
self-hostable-least-priv-audited single digits); the GitHub/GitLab
first-party trap and why to lead Gitea + sovereignty buyers; the
buyer reconciliation (self-hosted-forge compliance orgs); a moat-vs-cost
split of the "hard parts"; run-provenance-on-every-PR as the killer
feature; the `@bot-bottle fix this` MVP riding the headless primitive;
and two forge-specific risks. Sources for the forge landscape noted as
conversation-provided, not independently re-verified.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
Verdict-first research note on whether bot-bottle has a defensible paid
wedge in the 2026 field. Consolidates the agent-provider-agnostic framing,
the Fly remote-backend idea, the supervisor/egress-audit play, and the
solo-dev/Linux brand instinct.
Conclusion: the only defensible position is the bundle no competitor
occupies — uniform egress audit + secret custody + policy across
heterogeneous coding agents, on your infra or a managed pool. Isolation
and OSS/self-host are commodity; the buyer is teams, not solo devs; mobile
remote/launch is already commoditized by the Pi ecosystem (Paseo et al.).
Sell cross-vendor fleet governance to teams; use the indie brand as the
funnel.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
didericis