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

# Welcome to Skyhook

> A Kubernetes platform that generates the workflows, manifests, and GitOps plumbing — you keep the repo and the cloud account.

Skyhook generates the GitHub Actions, Kubernetes manifests, and GitOps wiring that most teams build by hand. You bring a cluster and a repo; Skyhook fills in the boring middle so engineers can ship to Kubernetes without running a platform team.

## Pick your path

<CardGroup cols={2}>
  <Card title="I'm shipping a service" icon="rocket" href="/application/services/create-import">
    Import a repo, get generated workflows + Kubernetes config, deploy to dev in under ten minutes. Start with **Create and Import Services**.
  </Card>

  <Card title="I'm setting up the platform" icon="layer-group" href="/getting-started/onboarding-guide">
    Connect clusters, set up GitOps, configure addons and CI/CD credentials. Start with the **Onboarding Guide**.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="Connect a cluster">
    Bring your own GKE, EKS, AKS, or any Kubernetes-compatible cluster. Skyhook installs a lightweight read-only connector via Helm — clusters stay in your account.
  </Step>

  <Step title="Import or create a service">
    Skyhook scans your repo, detects language and framework, and generates a Dockerfile, Kubernetes manifests, and CI/CD workflows. You review the pull requests before anything merges.
  </Step>

  <Step title="Deploy">
    Push to main and your service builds and deploys automatically. Promote across environments from the UI, CLI, or a `workflow_dispatch` run in GitHub Actions.
  </Step>

  <Step title="Iterate">
    Logs, metrics, traces, preview environments, GitOps with ArgoCD — all wired up. Override anything the generators produced; it's your repo.
  </Step>
</Steps>

## Set it up from your terminal

The fastest way through onboarding is the CLI:

```bash theme={"system"}
# install (macOS — see Onboarding Guide for Linux/Windows)
brew install skyhook-io/tap/skyhook

# walk through cluster connect → GitHub OIDC → ArgoCD bootstrap → first service
skyhook onboard
```

The same flow is available in the web UI at [app.skyhook.io](https://app.skyhook.io). Both produce the same result.

## What's in here

<CardGroup cols={3}>
  <Card title="Core concepts" icon="book" href="/introduction/core-concepts">
    Services, environments, clusters, GitOps, and the difference between the cluster connector and the AI agent.
  </Card>

  <Card title="CI/CD & deployment" icon="code-branch" href="/application/cicd/overview">
    How generated GitHub Actions workflows build, deploy, and promote your services across environments.
  </Card>

  <Card title="GitOps with ArgoCD" icon="shuffle" href="/infrastructure/gitops/overview">
    Optional declarative deployments — Git as the source of truth, ArgoCD reconciling clusters.
  </Card>

  <Card title="Connecting clusters" icon="server" href="/infrastructure/clusters/connecting-clusters">
    GKE, EKS, AKS, or any conformant Kubernetes — including bare-metal, k3s, and on-prem.
  </Card>

  <Card title="Observability" icon="chart-line" href="/observability/overview">
    Logs, metrics, traces, and FinOps — opinionated defaults you can swap out.
  </Card>

  <Card title="Skyhook Agent" icon="sparkles" href="/chatops/overview">
    AI assistant that knows your services, clusters, and code. Ask, debug, and configure in chat.
  </Card>
</CardGroup>

<Info>
  Stuck? Email [support@skyhook.io](mailto:support@skyhook.io) — a real engineer reads it.
</Info>