ProjectPulse: Engineering an ITIL-Aligned IT Project Portfolio Management Platform

Most IT teams manage their project portfolios across a tangle of spreadsheets, emails, and status meetings with no single source of truth for budget health, milestone risk, or open change requests. We built ProjectPulse to fix that: a self-hosted, ITIL-aligned PPM platform that gives any PMO office a unified dashboard for every project, risk, budget entry, and governance decision.

The Portfolio Visibility Problem

Ask a project manager for the current budget variance across their active portfolio and you will typically get a pause, a spreadsheet, and a caveat. Project details live in disconnected places: status in one tool, budget in another, risks tracked nowhere at all. Scope changes get approved informally over email and never make it into a formal record.

The result is predictable. Budgets overrun because no one is watching the ledger in real time. Milestones slip because overdue deliverables are not surfaced until a meeting. Risks go unscored and unmitigated until they become incidents. And when an auditor asks for a change log, there is nothing to show.

Enterprise PPM platforms like Microsoft Project and Planview solve this, but they carry significant licensing costs and months of implementation overhead. ProjectPulse was built to close that gap: a lightweight, self-hostable alternative that tracks every project, scores every risk, enforces budget accountability, and preserves a complete audit trail, running on nothing more than a Supabase project and a web browser.

What is ProjectPulse?

ProjectPulse is a full-stack, browser-based IT Project Portfolio Management system for enterprise PMO offices. It centralizes the entire project lifecycle from initiation through closure in a single interface, backed by a real-time executive dashboard that surfaces portfolio health, budget variance, overdue milestones, and open risk scores at a glance.

Every project receives a sequential human-readable identifier (PPM-#####) assigned by a database trigger. Actual spend is calculated automatically from an itemized budget ledger rather than manually entered, which prevents financial drift. Risk is tracked on a formal 5x5 scoring matrix where probability and impact produce a composite severity score. And every state change across the entire portfolio is recorded in an append-only audit log with actor attribution and timestamp.

ProjectPulse completes an enterprise IT governance trilogy alongside InfraNode (IT asset management) and FlowDesk (IT service desk and SLA management), giving organizations a unified governance layer across assets, services, and projects.

How ProjectPulse Works

1. Register and Govern Projects

Project Managers create projects from the registry, assigning health status (On Track, At Risk, Off Track, On Hold, or Completed), a planned budget, and a target timeline. The platform generates a PPM-##### identifier automatically and begins tracking actual spend as budget entries are logged to the ledger. The executive dashboard reflects portfolio health in real time with a donut chart and side-by-side budget bars for every active project.

2. Track Milestones and Surface Overdue Risk

Every project carries a milestone registry with target dates and status flags. Milestones that pass their due date without completion are automatically surfaced on the executive dashboard alert watchlist, giving PMO managers immediate visibility without manual chasing. Status transitions (Not Started, In Progress, Completed) are timestamped and logged to the project event trail.

3. Score and Monitor Portfolio Risk

Each risk is entered on a 5x5 scoring matrix: a probability score from 1 to 5, an impact score from 1 to 5, and a documented mitigation plan. The composite score maps to a severity band (Low, Medium, High, or Critical). All open risks across the portfolio surface on the executive dashboard ranked by score, so the highest-severity items never get buried in a project-level view.

4. Control Budget, Scope, and Change Requests

Budget entries are logged as itemized ledger items per project. Variance (planned minus actual) is calculated continuously and flagged when a project exceeds its budget. Scope changes go through a formal workflow: team members submit a change request with justification and scope impact description, and PMO Admins or Project Managers approve or reject with a recorded reason. Every approval and rejection is captured in the audit log.

Technical Case Study: Architecture Decisions

ProjectPulse is built on the Next.js 15 App Router with TypeScript throughout. Data is fetched in React Server Components and mutated through Server Actions, which also write the corresponding audit events to the project_events table. This keeps all business logic server-side, ensures the audit trail is always consistent, and prevents client-side state from diverging from the database record.

The backend is Supabase PostgreSQL organized around eight tables: profiles, projects, milestones, risks, budget_entries, stakeholders, change_requests, and project_events. Every table has Row Level Security enabled, enforced by a get_my_role() security-definer helper. Stakeholders are scoped to only their assigned projects at the database layer, not just the UI. Actual spend on each project is rolled up from budget_entries automatically rather than stored as a field, which eliminates an entire class of financial inconsistency.

One deliberate governance decision was to model every destructive or consequential action as a workflow rather than a direct operation. Scope changes require a formal change request that progresses through an approval state machine. Archived projects and completed milestones are preserved rather than deleted. The audit log is strictly append-only. These patterns mean that ProjectPulse is not just a tracker but a system of record that can withstand a governance review.

Conclusion & Next Steps

ProjectPulse shows that enterprise portfolio governance does not need enterprise pricing. A formal risk register, automatic budget variance tracking, RACI accountability, governed change control, and a complete audit trail can all run on a single Supabase project accessible from any web browser.

The live demo is available at projectpulse.riyadhalmahmud.tech and the full source code is published on GitHub. Whether you are a PMO manager looking for a structured alternative to spreadsheet-driven tracking, a developer studying governance-first architecture, or a team that needs a single source of truth for portfolio health, ProjectPulse is a working, auditable foundation to build on.