Ask your app anything.
From inside ChatGPT or Claude.
Prism reads your live Crossdeck workspace — revenue, entitlements, errors, analytics, database read-cost and customer identity — joined by identity. So you can ask the questions no single tool can answer, in the assistant you already have open.
Read-only · OAuth sign-in, no key to paste · Included with Crossdeck
The questions that used to need three tools and an afternoon
"Which paying customers did the errors hit?"
"Why did my database reads spike today?"
"How's my app doing today?"
Why a single-layer tool cannot answer these
Every tool in your stack owns one layer and stops at its edge. Your error monitor knows an exception fired four hundred times; it has no idea which of those people pay you. Your billing dashboard knows a customer cancelled; it cannot tell you they hit a failed checkout three days earlier. Your database profiler knows which query is expensive; it cannot name the account that ran it.
The join those answers need is identity — and identity is the one thing none of those tools own. Crossdeck does. The SDK establishes who someone is, the payment rails say what they pay, the error capture says what broke for them, and the read meter says what they cost to serve. Because all four land on one customer record, the question "which paying customers did this error hit, and what are they worth?" is a lookup rather than a project.
Prism is the surface that hands that joined answer back to you — to your AI, or to your backend.
How it works
-
1
Install the SDK
One install gives Crossdeck identity, revenue, errors and analytics on one timeline. Prism has nothing to read until this is in place — it is a lens over your data, not a separate data source.
-
2
Connect your assistant
Prism is a Model Context Protocol server, so it plugs into any MCP client — ChatGPT, Claude, Cursor. You sign in with OAuth 2.0; there is no API key to copy into a chat window, and access is revocable from your dashboard at any time.
-
3
Ask in plain language
Your assistant picks the right tools, and Prism answers from your live workspace. Ask follow-ups the way you would ask a colleague — the context carries.
Prefer code? The same intelligence is a read API your backend can call directly — same data, same permissions, no AI in the loop. Both paths are documented in the Prism developer docs.
What Prism can read
Every tool is read-only, scoped to your workspace, and answers about your own data.
Revenue
Recurring revenue, revenue averages, and the portfolio view across every project and rail — Apple, Google Play and Stripe in one figure.
Customers
A single customer's full picture, your customer census, and a ranked leaderboard — by value, by cost, by whatever the question needs.
Errors, by who they hit
The impact of an error expressed in people and money: who it affected, how many of them pay, and what that revenue is worth.
Database read-cost
What your app actually costs to serve, attributable to the customer or feature that drove it — the layer most stacks never measure at all.
Acquisition & analytics
Where people came from, per-host traffic and top pages, and user growth over time — rendered as a chart when a chart is the clearer answer.
Across every project
Switch project mid-conversation, or ask a portfolio-wide question and get one answer spanning all of them.
Numbers an AI cannot misread
Handing a language model a bare number is how confident, wrong answers get made. A
field called actors becomes "users" in the retelling; a missing value
becomes "zero"; a partial measure gets reported as the whole. Prism is built so those
failures cannot happen quietly.
Every number describes itself
Each value arrives with a sidecar stating what it means, what it explicitly is not, its authority (which ledger it came from) and its unit. A count of actors carries "not a user or customer count" in the payload itself, so an assistant cannot round it into something it isn't.
Missing is never zero
Every figure carries a coverage state. measured is a real value.
unavailable means a read failed and should be retried. And
not_instrumented means the surface simply isn't wired yet — so Prism
says "that isn't wired up" rather than reporting a confident, false
0. A blind spot and an empty result are different answers, and they
are kept different all the way to the sentence you read.
Crossdeck surfaces facts. It never invents the reasons behind them — the interpretation is yours.
What people use it for
- Triage a bug by what it is costing you
- Two errors, one afternoon, and time for one. Ask which paying customers each one hit and what they are worth, and the priority stops being a guess about severity and becomes a number. The loud error affecting nobody who pays can wait.
- Find out what a churn actually cost
- A customer cancelled. Ask Prism for their full picture and you get the journey that led there — what they paid, what broke for them, and when. Enough to answer whether it was price, or a bug you shipped.
- Explain an infrastructure bill
- Reads spiked and the invoice followed. A profiler tells you which query; Prism tells you which customer or feature drove it — so the fix is targeted rather than a week-long hunt, and you can see whether that account is worth what it costs to serve.
- Answer the investor question without a spreadsheet
- Recurring revenue across every rail and every project, in one figure, in the chat you already have open — instead of exporting three dashboards and reconciling them by hand.
- Give an AI agent real context
- Because Prism is MCP-native and read-only, an agent can consult your live business data safely as part of a longer task — with no key to leak and no way to change anything.
What it cannot do
- Read-only, with no write path. Prism cannot create, modify, delete, refund or charge anything. The capability does not exist to be misused.
- OAuth, not a pasted key. You sign in; no long-lived secret goes into a chat window, and access is revocable from your dashboard.
- Scoped to your workspace. A connection answers about your own projects and nothing else.
- Aggregate by default. Row-level customer identity is returned only where the connection has been explicitly granted that scope.
The full security model, key scopes and endpoint reference are in the developer documentation.
Prism where you already work
The same joined portfolio also renders as a card inside the tools your team already has open, so nobody has to learn a second console: Prism for Stripe puts the customer behind a payment next to the payment, Prism for Pipedrive puts them next to the deal, and Prism for Resend puts the person behind an email next to the open and the click.
Questions
- How do I use Crossdeck with ChatGPT?
- Connect Prism as an MCP server, or install Prism by Crossdeck from the app directory. Sign in with OAuth — there is no key to paste — then ask in plain language.
- Does it work with Claude and Cursor too?
- Yes. Prism is an MCP server, so it works in any MCP client with the same tools and the same permissions.
- Can Prism change anything in my account?
- No. It is read-only and has no write path. Asked to change something, it can only report that it cannot.
- What can it answer that my analytics tool can't?
- Anything that needs two layers joined by identity — which paying customers an error hit, who drove your read-cost, what a churn was worth. Single-layer tools stop at their own edge.
- How does it avoid making numbers up?
- Every value carries its meaning, its explicit "is not", its authority and its unit — plus a coverage state, so an un-instrumented surface reads as not wired rather than as zero.
- Does Prism cost extra?
- No. It is included with Crossdeck, which is free until $1,500 monthly app revenue.
Ask your app a question tonight
Install the SDK, connect your assistant, and see what the joined answer looks like.