Skip to content
Jan Luigi RiveraReal person, real projects
All work

SENTRO

Synchronized E-Governance Network for Transparent Records and Oversight

A single-barangay system, re-engineered into a platform

  • Platform
  • In development

An open-source platform built on a fork of the MIT-licensed BarangayOS, being re-architected from one system for one barangay into a multi-tier platform. Done so far: records, case tracking, finance, role-based access and cloud multi-tenancy with server-enforced isolation. Next: the sync engine that lets offline barangay nodes feed a central instance.

private deployment

Recorded on the local two-tier stack — one barangay node, one city hall, synthetic accounts and records.

What it is

Every barangay hall in the Philippines keeps the same records — residents, certificates, blotter entries, clearances — and almost every software attempt at it builds one system for one barangay. That works until the city or municipality above it wants to see across all of them, which is the moment the model breaks.

SENTRO is being built to change that: one platform where each barangay is its own tenant, with a cloud instance for the city or municipal hall above them.

Built so far

  • Records for residents and the documents a barangay issues.
  • Case tracking.
  • Finance.
  • Role-based access.
  • Cloud multi-tenancy, with isolation enforced on the server, not in the interface — each barangay sees only its own records.

Why fork rather than start over

SENTRO is a derivative of BarangayOS by Rodney Dela Cruz, used under the MIT licence. BarangayOS is a genuinely good single-barangay system. Rewriting from zero would have meant re-solving the domain — what a barangay clearance actually needs on it, how a blotter entry is structured, what the certificate templates have to say — which is the part that takes local knowledge and takes the longest to get right.

The domain modelling was worth keeping. The single-tenant, single-location architecture was not.

Next: offline barangay nodes (not built yet)

The design goal is a node in each barangay that keeps working with no connection, and syncs its records up to the cloud instance when a link is there. That sync engine is the next phase on the roadmap and is not built. Where the design stands:

  • Conflicts. When a barangay and the hall change the same record while apart, the last edit wins.
  • Which copy is the master. Not decided yet.

Status

In development. No barangay or municipality is using it yet.