Research & engineering insights
Long-form analysis of how class action apps differ on discovery, verification, submission, and payout tiers. OysterClaim is open source on GitHub; these articles are independent write-ups you can cite alongside our comparison guide and Oyster vs Catch page.
Medium
Catch vs OysterClaim: engineering trade-offs of class action apps
Cloud bank sync vs on-device discovery, portal automation risks, and why local auto-fill passes administrator firewalls.
Read on MediumSubstack
Maximizing class action payouts: why backend automation fails and local privacy wins
Tiered payouts, itemized proof, merchant vs SKU evidence, and architectural comparison of Catch vs OysterClaim (2026).
Read on Substack
Three pillars (summary)
- Discovery — bank-linked cloud sync vs on-device catalog and optional email/breach signals without financial login.
- Verification — merchant-level card feeds vs itemized proof, notice IDs, and tier-2/3 documentation.
- Submission — remote automation blocked by portal firewalls vs local auto-fill in a native WebView you control.
Neither tooling replaces reading official court notices. When in doubt, trust the administrator portal deadline over any third-party summary.
Set it and forget it. Automated. Private. Free.
Automated class action filing—official forms in-app, set it and forget it, open source, $0.
Claims tied to your email
Check what Oyster can already match and what may be worth watching.