Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Tabnine / Tabnine Chat

Tabnine Protected V2

Historical second version of Tabnine’s private chat model, made the default in May 2024.

historicalClosed weightsCodingText generation
Official documentation (opens in a new tab)Reviewed 15 Oct 2026
4 of 16 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedTabnine · historical managed deployment
Output billingNot collectedNo inferred price

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 exact model-specific value or customer API contract established in the reviewed sources.

Maximum input tokens
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Maximum output
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Parameters
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Release date
2024-05-23Source for Release date (opens in a new tab)

Date V2 became the default in product release v5.6.0; first preview date unverified.

Knowledge cutoff
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Reasoning
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Tool calling
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Structured output
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Streaming
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Batch processing
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Fine-tuning
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Context caching
Not collected

No exact model-specific value or customer API contract established in the reviewed sources.

Published training data
Public code with permissive licenses; separately customized customer models may use private code.Source for Published training data (opens in a new tab)

Provider statement about the completion and Protected families. Exact corpus, cutoff and checkpoint parameters are not supplied.

Access & pricing

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

Tabnine · historical managed deployment

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

UI model name only; no verified public raw-inference selector.

Access
Historical default model in the managed product. Current exact-version availability is unverified.
Regions
No model-specific serving-region inventory verified.

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

Data & enterprise terms

For Tabnine-owned models, the documentation says inference code context is discarded after response and is not used for general model training. Optional private customer fine-tuning is separate. Operational metrics/logs are retained for one week; self-hosted installations send support telemetry, while air-gapped installations can use customer monitoring. This is not zero retention for every data category.

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.

Tabnine · historical managed deployment

Not verified

No model-specific prompt-cache contract or billed cache tariff established.

How it works
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

Minimum reusable input
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

Lifetime & refresh
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

How to enable it
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

Usage fields
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

Billing rules
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

Limits & data boundaries
Not collected

No model-specific prompt-cache contract or billed cache tariff established.

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

Caching reviewed 15 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

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

Official release notes name a versioned Protected Chat Model. Proprietary/private classification is corroborated by the model-selection documentation; no public checkpoint release established.

Classification evidence (opens in a new tab)

Lifecycle dates

Protected V2 became the default model23 May 2024Source (opens in a new tab)

Sources reviewed