Otwieramy archiwum…
Initiative I·02Phase: preparation
eClerk. A digital workflow that never leaves the institution.
A digitisation platform for offices, foundations, social services, schools and NGOs. The Bielik AI assistant runs locally. Data never leaves the institution. Compliance with GDPR, NIS2, EU AI Act and KSC built in from day one of design.
17 modules · one platform · zero cloud
Everything required — under the institution's control.
Documents, routing, AI assistant, leave, reports, cybersecurity, ePUAP integrations. No window switching, no cloud, no compromise.
GDPRNIS2AI ActKSCISO 27001
Why eClerk
Three principles that set this platform apart.
01
Offline ≠ outdated
The AI runs on the institution's own server. Data never leaves the building or the internal network. This is not an exemption from modernisation — it is its strongest form.
02
Compliance from day one
The system is designed from the ground up for GDPR, NIS2, EU AI Act and KSC. Auditability is not an add-on — it is the foundation of the architecture.
03
A Polish language model
Bielik 7B/11B understands Polish administrative language better than any English-language model. Locally, auditable, with no external APIs.
Interactive module explorer
17 modules · one ecosystem.
Click a module to see its details. Switch to graph view to see dependencies between modules. Each module is marked with its development phase — from specification to prototype.
Module status:Specification · 5In design · 9Prototype · 3
❒
M01
Documents
Letters don't disappear. Cases don't die in someone's inbox
Every incoming and outgoing letter follows the same track: draft → approval → signature → archive. The workflow is visible to everyone, statutory deadlines (KPA) count themselves, and the decision lives on paper, not in the manager's head. You open documents in Word or OnlyOffice — no downloads, no „final-final-2-revised” versions. You apply a qualified PAdES signature in the browser. PDF/A for the state archive — automatically.
Planned features
- ◆AI-powered JRWA auto-classification
- ◆OCR for scanned documents
- ◆Trash with retention (GDPR art. 17)
- ◆WebDAV native edit — Word / LibreOffice
- ◆OnlyOffice / Collabora in the browser
- ◆Qualified PAdES signature
- ◆PDF/A export for the state archive
Independent core module
Technology stack
- Frontend
- Next.js · Tailwind · TypeScript
- Backend
- Node.js · PostgreSQL · Redis
- AI
- Bielik 7B · Llama.cpp · Trurl
- Infrastructure
- Linux on-premise · Docker · K3s
- Security
- AES-256 · OIDC · MFA · audit log
- Data formats
- JSON · XML · PDF/A · PAdES
Hardware requirements (on-premise reference installation)
- RAM
- min. 32 GB (64 GB recommended)
- CPU
- 8 cores / 16 threads
- GPU
- NVIDIA RTX 3090 / 4080 (for AI)
- Disk
- 1 TB SSD NVMe + backup
- OS
- Linux Debian / Ubuntu Server LTS
- Network
- 1 Gbps LAN, internet optional
Pilot programme
First deployments in a non-profit model
In the first round we plan to deploy eClerk in selected partner institutions — at no licence cost, with full implementation support, training and ongoing updates.
Selection is mission-driven: organisational readiness, staff engagement, potential for local impact. The first partners co-create the platform through feedback and user testing.
First round
up to 10 partners
Deployment time
30–90 days
Support
on-site + remote
Training
included in pilot
Updates
automatic
Model
non-profit