Deployment
Draw the control boundary where your governance requires it.
The same platform, three control models. Your institution decides how much of the stack sits inside its own walls — and can change that decision later without re-training a single user.
Private Cloud
A dedicated tenancy in India, managed by Merzal Labs.
Best for
Institutions that want a live pilot this term
- No shared infrastructure with other institutions
- Managed patching, monitoring and backups
- Live in weeks, not quarters
- Clean migration path to on-premise later
Hybrid
Knowledge, documents and retrieval stay on campus; elastic capacity handles peaks.
Best for
Most engineering colleges
- Institutional index never leaves the campus
- Burst capacity for exam and admission peaks
- Lower on-campus hardware requirement
- Recommended starting architecture
On-Premise
The entire platform runs on institution-owned hardware inside your perimeter.
Best for
Universities and institutions with existing datacentre capability
- Nothing leaves the campus network
- Institution owns the full stack
- Operates without internet access
- Sized against concurrency, not headcount
Architecture
What sits where
A hybrid deployment, drawn end to end. In an on-premise deployment every layer moves inside the campus boundary.
01 · Access
SSO, role mapping, department scope
02 · Ingestion
OCR, structuring, versioning
03 · Retrieval
Institution-owned index, on campus
04 · Reasoning
Private inference, isolated tenancy
05 · Governance
Audit log, attribution, analytics
Data ownership
The institution owns its documents, index and embeddings and can export them at any time.
No cross-tenant sharing
Nothing is pooled with other institutions, at any layer, in any deployment model.
Exit path
If the relationship ends, the institution keeps its knowledge base in an open format.