inline

GitLab, self-hosting and your own models

Connect gitlab.com or a self-managed GitLab and every merge request gets the same review as a GitHub pull request. Bring your own model keys, encrypted and write-only, or run inline yourself in one container beside SQL Server, Redis and blob storage.

1:33 · narrated, with captions · Workflow and integrationsRead about Self-hosting

Chapters

What it covers

  • GitLab merge requests
  • Same reviewer
  • Your own model keys
  • Docker Compose

inline on GitLab merge requests with the same reviewer as GitHub, your own Anthropic, OpenAI, Azure, Bedrock or Vertex keys, and self-hosting.

Read about Self-hosting

Transcript

The narration as spoken, by chapter. Select a time to play the film from there.

Intro

inline reviews your GitLab merge requests, runs on your own model accounts, and runs on your own servers.

Connect GitLab

On the Repositories page, connect gitlab.com or your own self-managed GitLab, with an access token or GitLab sign-in. inline imports the projects that account maintains. Turn reviews on, and it adds the webhook for you.

Same reviewer

Every merge request is then reviewed with the same prompts, validation and feedback loop as a GitHub pull request. Findings land as threads on the exact lines, and the merge gate is a commit status.

Your own model keys

In Settings, Models, bring your own keys for Anthropic, OpenAI, Azure OpenAI, Bedrock or Vertex. Keys are encrypted and write-only. Each model runs on the first credential that serves it, and on the platform's keys only where you allow it.

Self-host

Or run inline yourself: one app container beside SQL Server, Redis and blob storage, configured entirely from the environment. Compose sets up the database before the app starts, and the readiness check tells you when it's serving. inline. Your GitLab, your models, your servers.

Put it on one repository

Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.