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

# Overview

> Deploy your app to your own cloud account — no ops required.

Leanly deploys your app to your own AWS or GCP account. Connect your repo and your cloud account, and Leanly handles the rest — no ops required. You get the ease of a PaaS. You keep the infrastructure.

Your workloads run as standard cloud primitives (Lambda, ECS, Cloud Run, CloudFront) inside your own account. You own the infrastructure, the data, and the cloud bill. Leanly handles the orchestration.

## Core concepts

<CardGroup cols={2}>
  <Card title="Stacks" icon="layer-group" href="/concepts/stacks">
    A set of cloud primitives that together make up a deployed workload — all provisioned and managed by Leanly.
  </Card>

  <Card title="Console" icon="display" href="/concepts/console">
    A single pane of glass for all workloads running across your cloud accounts.
  </Card>

  <Card title="Agent skills" icon="robot" href="/concepts/agent-skills">
    Guided, automated workflows that handle tasks on your behalf.
  </Card>

  <Card title="CLI" icon="terminal" href="/concepts/cli">
    The Leanly command line interface for managing deployments, environments, and configuration directly from your terminal.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="Connect your cloud account">
    Grant Leanly an IAM role in your AWS or GCP account. Leanly uses it to
    provision and manage resources on your behalf — nothing more.
  </Step>

  <Step title="Connect your repo">
    Point Leanly at a GitHub repository. Leanly detects your app type and
    configures deployment automatically.
  </Step>

  <Step title="Review before you deploy">
    Leanly shows you what it will provision. Nothing is created until you
    approve.
  </Step>

  <Step title="Deploy">
    Leanly provisions the right cloud primitives for your app and deploys it.
    Your app is live in your own account — no servers to manage, no YAML to
    write.
  </Step>
</Steps>