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

# Introduction

> LaneSync is a GitHub-native release governance platform — ship with confidence, govern with clarity.

LaneSync gives engineering teams **end-to-end visibility into every release**. Track milestones through enforced SDLC stages, automate quality gates, and prove compliance from a single dashboard.

One YAML file per repo (`sdlc.yaml`). One dashboard for your entire organization.

## Why LaneSync

<CardGroup cols={2}>
  <Card title="Without LaneSync" icon="circle-x">
    * "Did anyone run tests before deploying?"
    * "Who approved this production deploy?"
    * CTO clicks through 10 repos to find status
    * Teams *think* they follow SDLC
    * Anyone can merge without review
  </Card>

  <Card title="With LaneSync" icon="circle-check">
    * Tests are **required** — release blocked if they fail
    * Full **audit trail** — every stage transition recorded
    * **One dashboard** — every repo, milestone, stage
    * Teams *provably* follow SDLC
    * **Branch protection enforced** — approvals + CI required
  </Card>
</CardGroup>

## Core capabilities

<AccordionGroup>
  <Accordion title="Five-stage release pipeline" icon="route">
    Every milestone moves sequentially through enforced gates:

    ```
    PLANNING → DEVELOPMENT → TESTING → EVIDENCING → DEPLOYMENT → DEPLOYED
    ```

    The backend state machine computes stage from live GitHub data — issues, PRs, workflow runs, evidence, and deployments. **Stages cannot be skipped.**
  </Accordion>

  <Accordion title="Three-layer enforcement" icon="shield-check">
    | Layer                          | What it does                                                       |
    | ------------------------------ | ------------------------------------------------------------------ |
    | **GitHub Rulesets**            | PR approvals, required checks, no force-push on protected branches |
    | **Backend state machine**      | Sequential gates; deploy readiness only when prior stages pass     |
    | **CI Action (`sdlc-enforce`)** | Posts `SDLC Enforce` status check; blocks SDLC violations in PRs   |

    See [Enforcement](/concepts/enforcement) for details.
  </Accordion>

  <Accordion title="Zero-config GitHub App integration" icon="github">
    Install the LaneSync GitHub App on your org. LaneSync discovers repositories, bootstraps `sdlc.yaml` and workflows, creates branch rulesets, and begins syncing automatically.
  </Accordion>

  <Accordion title="Central dashboard" icon="layout-dashboard">
    Org-wide milestone view with stage pipelines, drill-down to GitHub (issues, PRs, workflow runs), evidence approval, and quality scorecards.
  </Accordion>

  <Accordion title="Quality & feature tracking" icon="chart-bar">
    CI pipelines upload test evidence via API. LaneSync parses JUnit reports, links tests to features, detects regressions between releases, and exports CSV/HTML/XLSX quality reports.
  </Accordion>

  <Accordion title="Multi-tenant SaaS" icon="building">
    Each GitHub org is an isolated tenant with row-level security. GitHub OAuth sign-in with workspace picker for users in multiple orgs.
  </Accordion>

  <Accordion title="Project roll-ups" icon="layers">
    Group milestones across microservices into CEO-level release projects with aggregate deploy status.
  </Accordion>
</AccordionGroup>

## Get started in minutes

LaneSync is a **hosted SaaS** at [lanesync.dev](https://lanesync.dev). No servers to provision for the default path.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Sign in, install the GitHub App, and advance your first release.
  </Card>

  <Card title="Core concepts" icon="book-open" href="/core-concepts">
    Understand the pipeline, enforcement model, and `sdlc.yaml`.
  </Card>
</CardGroup>

## Need self-hosted deployment?

Enterprise customers can run LaneSync in their own environment. See [Enterprise overview](/enterprise/overview) — this is separate from the primary SaaS onboarding path.