Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Glean / Glean Protect models

Glean AI Security Models

Fine-tuned detection family for prompt injection, toxic content and malicious code.

restrictedClosed weightsModeration
Official documentation (opens in a new tab)Reviewed 16 Oct 2026
6 of 19 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingSee billing notesGlean enterprise platform
Output billingSee billing notesAccess and billing notes below

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Maximum input tokens
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Maximum output
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Parameters
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Release date
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Knowledge cutoff
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Tool calling
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Structured output
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Streaming
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Batch processing
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Fine-tuning
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Reasoning
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Context caching
Not collected

No reviewed standalone model-specific contract. Unknown is not unsupported.

Published price
Commercial order-form pricing; no standalone model tariff established.Source for Published price (opens in a new tab)

Product fees do not establish input/output token rates or cost per question.

Published training method
Fine-tuned on public data relevant to enterprise threats, with a second-model verification stage.Source for Published training method (opens in a new tab)

Provider model training does not establish a customer fine-tuning endpoint.

Output modalities
Security findingsSource for Output modalities (opens in a new tab)
Output formats
Security findings connected to prompts, source content and agent execution context.Source for Output formats (opens in a new tab)
Deployment scope
Commercial Glean Protect+; the September 2025 launch specified GCP availability.Source for Deployment scope (opens in a new tab)

Current product availability and optional security providers vary; the launch does not establish universal cloud parity.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

Glean enterprise platform

Provider source (opens in a new tab)
API model ID
Not collected

No standalone model selector or immutable inference version is published in the reviewed sources.

Access
Requires Glean Protect+ entitlement and applicable feature configuration; no standalone detector tariff or native model API verified.
Regions
Deployment-dependent single-tenant infrastructure. The subprocessor list allows customer-selected cloud location; third-party processing and support locations can differ.

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Current June 2026 terms govern service access and customer-data processing; separate signed agreements may supersede them. The AI Addendum prohibits training on Customer Data for covered AI Models and promises zero-day retention for Glean-key use, with law and trust/safety exceptions. Customer-key access is the customer’s responsibility. The July Limited Retention Addendum preserves no-training restrictions while allowing specified retention; current docs identify Claude Fable as an opt-in limited-retention model. Native search-encoder training scope, request retention periods and customer-specific terms remain unresolved.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Glean enterprise platform

Not verified

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

How it works
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

Minimum reusable input
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

Lifetime & refresh
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

How to enable it
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

Usage fields
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

Billing rules
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

Limits & data boundaries
Not collected

No model-specific inference-cache contract verified. LLM event cache counters, search indexes, application memory and retention are not proof of native cache support for this model.

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 16 Oct 2026

What the measurements say

Direct prompt-injection accuracy

Glean · provider-reported
97.8%

September 2025 provider evaluation across its described task-specific datasets and verification pipeline. Not independently reproduced; not a universal production guarantee.

Evaluation source (opens in a new tab)

Indirect prompt-injection accuracy

Glean · provider-reported
90%

September 2025 provider evaluation across its described task-specific datasets and verification pipeline. Not independently reproduced; not a universal production guarantee.

Evaluation source (opens in a new tab)

Toxic-content accuracy

Glean · provider-reported
93.5%

September 2025 provider evaluation across its described task-specific datasets and verification pipeline. Not independently reproduced; not a universal production guarantee.

Evaluation source (opens in a new tab)

Malicious-code accuracy

Glean · provider-reported
94.3%

September 2025 provider evaluation across its described task-specific datasets and verification pipeline. Not independently reproduced; not a universal production guarantee.

Evaluation source (opens in a new tab)

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Provider describes internally trained or adapted models used within its commercial service. Underlying technology is reserved under current terms; no public derivative checkpoint is established. This record represents a model family, not a count of unnamed versions or customer copies.

Classification evidence (opens in a new tab)

Lifecycle dates

Generally available security models announced for GCP deployments5 Sept 2025Source (opens in a new tab)

Sources reviewed