Private commercial SaaS
CampaignOps PH
A private multi-tenant campaign-operations platform for Philippine campaign geography, field coordination, lawful operational contacts, volunteers, events, incidents, area-level sentiment, election-day aggregates, dashboards, imports, and governed exports.
What this project proves
- Large multi-module SaaS architecture
- Philippine geographic hierarchy and complex import workflows
- Privacy-aware schema contracts and forbidden-field validation
- Integrated release and seeded launch-verification journeys
The problem
Campaign operations can become fragmented across geographic files, field assignments, volunteer records, events, incidents, election-day updates, and inconsistent reporting workflows.
A commercial platform must organize operations while preserving strict boundaries around individual political preference and sensitive election data.
My approach
Build tenant- and campaign-scoped modules for geography, contacts, imports, field teams, volunteers, area-level sentiment, events, incidents, election-day aggregates, dashboards, and exports.
Encode privacy constraints into schema validation rather than relying only on policy documentation.
Use a full-stack release path that validates containers, database schema, API readiness, web availability, and a seeded end-to-end operating journey.
Architecture and engineering choices
- Next.js frontend and generated OpenAPI TypeScript client
- FastAPI application services and PostgreSQL 16
- Celery workers with Redis
- Docker Compose development and release-candidate environment
- Role, permission, tenant, campaign, geography, and audit controls
Truthful scope and boundaries
- The source code and detailed commercial strategy remain private.
- The product is not designed to store a named person's inferred or reported political preference.
- Public materials use synthetic data and disclose only controlled product-level information.