VillageOS — gram panchayat management software for rural India

Government-grade by architecture, not by adjective.

Public money and citizen records demand more than a login page. These are structural decisions in VillageOS, not settings.

• Database-per-village isolationEach village runs on its own dedicated PostgreSQL database — zero shared tables, no possible data leakage between villages.
• Immutable financial ledgerThe tax ledger is append-only; voids are new entries with mandatory reasons, excluded from aggregates, logged forever.
• Granular RBAC24 atomic permissions enforced on every endpoint — clerks enter data, the President approves spending, deny-by-default everywhere.
• Encryption throughoutAES-256 at rest and in transit, RSA-2048 OAEP login encryption, httpOnly JWT cookies, and full-strict TLS edge to origin.
• Mandatory 2FATOTP two-factor on operator logins with recovery codes, lockout after failed attempts, and forced reset of seeded passwords.
• Privacy by designNo sensitive national ID numbers are collected anywhere — registration, imports, or receipts — keeping villages clear of compliance risk.
• Nightly encrypted backupsOff-site with 7-day daily and 28-day Sunday retention, plus automated failure alerts.
• Hardened uploadsEvery file is validated by real header bytes, not MIME type — forged uploads are rejected at the boundary.
• Email anti-spoofingSPF, DKIM, and DMARC on villageos.in so receipts and alerts can't be forged in residents' inboxes.