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

# Orcra Run: Git-native container orchestration

> Orcra Run is a pull-based container orchestrator. Nodes pull from Git and apply state autonomously — no control plane or ongoing SSH access required.

Orcra Run (`orun`) lets you deploy and manage containers on any VPS or dedicated server using nothing but a Git repository. Commit a manifest, push it, and every node reconciles itself to match — no SSH required after initial setup, no control plane to maintain, no complex CD pipeline to debug.

<CardGroup cols={2}>
  <Card title="Quick Start" icon="rocket" href="/quickstart">
    Bootstrap your first node and deploy a container in minutes.
  </Card>

  <Card title="How It Works" icon="circle-info" href="/concepts/how-it-works">
    Understand the pull-based reconciliation model and why it works offline.
  </Card>

  <Card title="Configuration Reference" icon="file-code" href="/configuration/node">
    Explore all manifest fields for Nodes, Deployments, and Services.
  </Card>

  <Card title="CLI Reference" icon="terminal" href="/reference/cli">
    Full reference for the `orun bootstrap` and `orun start` commands.
  </Card>
</CardGroup>

## Get up and running

<Steps>
  <Step title="Install orun">
    Download the `orun` binary and place it on your `PATH`. See [Quick Start](/quickstart) for platform-specific instructions.
  </Step>

  <Step title="Create a manifest repository">
    Initialize a Git repository that will hold your node and deployment manifests. This repository is the single source of truth for your infrastructure.
  </Step>

  <Step title="Bootstrap a node">
    Run `orun bootstrap` from the manifest repository root. `orun` connects via SSH, installs Docker if needed, copies itself to the node, and starts a systemd service.
  </Step>

  <Step title="Deploy containers">
    Commit `deployments/` and `services/` manifests to your repository. The node picks up changes within seconds and reconciles containers to match.
  </Step>
</Steps>

## Why Orcra Run?

<CardGroup cols={2}>
  <Card title="No control plane" icon="server">
    Nodes operate autonomously. Your cluster keeps running even when your laptop is offline.
  </Card>

  <Card title="Git is the source of truth" icon="code-branch">
    Every configuration change is a commit. Roll back by reverting. Audit history for free.
  </Card>

  <Card title="Built-in ingress & SSL" icon="shield-halved">
    Caddy is embedded in `orun`. Point a domain at your node and SSL provisioning is automatic.
  </Card>

  <Card title="Encrypted secrets in Git" icon="lock">
    Commit SOPS-encrypted secrets directly to your manifest repository. Nodes decrypt at apply time using age keys that never leave the node.
  </Card>
</CardGroup>