> ## 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.

# Enterprise overview

> When to choose hosted LaneSync SaaS vs self-hosted deployment — data residency, compliance, and support.

LaneSync is primarily a **hosted SaaS** at [lanesync.dev](https://lanesync.dev). Enterprise customers may deploy LaneSync in their own environment for data residency, air-gapped networks, or custom compliance requirements.

## Hosted SaaS (default)

| Benefit                    | Description                                 |
| -------------------------- | ------------------------------------------- |
| **Zero ops**               | No servers, database, or upgrades to manage |
| **Fast onboarding**        | Sign in → install GitHub App → repo wizard  |
| **Always current**         | LaneSync team ships updates to lanesync.dev |
| **Multi-tenant isolation** | PostgreSQL RLS per GitHub org               |

**Best for:** Most teams who want release governance without infrastructure overhead.

[Get started →](/quickstart)

## Self-hosted (Enterprise)

| Benefit               | Description                                             |
| --------------------- | ------------------------------------------------------- |
| **Data residency**    | All data stays in your VPC or region                    |
| **Custom domains**    | Serve dashboard and API on internal URLs                |
| **Air-gapped option** | Deploy without public internet (with GitHub Enterprise) |
| **Custom GitHub App** | Register your own app with org-controlled credentials   |

**Best for:** Regulated industries, strict compliance frameworks, or organizations that cannot use third-party SaaS for release metadata.

[Self-hosting guide →](/enterprise/self-hosting)

## Comparison

| Capability              | Hosted SaaS            | Self-hosted                |
| ----------------------- | ---------------------- | -------------------------- |
| Sign up at lanesync.dev | Yes                    | N/A — you deploy           |
| GitHub App              | LaneSync-managed       | Customer-managed (typical) |
| `SDLC_API_URL` for CI   | `https://lanesync.dev` | Your API URL               |
| Upgrades                | Automatic              | Your release process       |
| Support                 | Standard               | Enterprise agreement       |

## Compliance angle

Self-hosted deployments help when auditors require:

* Evidence and milestone data stored in a specific geography
* No third-party subprocessors for release governance metadata
* Integration with internal SSO and logging (roadmap / custom)

Quality evidence still originates from **your CI** and **your GitHub** — LaneSync aggregates and enforces; it does not replace your source control or build systems.

## Next steps

<CardGroup cols={2}>
  <Card title="Self-hosting" icon="server" href="/enterprise/self-hosting">
    Docker Compose deployment, environment variables, service URLs.
  </Card>

  <Card title="Security" icon="shield" href="/enterprise/security">
    RLS, GitHub App tiers, CI API URL override.
  </Card>
</CardGroup>

Contact **[support@lanesync.dev](mailto:support@lanesync.dev)** for enterprise licensing and deployment assistance.