The Unified DevOps & FinOps Control Plane is a multi-tenant SaaS web application that gives developer and platform teams a single pane of glass over four concerns that are usually scattered across separate tools: version control and release history, CI/CD deployment records and rollback actions, server and storage health, and estimated cloud billing with FinOps projections.
The product is built for organizations that run multiple projects across Development, Staging, and Production environments and need to answer, in one place: what shipped, did it succeed, is the infrastructure healthy, and what will this month cost. Each organization is a tenant with strict data isolation, role-based access control, and an encrypted credential vault for its integrations.
This document is the System Requirements Document for the project named devops-finops. It specifies the current delivery: the accepted pages, the ingestion endpoints and background workers, the tenant-isolation and security model, and the dark-mode-first developer UI.
The control plane is delivered as a Next.js (App Router) web application with a shared backend process that serves the application APIs, the GitHub webhook receiver, the server-agent telemetry endpoint, and the domain modules behind the dashboard. PostgreSQL stores all tenant-scoped application data under Row-Level Security. Redis with BullMQ runs the background jobs: processing GitHub push/deployment events and the scheduled billing and cloud-cost sync.
The active human actors are the Organization Owner, Organization Admin, Developer, and Viewer. Anonymous visitors reach the Landing page; new users enroll through Sign Up and become the OWNER of a new organization; returning users verify identity through Login. All dashboard pages require login, and the Integrations page is restricted to OWNER and ADMIN.
Current delivery covers: organization and project context switching, the Overview KPI band and release timeline, deployment records with pipeline status, build durations, searchable error logs and one-click rollback, infrastructure and storage health with forecasts and deployment markers on latency/error graphs, billing and FinOps with month-to-date spend, month-end projections, per-environment breakdowns and anomaly alerts, integration credential management in the encrypted vault, and team and settings with member roles.
Removed from scope
The product is a first-party, application-owned control plane. Identity is application-owned: a new user self-enrolls through Sign Up and creates an organization as its OWNER; returning users verify identity through Login before reaching any protected organization data. The Landing page is the anonymous entry surface and does not expose tenant data.
All dashboard destinations (Overview, Deployments, Infrastructure & Storage, Billing & FinOps, Team & Settings) require login. Integrations is additionally restricted to the OWNER and ADMIN roles because it manages encrypted credentials and API keys. Destructive actions — production rollbacks, deleting servers, and updating API keys — are restricted to OWNER and ADMIN across the product, regardless of which page surfaces the control.
Data enters the system through two machine-facing boundaries that are not human pages: the GitHub webhook receiver at /api/webhooks/github and the server-agent telemetry endpoint at /api/v1/ingest/metrics. Both are owned by the shared backend. The scheduled billing and cloud sync worker runs in the background on BullMQ and writes daily cost breakdowns and month-end projections that the Billing & FinOps page reads.
Nothing in the current scope is deferred to a future horizon; the future section records no additional accepted requirements.
sk_live_...). Accessible to OWNER and ADMIN only.FR-1 — Multi-tenant control plane foundation (explicit) As an Organization Owner I should have a multi-tenant SaaS control plane built with Next.js (App Router), TypeScript, Tailwind CSS, Shadcn UI, PostgreSQL (Prisma or Drizzle ORM), and Redis (BullMQ) for background jobs, so that my organization's DevOps and FinOps data lives in one application.
FR-2 — Single-pane-of-glass dashboard (explicit) As a Developer I should see version control, deployments, infrastructure health, and FinOps unified in one dashboard, so that I do not switch between separate tools.
FR-3 — Version control and release timeline (explicit) As a Developer I should track Git commits, branches, PR authors, and environment mappings for Dev, Staging, and Production, so that I know what shipped where.
FR-4 — Deployment records with pipeline status and durations (explicit) As a Developer I should see deployment records with CI/CD pipeline statuses (Queued, Building, Success, Failed) and build durations, so that I can judge release health.
FR-5 — Searchable error logs (explicit) As a Developer I should search deployment error logs, so that I can find and fix failures.
FR-6 — One-click rollback (explicit) As an Organization Owner or Organization Admin I should trigger a one-click rollback from a deployment record, so that I can recover a bad release quickly.
FR-7 — Server and storage health (explicit) As a Developer I should see real-time CPU, RAM, network I/O, disk usage %, and storage exhaustion forecasts (for example "Disk full in 12 days"), so that I can act before an outage.
/api/v1/ingest/metrics and rendered on Infrastructure & Storage.FR-8 — Deployment markers on latency/error graphs (explicit) As a Developer I should see deployment markers overlaid on latency/error graphs, so that I can correlate incidents with releases.
FR-9 — Estimated billing and FinOps (explicit) As an Organization Owner I should see month-to-date cloud spend, linear/AI month-end bill projections, per-environment cost breakdowns, and threshold anomaly alerts, so that I can control cost.
FR-10 — Shared-database, shared-schema tenant model (explicit)
As an Organization Owner I should have every core table (organizations, projects, repositories, deployments, servers, server_metrics, billing_snapshots, integrations) carry an organization_id, so that tenant data is structurally scoped.
FR-11 — PostgreSQL Row-Level Security (explicit) As an Organization Owner I should have RLS policies enforced on all tenant-scoped tables, so that one tenant can never read another's data.
FR-12 — RBAC roles (explicit) As an Organization Owner I should assign OWNER, ADMIN, DEVELOPER, or VIEWER roles to members, so that access matches responsibility.
FR-13 — Destructive action restriction (explicit) As an Organization Owner or Organization Admin I should be the only roles able to perform production rollbacks, delete servers, and update API keys, so that destructive changes are controlled.
FR-14 — Encrypted credential vault (explicit) As an Organization Owner or Organization Admin I should store GitHub App installation tokens, AWS Cross-Account Role ARNs with unique ExternalId, and server agent ingest keys through an abstraction layer using AES-256-GCM envelope encryption, so that tenant credentials are protected at rest.
FR-15 — GitHub webhook receiver (explicit)
As a Developer I should have /api/webhooks/github verify X-Hub-Signature-256, map the repository to the corresponding organization_id, and enqueue deployment/push events into BullMQ, so that release data flows in automatically.
FR-16 — Server agent telemetry endpoint (explicit)
As a Developer I should have /api/v1/ingest/metrics authenticate via a tenant-scoped Bearer API key (sk_live_...), validate payload fields (cpu_percent, ram_used_mb, ram_total_mb, disk_used_gb, disk_total_gb), and batch-insert into server_metrics, so that server health is current.
FR-17 — Scheduled billing and cloud sync worker (explicit) As an Organization Owner I should have a scheduled BullMQ worker fetch or simulate daily cloud cost breakdowns per environment and calculate a projected month-end total, so that FinOps figures stay current.
billing_snapshots are written and the projection updates on Billing & FinOps.FR-18 — Dark-mode-first developer UI (explicit) As a Developer I should use a sleek, high-density dark-mode-first UI (Linear/Vercel aesthetic) with Slate/Zinc neutral tones, JetBrains Mono for commit hashes, IP addresses, and logs, and crisp status badges, so that dense data is fast to scan.
FR-19 — Sidebar and top bar layout (explicit) As a Developer I should have a left sidebar with Organization Switcher, Project Selector, and navigation (Overview, Deployments, Infrastructure & Storage, Billing & FinOps, Integrations, Team & Settings), and a top bar with a live environment filter (All, Production, Staging, Development) and time-range selector (1h, 24h, 7d, 30d), so that I can move and scope quickly.
FR-20 — KPI Summary Cards (explicit) As a Developer I should see KPI Summary Cards on the Main Overview View, so that I get an at-a-glance status.
FR-21 — Self-service enrollment and organization creation (required_inference) As a new user I should complete self-service enrollment and create an organization as OWNER, so that I can begin using the control plane.
FR-22 — Returning identity verification (required_inference) As a returning user I should verify my identity before access to protected organization data, so that tenant data stays private.
FR-23 — Role-gated destructive and credential actions (required_inference) As an Organization Owner or Organization Admin I should be the only roles able to perform rollbacks, delete servers, update API keys, and manage integration credentials, so that sensitive operations stay controlled.
/api/webhooks/github.X-Hub-Signature-256, maps the repository to the organization_id, and enqueues the event into BullMQ./api/v1/ingest/metrics with a tenant-scoped Bearer key (sk_live_...).cpu_percent, ram_used_mb, ram_total_mb, disk_used_gb, and disk_total_gb, and batch-inserts into server_metrics.billing_snapshots, and Billing & FinOps reflects the new figures.The creative direction is authoritative: editorial swagger for a dark control plane, after Tobias van Schneider. Dark editorial ground, one hot accent, oversized type — a dense dashboard that feels authored, not templated.
#0E0F11 (near-black ground, ~80% of the page)#17181B#F2EFE9 (warm off-white, ~15% with hairlines)#F2EFE9#FF4A1C (hot orange, one signal only — e.g., the active environment filter rule)#8A8D93#16A34A, warning #FACC15, critical #EF4444The public entry is a full-bleed near-black first screen. A serif headline — "Every deployment, server and bill in one view" — spans the viewport in two lines at 64px mobile to 96px desktop, set in Instrument Serif with tight leading. A single hot orange #FF4A1C rule runs under the headline, with the "Open control plane" CTA at left. The subline reads "Track releases, infrastructure health and cloud spend across every environment." Below, a restrained band presents the four unified concerns as hairline-ruled labels with status dots, echoing the sidebar rows of the dashboard. No rounded glass cards, no gradients, no blue-indigo accents, no decorative illustration — the composition is type, rule, and data.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
organizations, projects, repositories, deployments, servers, server_metrics, billing_snapshots, integrations) includes organization_id; PostgreSQL RLS policies enforced on all tenant-scoped tables.X-Hub-Signature-256 verification on /api/webhooks/github.sk_live_...) on /api/v1/ingest/metrics./api/webhooks/github and /api/v1/ingest/metrics.X-Hub-Signature-256.sk_live_...)./api/v1/ingest/metrics with a tenant-scoped key.sk_live_...) used by the server agent.
Track releases, infrastructure health and cloud spend across every environment.
Unified concerns
For developer and platform teams running multiple environments.

Track releases, infrastructure health and cloud spend across every environment.
Unified concerns
For developer and platform teams running multiple environments.
No comments yet. Be the first!