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

# Ecosystem

The Charm Platform turns agent projects into hosted applications. It provides the runtime, publishing, billing, authentication, and observability layers around your agent code.

## What the Platform Includes

Charm is made of several coordinated surfaces:

* **Charm CLI**: creates, validates, runs, and publishes agents.
* **Charm Store**: hosts published agents and user-facing app pages.
* **Cloud Runner**: executes serverless and interactive agents in isolated runtimes.
* **Daemon Runtime**: runs long-lived agents on Fly.io-backed machines.
* **Studio and Observability**: tracks runs, logs, usage, and revenue.
* **Docs and Templates**: help builders create compatible agents quickly.

## Core Capabilities

### 1. Isolated Execution

Agents run in managed environments so users do not need to provision infrastructure for every app.

### 2. Secrets and OAuth

Charm can inject platform-managed API keys and user-authorized OAuth tokens into the runtime when declared in `charm.yaml`.

### 3. Server-Driven UI

The manifest defines the input schema and output expectations so the Store can render a usable app without custom frontend code.

### 4. Billing and Monetization

Charm supports wallet balance checks, pricing metadata, subscriptions or one-time purchase flows, and creator revenue tracking.

### 5. Observability

Runs, logs, traces, and status events help creators understand how their agents behave in production.

## Runtime Lifecycles

* **Serverless**: short-lived task execution.
* **Interactive**: real-time streaming conversations.
* **Daemon**: always-on or long-running background agents.

See [Execution Modes](/platform/execution-modes) for details.

## Infrastructure

Charm currently uses a combination of:

* Google Cloud Run for the runner services,
* Supabase for auth and application data,
* Fly.io for daemon machines,
* Docker images for standard and full runtimes.

The exact production architecture may evolve, but the developer-facing contract is the manifest, CLI, and Store publishing flow.