Enterprise - Future Roadmap, coming soon

Your own branded platform.

PRMNews is multi-tenant from the ground up. Ministries and organizations can run the platform with their own product standards: their branding, their feeds, their keywords, their community — on infrastructure that was designed to scale from day one.

Isolation by rigorous architecture

Designed from the ground up, not bolted on.

Tenant → team → user

Every authenticated identity resolves through a single indexed identity map to its tenant, teams, and users. Isolation is a property of the data model, not a convention developers must remember.

Managed authentication

Authentication runs on Clerk with role-based gating enforced at the API boundary. Tokens are verified server-side on every request — including realtime and upload paths.

Tenant-scoped by construction

Collections, indexes, and configuration carry tenant scope through the whole stack. A branded deployment starts from isolation that already exists — configuration, not re-architecture.

Your brand, your feeds

The platform disappears behind your name.

A white-label deployment carries your identity — your branding, your keyword set, your curated feeds — while the pipeline, signals, and private-study instruments keep working underneath exactly as they do for PRMNews itself. Your community sees your News-intelligence platform; the operations, infrastructure, and support stays ours to run.


Inherit the platform with multi-year development effort. No need to start from scratch. A small, discreet "Powered by PRMNews" is required. Furthermore, we provide all backend support to supplement managing your platform, news feeds, and users.

Diligence you can audit

The commit history is the due diligence.

An organization putting its name on a platform deserves evidence, not assurances. The engineering record is open to serious evaluators.

245
structured sprints, branch-per-sprint, PR-reviewed
21 mo
from first commit to a live private preview
3,324
backend test suites run on every change
v0.7.8
semantic releases with a maintained changelog
The machinery

Four proven technical foundations, each doing one job.

Node.js backend

An Express service layer with an OpenAPI-documented control plane and server-side identity verification on every endpoint.

Next.js frontend

A modern React application — server components, streaming, and a component system disciplined enough to ship a screen per sprint.

MongoDB Atlas

The system of record, a no-SQL document oriented database with Atlas Search and vector search over the enriched article corpus.

Convex realtime

Team chat, presence, and notifications ride a dedicated realtime layer, cleanly separated from the transactional core.

The ETL pipeline runs staged and gated, under named operational profiles, with database-backed leases that make double-firing structurally impossible. Every run is heartbeat-monitored and cancellable; every enrichment is logged with its usage and cost.