Prism research terminal

Public-equity research, structured like a terminal.

Single-name briefs, head-to-head compares, portfolio diagnostics, and theme ranking with verified inputs and visible guardrails.

Public equities and ETFs only. No account required.

Coverage Brief, compare, portfolio, and theme workflows in one workspace.
Guardrails Verified inputs and missing evidence stay visible in the read.
Scope Public equities and ETFs only in the current build.

Live sample

Actual brief output, not a marketing mockup.

This panel loads from Prism's live sample endpoint and shows the real output shape with coverage and guardrails.

Loading live sample... Fetching current market context...
Single-stock brief

MSFT ยท Loading...

Pulling a current sample from Prism's stock brief engine.

Sample loading Confidence: Loading Prism is building the latest sample now.
Current price$--
Research score-- / 100
Strongest signalLoading...
Weakest signalLoading...
Coverage Loading...
Security type Loading...
Sources cited Loading...

Core thesis

This panel updates from the live sample endpoint once the page loads.

Why the rating holds up

  • Loading current sample strengths...

Risks flagged

  • Loading current sample risks...

What changes the call

  • Loading current sample change conditions...

Research modules

Start from the workflow, not a blank screen.

Each module opens on a seeded example so the product is inspectable immediately.

Access

Public beta now. Synced desk later.

Prism is free in the current beta while the core research frame tightens. The future paid layer is for continuous use, not for gating the first brief.

Available now

Full research workspace.

Brief, compare, portfolio, and theme modules are already live in the public beta.

Stored locally

Desk memory stays on-device.

Saved names, recent briefs, and run-to-run changes stay in local workspace memory unless you copy them out.

Future paid layer

Built for ongoing research.

Synced desk history, cross-device saved work, monitored change tracking, and alerts belong in the paid layer when the workflow is ready.