r/e REVERSEENGINEER LAB
AN OPEN INDEX OF HOW THINGS WORK

Software reverse engineering
research.
Evidence included.

Explore the architecture, APIs, and decisions behind real systems. Read what was observed, what was inferred, and what remains unknown.

Explore the catalog ↓
THE RESEARCH INDEX

Explore reverse engineering examples

09 published
Web application01 ↗
Notion

Notion: databases, data sources and pages

The practical consequences of Notion’s database/data-source split for schema discovery, page creation and integration identity.

Web application02 ↗
WooCommerce

WooCommerce: Store API versus order storage

Why a customer-facing API, merchant order access and HPOS are different layers—and why table existence alone cannot identify authoritative orders.

Web application03 ↗
Klaviyo

Klaviyo: API revisions and rate-limit windows

How explicit API revisions and separate burst/steady limits affect a Klaviyo client’s retry, scheduling and compatibility decisions.

Web application04 ↗
Shopify

Shopify GraphQL: query cost and cursor pagination

A worked client model for Shopify’s query-cost budget and cursor pagination, showing why page position and request capacity are separate concerns.

Web application05 ↗
Shiptheory

Shiptheory: shipment data and service selection

Separate the shipment you describe, the service selected by rules, and the carrier result before treating a label request as fulfillment.

Web application06 ↗
Katana

Katana: on-hand, committed and expected stock

Why Katana’s inventory contract needs several quantities, with a worked planning example and explicit limits on what those numbers prove.

Web application07 ↗
DOSS

DOSS: workflows over shared operational data

What DOSS’s public workflow and master-data surfaces reveal about triggers, shared records and the boundary between automation and business state.

Web application08 ↗
Campfire

Campfire: bank feeds and journal entries

A contract-level look at bank-feed ingestion, journal construction and the distinction between a recorded bank event and a posted accounting result.

Web application09 ↗
Digits

Digits: source transactions versus the ledger

How Digits separates imported records from accounting results, and why source identity, replay and ledger visibility are different concerns.

LEAVE A TRAIL FOR THE NEXT PERSON

Investigated something interesting?

Share the question, the findings, and the evidence. Every submission is reviewed before it joins the catalog.

Contribute a distillation ↗