Skip to main content
This guide covers self-hosted LaneSync for enterprise customers. The primary product path is the hosted SaaS at lanesync.dev — see Quickstart for cloud onboarding.
Self-hosting requires operational ownership: database backups, upgrades, GitHub App registration, and TLS certificates.

​
Architecture

​
Prerequisites

  • Docker and Docker Compose
  • A GitHub account (or GitHub Enterprise Server)
  • A repository to track
  • TLS termination (reverse proxy) for production

​
Installation

Enterprise customers receive deployment artifacts from LaneSync support. Contact support@lanesync.dev for your installation package and credentials. Typical self-hosted layout:
Production deployments should replace localhost with your internal or public domain behind HTTPS.

​
First-run setup

1

Open the setup wizard

Navigate to your dashboard URL. The wizard guides GitHub App creation (full or minimal tier).
2

Install the GitHub App

Install on your org or account with required repository access.
3

Configure OAuth

Set GitHub OAuth credentials in .env or via the setup API. For pre-created apps:
4

Sign in and bootstrap repos

Complete OAuth sign-in. Run the repo setup wizard for each tracked repository.

​
Environment variables

Copy from .env.example. Key variables: See internal deployment docs in the repository docs/ folder for cloud-specific variants (AWS, Alibaba).

​
CI integration

Bootstrapped workflows default:
For self-hosted, set a repository variable SDLC_API_URL to your API base URL (e.g. https://lanesync.internal.example.com). Evidence upload and deploy gate checks must reach your instance from GitHub Actions runners.

​
Advance your first release

Same stage gates as hosted SaaS:
  1. Create milestone with issues
  2. PLANNING → assign issues
  3. DEVELOPMENT → merge PRs, cut release branch
  4. TESTING → CI passes on release branch
  5. EVIDENCING → approve evidence PR
  6. DEPLOYMENT → promote to production
Demo helper (self-hosted only):

​
Upgrades

  1. Pull latest image or rebuild docker-compose up -d --build
  2. Run database migrations (automatic on backend startup)
  3. Verify /api/health