Public sector platform
In developmentCivicOS
CivicOS is the product lane for our public-sector work: a modular digital government platform built on Django and Wagtail, designed for municipalities and civic organizations that need a secure CMS, forms, citizen portal, notifications, workflows, and audit logging without rebuilding everything from scratch.
Flagship product in progress
CivicOS is still evolving, but it already defines the reusable public-sector foundation we want to keep shaping. Services fund the work today; CivicOS is the platform we are building toward.
Why it exists
GovStack-aligned building blocks for municipal websites, citizen services, workflows, and audit-ready operations.
The product lane exists for work that should compound over time. Instead of re-explaining the same foundations on every engagement, we build reusable systems once and keep improving them.
Product surface
What CivicOS is actually trying to contain
This is a module map for a product still in development — not a live municipal dashboard screenshot. The goal is a reusable civic foundation, not a one-off rebuild every time.
01
Public website and CMS
Pages, structured content, accessibility, multilingual support, and publishing governance.
02
Forms and service requests
Resident-facing forms, intake flows, review queues, and status-aware submission handling.
03
Workflows and approvals
Internal routing, review steps, escalation points, and ownership across departments.
04
Notifications and audit trail
Triggered updates, reminders, delivery history, and accountable change records.
System sketch
CivicOS core
A reusable operating layer for public websites, forms, approvals, notifications, and accountable record-keeping.
Content structure · Service workflows · Operational accountability
01
CMS
Structured pages, publishing roles, multilingual content, and public updates.
02
Forms
Requests, intake, validation, status-aware submissions, and service capture.
03
Workflows
Routing, review queues, handoffs, approvals, and escalation logic.
04
Notifications
Email or internal updates that keep staff and residents informed.
05
Audit trail
Change history, accountability, and the operational record behind each action.
Core strengths
01
Modular building blocks
02
Accessible and bilingual
03
Audit-ready operations
04
Reusable civic workflows
Defined vs evolving
Already defined
- GovStack-aligned product direction
- Core CMS, forms, workflow, and audit-logging boundaries
- Django/Wagtail foundation and maintainable stack choices
Being shaped now
- Module packaging and admin boundaries
- Deployment patterns for smaller public-sector teams
- Reusable implementation path informed by current delivery work
Example workflow
The product is meant to reduce operational drift, not just publish pages.
This is the kind of flow CivicOS is being shaped to support across public-sector sites, forms, and approvals.
01
Resident or staff input enters through structured forms or managed content
02
The system routes the request or content into the right review queue
03
Approvers, editors, or operators act without losing ownership history
04
Notifications and audit records keep the process visible and maintainable
Stack
Built on tools that keep the product maintainable.
Django · Wagtail · PostgreSQL · Celery · Redis · GovStack
Delivery lineage
Civic content patterns from nonprofit and community delivery.
Apoti and BIBHW shape the public-facing trust, CMS, and handoff model. Enterprise and product engagements elsewhere in the portfolio reinforce the operating discipline CivicOS still needs.
01
Nonprofit
A practical nonprofit platform plan that cleans up public claims, prepares an editable CMS model, and keeps infrastructure lean. Reusable signal: Nonprofit CMS/content strategy and low-cost infrastructure.
02
Faith Community
A faith-centered community platform for BIBHW with clear content structure, prayer-community messaging, launch operations, and editor handoff. Reusable signal: Community portal, editor workflow, and CMS handoff.
Want to talk through a product idea?
Whether the answer is CivicOS, Recurr, Kavora Resume, or something entirely new, we can help shape the right product lane.