ProGate

Problem

The problem

Residential and organizational access depends on security teams, residents, visitors, administrators, billing, and incident response working from the same source of truth. Fragmented tools make validation slow, permissions inconsistent, and operational events difficult to audit.

System model

A connected operational flow

Context

Coordinating access across roles

ProGate brings resident, security, visitor, administrative, billing, and incident workflows into one operational system. The work called for a backend that could represent permissions and events without exposing sensitive security internals.

Responsibility

Backend architecture with an AI layer

I focused on the backend architecture and the AURA voice-assistant integration, shaping the system around role-aware actions, reliable state changes, and real-time operational behavior.

The design keeps the engineering story at the level of workflows and accountability: access validation, digital access, payments, administrative controls, and incident response can be understood from a common source of truth.

Engineering decisions

Make operational state inspectable

FastAPI supports a focused API layer, PostgreSQL provides durable operational records, and Redis supports coordination where timely state matters. The result is a platform narrative centered on reliable multi-role operations rather than isolated screens.