Sending a DMCA is easy. Getting the takedown is not.

The proprietary infrastructure behind every CRD removal. For each platform: who to contact, what to send, when to follow up, when to escalate, how to verify.

See what’s new

The original sketch.

Drawn by the founder in CRD’s earliest days.

  • Instagram
  • TikTok
  • Reddit
  • Telegram
  • X · Twitter
  • Forums
  • Mirrors
Explore how CRD Engine works
social + leak sitesmatch + evidencenotice + follow-upsRemoval verified
From source to removal. The engine continuously searches social platforms, leak sites, forums, and mirrors for copies.
681Documented platformsCRD Index4Search enginesCRD IntelOpens in a new tab
150K+DMCA notices sent
86.2%
<2hAverage first action
0Manual steps required
Pipeline

Six steps. Zero manual work.

Every step runs autonomously, 24/7, from the first scan to the confirmed removal and the search de-indexing that follows it.

Detection

Find what’s out there.

AI scanners run continuously across leak sites, forums, mirrors and file hosts. Leaks identified and queued within seconds.

Images, profiles and links are matched before the result enters the queue.

The outcome

An identified result, ready for processing.

Infrastructure

Built on what works.

A proven public stack behind every customer-facing capability.

Frontend

  • Next.js 16Public web
  • React 19Interface layer
  • TypeScriptTyped application
  • Tailwind CSSVisual system
  • Framer MotionInterface motion

Backend & Data

  • SupabaseManaged backend
  • PostgreSQLPrimary database
  • Edge FunctionsServerless compute
  • Row Level SecurityData isolation
  • DenoRuntime

Integrations

  • ResendEmail delivery
  • StripeBilling
  • VercelWeb delivery
  • AppleiOS app
  • CloudflareNetwork & DNS

Search ecosystem

Coverage across major search engines.

Coverage

  • GoogleSearch + Images
  • BingSearch coverage
  • YahooSearch coverage
  • YandexWeb search

What this supports

  • AI detection
  • Cross-platform coverage
  • DMCA notices
  • Continuous monitoring
  • Follow-up management
  • Verified removals
  • Duplicate protection
  • Delivery monitoring

Need the public architecture brief? Contact support

APILive

CRD Engine API

Connect your software to CRD: creators, scans, reports and removals, all in one agency workspace.

One connected workflow

Your software. Our engine.

  1. Connect your agency

    Create a scoped key in your agency dashboard.

  2. Use the existing workflow

    Your creators and leak cases stay synchronized with the CRD portal.

  3. Follow every stage

    Read case status or receive signed events in your software.

API documentationOpens in a new tab

Access is rolling out to verified agencies. Manage keys, webhooks and usage in your dashboard.

Access through your agencyOpens in a new tab
Build log

How the engine got here.

Every release that changed how leaks get found, filed and removed. Nothing here was replaced. All of it still runs inside v4.8.

v4.8 v1.0
v4.82026CURRENT RELEASE

Your software, connected to the protection workflow

v4.8 expands the agency API with creator management, direct reporting of leaks and impersonation accounts, on-demand scans and case tracking. Operations use the same records and workflows as the CRD portal.

What changed7 changes
  1. More reliable email invitations: fixed a delivery failure found in an end-to-end test. An invitation sent through the API can also be cancelled before it is accepted.
  2. Report a leak or impersonation account directly from your software. Leaks enter the usual reporting and removal workflow, and reporting the same URL again does not create a duplicate case.
  3. Profile photos by URL: the image is imported into CRD and appears in the portal, in the same place as a photo added during onboarding.
  4. Per-creator domain whitelist: add, read or remove an allowed domain in the same list the CRD team already manages.
  5. Additional on-demand scans include Yandex, capped at five per creator in a rolling seven-day window. Automatic monitoring follows the creator’s CRD plan without running a second schedule alongside it.
  6. Leak case tracking stays synchronized with CRD, with signed webhooks for observed changes. Delivery attempts and replays are available in the agency dashboard.
  7. Paid legal escalation for leak cases: share a payment link with the agency or creator and track its status. In private rollout, available on request.
FAQ

Frequently asked questions.

The infrastructure behind CRD.

Built for CRD's own removal operations. Agencies run their whole roster on the same engine through our partnership program and agency app.

Agency access