Products / Crossdeck

Crossdeck

Active Application intelligence Web application and SDKs

The application-intelligence layer that joins customer identity, revenue, analytics, errors and operational cost on one timeline.

Relationship: Crossdeck is an independent product created and operated by Cross Constellation.
Canonical site: cross-deck.com
Status: Active public product
Product colour: #FF6E45

01 / 8

The one-sentence definition, without comparison or superlative.

What it is

Crossdeck is the application-intelligence layer that joins customer identity, revenue, analytics, errors and operational cost on one timeline. One SDK reports what happened inside an application; Crossdeck resolves it to the customer it affected, so a purchase, a crash and a session belong to the same person rather than to three disconnected dashboards.

02 / 8

The operating frustration that existed before the product.

The problem we encountered

Operating iOS applications meant waiting days for App Store Connect to report what had already happened inside our own software. As the number of products grew, the delay stopped being the main problem. Revenue lived in one system, analytics in another, errors somewhere else, and customer identity nowhere coherent. Answering a question as ordinary as "who was affected, and did they pay us?" meant reconciling four exports by hand.

03 / 8

The founder’s account, in their own words.

Why we built it

“We built Crossdeck because we were tired of waiting days for App Store Connect to reveal what had happened inside our own iOS applications. As the number of products grew, the larger problem became obvious: revenue lived in one system, analytics in another, errors somewhere else and customer identity nowhere coherent. We wanted one place where every operational fact could be joined to the customer it affected.”

Wes Thomson, Founder

04 / 8

How the first problem expanded into the current product.

What the product became

One SDK, rather than one integration per signal.
Identity that carries across a customer’s activity in a product.
Revenue and entitlement truth, verified rather than assumed.
Behavioural analytics reported against that same identity.
Runtime errors, with the users each failure actually reached.
Database read-cost, so operational spend sits beside the behaviour causing it.
Trust, for signup and login protection.
Prism, for asking questions of verified application context.

05 / 8

Genuine dogfooding. Deployed uses only.

How we use it ourselves

Crossdeck Trust protects login and signup flows across the portfolio and helps verify browser-origin and human signals. Deployed
Crossdeck Analytics records product behaviour. Deployed
Crossdeck Errors shows failures and the users affected. Deployed
Crossdeck Revenue and Entitlements verify purchases and gate paid access where implemented. Deployed
Crossdeck identity joins anonymous and known activity. Deployed
Crossdeck Pulse shows activity across the portfolio in one live operating surface. Deployed

06 / 8

The relationship graph, rendered from the register.

How it connects to the portfolio

Crossdeck uses

Crossdeck uses Biotree — Crossdeck uses a Biotree page as its public social and resource hub at crossdeck.biotree.bio. · Evidence
Crossdeck uses Digital Hank — Crossdeck uses Digital Hank as the business-aware AI assistant it runs its business on.

Products that use Crossdeck

Biotree uses Crossdeck — Biotree uses Crossdeck for product analytics, identity, errors, Trust and applicable entitlement visibility.
Grid uses Crossdeck — Grid uses Crossdeck as a real iOS production application for identity, analytics, errors and applicable revenue or entitlement verification.
Digital Hank uses Crossdeck — Digital Hank uses Crossdeck for analytics and entitlement gating, on iOS and on the web.
PricePage uses Crossdeck — PricePage uses Crossdeck for analytics, errors and revenue tracking.
ClaudeArchitect uses Crossdeck — ClaudeArchitect uses Crossdeck for analytics, errors and revenue tracking.
PageSwipe uses Crossdeck — PageSwipe uses the Crossdeck iOS SDK and Web SDK for analytics and errors.

07 / 8

Attributable support for everything claimed above.

Evidence

Crossdeck production website Public page
Crossdeck public resource hub on Biotree Public page
Who builds Crossdeck Public page

Open source

crossdeck-swift Native Swift client for iOS, iPadOS, macOS, tvOS and watchOS.
crossdeck-android Android SDK — analytics, errors and entitlements.
crossdeck-react-native React Native client across iOS and Android, one JS codebase.
crossdeck-web SDK for browsers and Node.js.
crossdeck-node Server-side telemetry, entitlements and error capture.
crossdeck-cli Uploads source maps so production stack traces resolve to file, line and function.
crossdeck-prism Prism, the MCP intelligence layer — ask your app a question in plain English.
buckets-oss Read-cost meter for Firestore, MongoDB and Postgres. The subject of its own story.

08 / 8

Where to go for the product itself.

Official destinations

cross-deck.com remains the commercial destination. This page is the origin and relationship source.

Stories

Where Crossdeck comes up.

Why we built Crossdeck — and why every product we build helps test it
We thought the App Store Connect wait was the problem. The real problem was fragmentation — the same person scattered across a dozen disconnected tools. So we put one SDK and one customer timeline underneath everything we operate.
Every product is a test environment for the one beneath it
A habit tracker on the App Store, a link-in-bio product carrying anonymous global traffic, and a book catalogue on two platforms. None of them was built to test anything. That is exactly why they work as tests.
The Firebase bill that taught us to see
A runaway Firestore read bill sent us chasing ClickHouse. The real fix was not a new database — it was being able to see where every read came from. What we learned, and why we open-sourced Buckets.
The email address you’re keying on is not the person
Why email is a fragile anchor for user identity, how keying on the wrong id forks one person into many records, and how an identity graph converges every key onto one canonical customer.
We got our connector rejected. It was the best product spec we received all year.
A marketplace review rejected our connector with roughly a dozen findings. Instead of a failure, it read like a spec — the exact definition of a production-grade third-party integration we would never have written ourselves.
The black box blinks: seeing App Review happen in your own data
App Review is a black box. Identity-joined session data reveals when a reviewer starts testing your build, where they connect from, and the exact path they walk — plus the line we will not cross.
Why Biotree needed Crossdeck Trust — and how we stopped the SEO spam farms
Public, indexed link-in-bio pages are a magnet for spam farms and bot signups. The attack Biotree faced, why the obvious defences backfire, and the signup firewall that stopped it without punishing real users.
Why we are building Crossdeck Sales
Cold outbound is miserable because the seller is blind. We were not — we already saw who landed, what they read, and why. So we are building the tool that turns that journey into outreach that lands.

All products · Stories · How we build