The challenge
Manufacturer applications for the BEE Star Label arrive in mixed formats, label renewals are tracked manually, and field-data validation depends on a small inspection team. With 11 official languages on the citizen-facing side, scaling intake without slipping on sovereign-cloud rules is the constraint.
How we approached it
Ajuni is scoping a pilot with the ministry where Sevak handles citizen and manufacturer intake across 11 languages, Pragna validates submitted field data, and Veer signs every state change into a sovereign audit ledger. The pilot will deploy on the ministry's sovereign cloud footprint with zero outbound egress.
What the pilot will prove
- Pilot will prove 11-language manufacturer intake
- Pilot will prove sovereign-cloud audit ledger end to end
- In scope: renewal reminders and field-data validation
- In scope: zero outbound data egress
- Scoping target: full national rollout post-pilot
Stack & guardrails
Integration & deployment
- Sovereign cloud · NIC
- Llama 3.1 70B self-hosted
- BEE portal integration
- IndicTrans2 · 11 languages
- Audit ledger · signed
- Inspector mobile bridge
Compliance & audit
- Sovereign data residency
- DPDP Act 2023
- CERT-In audit
- Ministry IT policy
Timeline
-
Week 0–2
Ministry scoping
Use cases ranked with the ministry; sovereign-cloud topology approved.
-
Week 3–5
Language pack tuning
11 Indian languages tuned against archived applications and SOPs.
-
Week 6–8
Shadow intake
Sevak observes live intake; outputs reviewed by ministry inspectors.
-
Week 9–10
Pilot review
Pilot reviewed with ministry leadership; national-rollout decision finalised.
