> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bothive.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Bothive

> Why teams choose Bothive over DIY agent stacks, LangChain, and raw API calls.

<div className="hero-container">
  <p className="hero-subtitle">
    Coding an agent isn't the hard part. Shipping one that real users can rely on — that's where Bothive wins.
  </p>
</div>

<Info>
  **TL;DR** — Bothive is not a prompt wrapper. It's the infrastructure layer that makes AI agents reliable, observable, multi-tenant, and deployable — without reinventing the stack.
</Info>

## What you're really buying

When you use Bothive, you're not just getting an AI chat interface. You're getting:

<div className="feature-grid">
  <div className="feature-card">
    <div className="feature-icon" />

    <h3>Hosted Runtime</h3>
    <p>No DevOps. No scaling. No cold starts. Your agent runs on Bothive's production infrastructure.</p>
  </div>

  <div className="feature-card">
    <div className="feature-icon" />

    <h3>Persistent Memory</h3>
    <p>Conversation, persistent, and summarized memory types. Your agents remember what matters.</p>
  </div>

  <div className="feature-card">
    <div className="feature-icon" />

    <h3>25+ Integrations</h3>
    <p>GitHub, Gmail, Slack, Telegram, Stripe, Notion, Google Calendar — ready to connect from the dashboard.</p>
  </div>

  <div className="feature-card">
    <div className="feature-icon">️</div>
    <h3>Full Observability</h3>
    <p>Every run has a trace. See exactly what happened, what tool was called, and why it failed.</p>
  </div>
</div>

## The Shopify Analogy

Vercel AI SDK and LangChain are like React — powerful building blocks, but you assemble everything yourself.

**Bothive is like Shopify.** You get the complete platform:

| With Shopify        | With Bothive                 |
| ------------------- | ---------------------------- |
| Payments built-in   | Hosting built-in             |
| Themes & storefront | Visual agent builder         |
| App marketplace     | HiveStore marketplace        |
| Analytics dashboard | Observability & traces       |
| Multi-store support | Multi-tenant agent isolation |

You don't need to wire together a payment gateway, CDN, inventory system, and auth — Shopify is the product. Bothive is the same for AI agents.

## Bothive vs DIY

If you build your own agent stack, you still need to solve:

<CardGroup cols={2}>
  <Card title="Without Bothive" icon="x" className="glass-effect" style={{ borderColor: 'rgba(239, 68, 68, 0.3)' }}>
    * Auth and token refresh logic
    * Memory storage and retrieval
    * Multi-channel delivery
    * Retry queues for failed tool calls
    * Run logs and trace debugging
    * End-user identity separation
    * Deployment infrastructure
    * Rate limiting and abuse protection
    * Scaling and cost optimization
  </Card>

  <Card title="With Bothive" icon="check" className="glass-effect" style={{ borderColor: 'rgba(34, 197, 94, 0.3)' }}>
    * OAuth and credentials managed for you
    * Memory system with 4 types, no setup
    * Web, Telegram, Slack, API out of the box
    * Automatic retries and error handling
    * Full trace visibility per run
    * Tenant-isolated sessions per user
    * Hosted runtime, one-click deploy
    * Built-in rate limits
    * Infrastructure that scales with you
  </Card>
</CardGroup>

## Who Bothive is for

<CardGroup cols={3}>
  <Card title="Founders & Operators" icon="rocket" className="glass-effect">
    Build and ship customer-facing agents without writing backend infrastructure. Use HiveMind and the visual builder. Deploy in hours, not weeks.
  </Card>

  <Card title="Developers" icon="code" className="glass-effect">
    Write agent behavior in HiveLang v5. Call the REST API from your existing product. Compose multi-agent swarms with a clean declarative syntax.
  </Card>

  <Card title="SaaS Teams" icon="layer-group" className="glass-effect">
    Embed Bothive as the agent layer in your product. Tenant isolation, per-user memory, and full observability make it production-ready on day one.
  </Card>
</CardGroup>

## Bothive wins when you need to

* Ship agents into a real SaaS serving many end users, not just yourself
* Connect many integrations without writing custom auth for each
* Deploy across channels (Web, Telegram, Slack, API) from one agent definition
* Debug and improve agent behavior after real usage — with traces, not guesses
* Sell or share agents via the HiveStore marketplace

## The standard Bothive must meet

Bothive has to feel:

| Standard                    | What it means in practice                                 |
| --------------------------- | --------------------------------------------------------- |
| **Faster than DIY**         | Agent deployed in an afternoon, not a sprint              |
| **Easier to operate**       | Fix a broken agent by reading a trace, not searching logs |
| **More observable**         | Know *why* a run failed, not just *that* it failed        |
| **More deployable**         | One agent definition → multiple channels                  |
| **Multi-tenant by default** | Isolated state per workspace, no extra setup              |

## The blunt version

If a developer would be better off building the whole thing themselves, Bothive has failed.

Bothive wins because it gives teams a better **operating model** — less infrastructure work, better deployment surfaces, better visibility, faster iteration once real users arrive.

## Next reads

<CardGroup cols={3}>
  <Card title="Quickstart" icon="bolt" href="./quickstart" className="glass-effect" />

  <Card title="Bothive vs Vercel AI" icon="scale-balanced" href="./concepts/bothive-vs-vercel-ai" className="glass-effect" />

  <Card title="Observability" icon="chart-line" href="./concepts/observability" className="glass-effect" />
</CardGroup>