File: licensing_and_offerings.md

package info (click to toggle)
gitlab 17.6.5-19
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 629,368 kB
  • sloc: ruby: 1,915,304; javascript: 557,307; sql: 60,639; xml: 6,509; sh: 4,567; makefile: 1,239; python: 406
file content (69 lines) | stat: -rw-r--r-- 2,950 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
---
stage: AI-Powered
group: Custom Models
description: Self-Hosted AI Models Licensing and Offerings
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

# Self-Hosted AI Models: Licensing and Offerings

DETAILS:
**Tier:** Ultimate with GitLab Duo Enterprise - [Start a trial](https://about.gitlab.com/solutions/gitlab-duo-pro/sales/?type=free-trial)
**Offering:** Self-managed
**Status:** Beta

> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../../administration/feature_flags.md) named `ai_custom_model`. Disabled by default.
> - [Enabled on self-managed](https://gitlab.com/groups/gitlab-org/-/epics/15176) in GitLab 17.6.
> - Changed to require GitLab Duo add-on in GitLab 17.6 and later.

To deploy self-hosted AI models, you need GitLab Ultimate and Duo Enterprise - [Start a trial](https://about.gitlab.com/solutions/gitlab-duo-pro/sales/?type=free-trial).

## Offerings

### 1. Self-Hosted Models

These are AI models deployed within your infrastructure, giving you full control over your data and security.

- **Configuration:** Set up an AI gateway and configure model endpoints within GitLab.
- **Licensing:** Requires a valid GitLab license. You can request a license through the [Customers Portal](https://customers.gitlab.com).

The following sequence diagram illustrates the process of handling a user request through a self-hosted model:

```mermaid
sequenceDiagram
    participant User
    participant GitLab as GitLab Instance
    participant Gateway as AI gateway
    participant Model as Self-Hosted Model Endpoint

    User->>GitLab: API Request
    GitLab->>Gateway: Forward Request
    Gateway->>Model: Route to Self-Hosted Model
    Model-->>Gateway: Return Response
    Gateway-->>GitLab: Send Response
    GitLab-->>User: Deliver Response
```

### 2. GitLab Vendor Models

These models are hosted by GitLab and accessed through the GitLab Cloud Connector, providing an out-of-the-box AI solution without requiring on-premise infrastructure.

- **Configuration:** Enable the desired features in GitLab and select a vendor-hosted model.
- **Licensing:** Included with your GitLab subscription, depending on your plan (Ultimate or GitLab Duo). No additional license is required for these models.

The following sequence diagram illustrates the process of handling a user request through a GitLab Vendor Model:

```mermaid
sequenceDiagram
    participant User
    participant GitLab as GitLab Instance
    participant Connector as GitLab Cloud Connector
    participant Vendor as GitLab Hosted Model

    User->>GitLab: API Request
    GitLab->>Connector: Forward Request
    Connector->>Vendor: Route to GitLab Hosted Model
    Vendor-->>Connector: Return Response
    Connector-->>GitLab: Send Response
    GitLab-->>User: Deliver Response
```