T-Pro or GigaChat: which one for a Russian company

Both lines are Russian, both list Russian language support and both are open for commercial use: T-Pro under Apache 2.0, GigaChat under MIT. T-Pro and T-Lite from T-Bank are fine-tuned on top of Qwen, stay in the 7B to 36B-A3B range and expect a GPU, while T-Search 36B-A3B acts as a multi-step search agent. GigaChat from Sber covers a wider range, 10B-A1.8B to 702B-A36B, runs on a CPU as well, and GigaChat3.1-Audio handles recordings up to two hours. Neither is in Ollama, so installation is manual; GigaChat was updated in September 2026, T-Pro in July 2026.

Comparison based on catalog data

ParameterT-Pro / T-LiteGigaChat
CategoryTextText, Voice assistants
DeveloperT-Bank, RussiaSber, Russia
ReleasesDec 2024 – Jul 2026Dec 2024 – Sep 2026
Sizes7B – 36B-A3B10B-A1.8B – 702B-A36B
HardwareLaptop, 1 GPULaptop, 1 GPU, Cluster
Commercial useCommercial use allowedCommercial use allowed
LicenseApache 2.0 (versions 2.0, 2.1 and T-Search; based on Qwen)MIT
RussianSupportedSupported
OllamaNoNo
Without GPUNoYes
Tasks
  • Russian-language support chatbot
  • Analysis of requests and documents in Russian
  • Answers based on the company knowledge base
  • Drafts of emails and reports
  • Russian-language employee assistant on your own server
  • Customer replies and request handling in Russian
  • Working with contracts and internal policies
  • Drafting emails and reports

Choose T-Pro / T-Lite if

  • You need a single-GPU model: T-Pro is 32B
  • Your work is banking, fintech, legal or HR in Russian
  • You need a multi-step search agent: T-Search 36B-A3B
T-Pro / T-Lite

Choose GigaChat if

  • You are a public body or must keep data inside Russia
  • You need audio: GigaChat3.1-Audio takes recordings up to two hours
  • Hardware varies: from 10B-A1.8B on a CPU to 702B on a cluster
GigaChat

Other comparisons

Need a model for your task?

An open model can run on your own server: data stays in-house, there is no per-request fee, and the model can be fine-tuned on your documents.

  1. SelectThe model and size for your task and hardware budget
  2. DeployOn your server or in a closed network, with an API
  3. Fine-tuneOn your data, or connect a knowledge base
  4. IntegrateInto your CRM, ERP, bot, website or team chat
Discuss deployment