PLLuM
Polish 4B-70B family; base, instruct and chat models
PLLuM (Polish Large Language Model) is a model family developed by a consortium of Polish research and public institutions. The project created a Polish corpus of roughly 140 billion tokens, an instruction dataset and preference data for response alignment. The current second generation (v2.2, model suffix 2512) includes 4B, 8B and 12B models in base, instruct and chat variants, plus 70B instruct and chat models. The first generation also included an 8×7B MoE architecture and non-commercial releases. Licensing varies by repository: current 4B and 12B models use Apache 2.0, while 8B and 70B models use the Llama 3.1 license.
Verified: 2026-06-23
Purchase decision (when to choose / when to avoid)
Choose if...
- Polish quality, self-hosting and data control are the priorities.
- You are building RAG or an assistant for public-sector, educational or domain documents.
- You can evaluate the current 4B, 8B, 12B and 70B variants and select the appropriate license deliberately.
Avoid if...
- You cannot review the exact model license; the family includes Apache 2.0, Llama 3.1 and older CC BY-NC 4.0 releases.
- You need a turnkey SaaS product with user administration, SLA and per-seat billing.
- Frontier coding, multimodality or complex reasoning are the main requirements.
Cost in practice (scenarios)
GPU infrastructure and operating cost; there is no single official API price for the family.
- self-host
- RAG or internal assistant
- selected quantization and inference engine
Much higher memory and inference requirements; calculate against target traffic and SLA.
- multi-GPU infrastructure
- monitoring and MLOps team
Deployment / data / enterprise
Deployment channels
- Self-host from weights published by CYFRAGOVPL on Hugging Face
- Deploy with an inference stack compatible with the selected architecture
- Choose the current 4B, 8B, 12B or 70B variant according to resources and license
Data policy
- Training on data
- With self-hosting, data and any further tuning remain under the deployer's control.
- Retention
- Determined by the organization's self-hosted configuration.
- Data residency
- Full control with on-premises or selected Polish/European cloud infrastructure.
Enterprise readiness
- Admin
- Provided by the deploying organization.
- SSO/SCIM
- Provided by the selected platform or application.
- Audit
- Provided by infrastructure, application and logging layers.
- DPA
- Depends on infrastructure-provider agreements.
- Certifications
- Depends on hosting and deployment design.