System architecture
How the OPID prototype is structured
A simple civic-tech architecture for submission, review, identity generation, public verification and government intelligence.
Layer 1
User access layer
Property owners, agents, developers, citizens, institutions and government officers access role-specific flows.
Layer 2
Frontend application layer
Next.js / React App Router interface provides responsive submission, verification and dashboard screens.
Layer 3
Supabase backend layer
Supabase services and API/server functions handle data access and prototype workflow operations.
Layer 4
Database layer
PostgreSQL stores property submissions, developer projects, OPIDs, audit logs and dispute flags.
Layer 5
Government/admin review layer
Demo officers approve, reject or flag records. Production access would use Supabase Auth and RBAC.
Layer 6
Public verification layer
Approved OPID records are searchable without exposing sensitive applicant or owner details.
Layer 7
Future integration layer
Future API-based integration with authorised government systems is possible subject to approval.
Technology stack
- Frontend: Next.js / React
- Backend: Supabase services and API/server functions
- Database: PostgreSQL
- Auth and access control: planned Supabase Auth and role-based access control
- Security: TLS, encryption at rest through managed cloud services, audit logs, RLS policies
Future integration position
No live government integrations currently; future API-based integration is possible subject to approval, data-sharing agreements and security requirements.