LucityLucity
Get Started
Features

GitHub Integration

Connect your repositories and automate deployments via webhooks.

Lucity integrates with GitHub for source code access, authentication, and automated deployments. Your GitHub account is your identity, your repositories are where your code lives, and webhooks tie it all together.

Sign in with GitHub

Authentication is OAuth-based. Sign in with your GitHub account and you're in. No separate credentials to manage, no invitation emails, no password reset flows. Your GitHub identity (login, name, avatar) carries over to the Lucity dashboard.

Each Lucity instance supports multiple workspaces. Your workspace is your team boundary, and everyone in the workspace shares access to the same projects and environments.

Connect repositories

When adding services to a project, browse your accessible GitHub repositories and select one. Each service connects to its own source repo, so a single project can span multiple repositories: your API from one repo, your frontend from another.

Lucity uses the GitHub API to read your source code for builds and service detection. The keyword here is read. Lucity needs to see your code to build it. It never needs to write to your repo. No generated config files get committed, no CI pipeline YAML appears in a pull request you didn't expect, no mysterious bot commits in your history.

Automate with webhooks

Configure webhooks on your GitHub repo to enable automatic deployments:

  • Push to default branch: triggers a build and deploy to your development environment. Push code, get a running deployment. The feedback loop that makes everything else faster.

The webhook service receives push events, matches the repository to the services in your project, and kicks off the build-deploy pipeline automatically. It's the glue between GitHub's event system and Lucity's deployment pipeline.

Coming soon: PR preview environments. When implemented, opening a pull request will automatically create an ephemeral environment, build the PR branch, and deploy it. Merging or closing the PR will clean up the environment. For now, you can create environments manually via the createEnvironment mutation.

Trust that your repo stays sacred

This bears repeating: Lucity reads from your GitHub repositories but never commits to them. No .lucity.yml in your root directory. No generated Dockerfiles. No workflow files injected into .github/. Nothing.

All platform-managed configuration lives in the GitOps repository, which Lucity creates and manages separately. Your source repos are yours, exactly as you left them.

Promotion

Promote images between environments without rebuilding.

Eject

Export your entire setup as standard Helm charts and ArgoCD configs.