SaaS Pro Max

Context

SaaS Pro Max is a multi-tenant control plane for applications. An organization can operate several apps and environments while keeping analytics, session replay, errors, traces, feature flags, evaluations, people, revenue, communications, exports, and agent access in one system.

Problem

A typical SaaS stack spreads one incident or business question across separate analytics, error, observability, feature-flag, billing, and CRM products. The identifiers and authorization models rarely line up, so teams spend time correlating exports instead of following one user action to the error, request, release, flag, and revenue context behind it.

Approach

I built the product around one event envelope and one Postgres data model. Browser and server SDKs send typed events into the same ingest path, then each workspace reads a different view of those rows. Tenant permissions are resolved server-side for every console and API request, and the MCP layer exposes only the same permission-filtered management surface available to an operator.

What Shipped

• Web and product analytics, people timelines, goals, funnels, retention, and traffic attribution.
• Session replay, browser and Node error capture, releases, traces, logs, metrics, uptime checks, and alerting.
• Boolean and multivariate feature flags, experiments, evaluations, and quality gates.
• Revenue reporting, communications, ad destinations, data exports, and public aggregate reports.
• Browser, React, React Native, Node, Python, replay, and native-crash SDK packages plus a one-line script tag.
• A permission-filtered MCP server and Management API for agent-driven analysis and operations.

Results

• SaaS Pro Max is live at saaspro.dev with a free event allowance and no payment method required to start.
• Operators can move from a number to the people, sessions, requests, releases, and product decisions that produced it without manual cross-tool correlation.
• Application data remains exportable, session inputs are masked before replay frames leave the browser, and public sharing is aggregate-only and off by default.

Technical Notes

The repository is a pnpm monorepo with a Next.js 16 console, shared event contracts, multiple SDK packages, an MCP server, a worker, and a fully instrumented example application. The security model combines invited Google identities with WebAuthn passkeys, server-side tenant authorization, encrypted provider secrets, asymmetric ingest keys, PII permissions, and an append-only hash-chained audit ledger.