Barazia
Less networking.
More progress.
I founded Barazia to help people move from finding collaborators to making progress together. The platform is designed around shared interests, focused asks, and time-bound alliances. I own the product direction and full-stack engineering, including the systems behind trust and safety.
Inside the build +
From product concept to system design.
My implementation spans collaborator discovery, project asks, local networks, and meetups. I also designed the database, server-side authorization, moderation controls, and release-verification workflows.
Responsive interfaces. Predictable behavior.
I improved discovery pages with loading placeholders, protection against out-of-order requests, and smoother data transitions. Reducing layout shifts helps the interface stay steady as content arrives.
Release decisions backed by evidence.
I built release-verification workflows with GitHub Actions and Cloudflare. Limited canary releases, deliberate failure tests, and preserved verification records support reviewable decisions before wider rollout.

Homepage preview · Opens Barazia in a new tab
BACKEND AUDIT SCOPE
Security beyond the interface.
My backend work covers server-side authorization and content-safety checks, including disguised unsafe input. Enforcing these rules in the database protects write operations even when requests bypass the interface.
PostgreSQL · Supabase · Development and validationRELEASE PREPARATION
Stage the change.
Staged canary workflows check a limited release before wider rollout.
Test the failure.
Fault-injection drills deliberately test how the system handles failure.
Keep the evidence.
Immutable records preserve what was tested and support traceable release decisions.