Back to cases
SaaS & AI OperationsIn validation

Coven — Marketing AI Control Tower

Internal SaaS under validation, with a Next.js frontend and tenant-isolated FastAPI backend for governed marketing operations.

System screenshots are not available yet.

Stage
Internal validation
Authenticated smoke
2026-05-05
API, not a customer outcome

Challenge

Centralize approvals, policies, channels, and costs without presenting implemented surfaces as customer outcomes.

Solution

The code mounts auth, operator/control tower, approvals, social, Meta Ads, content velocity, workspace, analytics, and subscription surfaces.

Available evidence

  • Separate Next.js frontend and FastAPI backend
  • Mounted operations, approvals, workspace, analytics, social, and billing routers
  • An authenticated API smoke validated auth, dashboard, ROI, and billing on 2026-05-05
Source
fal-ai-agency@d0fe4f1 — docs/runtime-matrix.md, docs/deploy-matrix.md, and authenticated API smoke dated 2026-05-05
Period
Development in 2025-2026; smoke on 2026-05-05; public endpoint reviewed on 2026-07-15.
Method
Review of routers, runtime/deploy matrices, smoke artifact, and public Home.
Context
Internal dogfooding; mounted code does not prove provisioned external integrations or commercial performance.
Verified on

Limitations

  • The current audit did not log in.
  • The historical smoke validated the API, not the complete BFF/cookie boundary.

Architecture & Stack

The stack reflects the recorded implementation and this project's context; it is not a generic guarantee of resilience, performance, or scale.

  • Next.js
  • TypeScript
  • FastAPI
  • PostgreSQL
  • Stripe
  • Sentry
  • Docker

Core Features

  • Operator/control tower with runs, actions, and policies
  • Human approvals and workspaces
  • Social, Meta Ads, analytics, and billing surfaces

Is your context a fit for a responsible delivery?

Next case
Coven — Marketing AI Control Tower | F.A.L A.I Agency