Delta Registry — Regulatory & Compliance Monitoring (28 tools) MCP server

Delta Registry — Marketing Website

The public marketing site for Delta Registry — architecture explainer, pricing overview, and delta-engine internals for the full fleet of pay-per-event Apify Actors. Built with the Next.js App Router, React 18, and Tailwind CSS.

Run it locally

npm install
npm run dev

Then open http://localhost:3000. npm run build && npm run start runs the production build; npm run typecheck and npm run lint run TypeScript and ESLint respectively.

What's here

(Header, Hero, ArchitectureMatrix, HowItWorks, EconomicEngine, IntegrationTerminal, DeltaEngineDocs, FaqAccordion, Footer) in render order; there is no other route.

• app/ — Next.js App Router pages and layouts. app/page.tsx composes every section

(the fleet filter, the JSON delta-viewer playground, the accordion, the code-language tabs) are client components ('use client'); everything else renders on the server.

• components/ — one React component per site section. Sections that need interactivity

exports the real ACTORS array plus derived constants (ACTORCOUNT, DOMAINS, GITHUBREPO_COUNT).

• lib/ — the site's data contract. lib/types.ts defines the Actor shape; lib/actors.ts

• middleware.ts — edge middleware for the deployed site.

Architecture: lib/actors.ts as the single source of truth

Every number, price, badge, and filter option rendered anywhere on this site — the hero stat counters, the fleet catalog cards, the pricing comparison table, the BYOK disclosure, the integration workbench's actor tabs, the FAQ's live counts — is read from the same ACTORS array in lib/actors.ts, never hand-typed a second time in a component. Each Actor record carries slug, title, domain, jurisdiction, dataSource, pricing[] (per-event-type price and unit), deltaEvents[], storeUrl, githubUrl, byok ('required' | 'optional' | 'none', plus byokDetail when applicable), updateFrequency, and isPublic.

This is deliberate, not incidental: it means a component can never drift out of sync with the real fleet, and every price or claim on this marketing site traces back to one file that's independently re-verified against each actor's own Apify Store listing and README whenever the fleet changes. When an actor's price changes or a new actor launches, updating lib/actors.ts is the only change needed — every section that references it (filters, cards, comparison tables, code snippets) updates automatically.

Security headers & CSP model

next.config.js sets standard hardening headers (X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Strict-Transport-Security, a restrictive Permissions-Policy) globally. The Content-Security-Policy is set separately, per-request, in middleware.ts — not as a static header — because a static script-src 'self' blocks Next.js's own inline hydration/bootstrap scripts and breaks the app at runtime. Instead, middleware.ts generates a fresh nonce on every request, threads it to Next.js via the x-nonce request header (read in app/layout.tsx), and scopes the CSP to that nonce (script-src 'self' 'nonce-' 'strict-dynamic') rather than falling back to 'unsafe-inline', which would defeat the policy's purpose. 'unsafe-eval' is included only when NODE_ENV === 'development' (webpack's Fast Refresh needs it) and is never present in the production CSP.

Shortened. The full README is on GitHub.