Skip to content
All projects

Full-Stack Development · SaaS · API Integrations

DMCA Protection & Brand Monitoring Platform

A subscription-based platform for digital content protection and brand monitoring, covering property management, multi-step scan workflows, customer onboarding, billing, and automated alerts.

PHPPDOMySQLStripeWebhooksJavaScriptHTML/CSSTransactional email

This is a private project. The case study is sanitized and illustrative: client names, URLs, data, credentials, and infrastructure details are intentionally omitted.

01Overview

The platform helps customers protect digital content and monitor their brand. Customers register the properties they want to protect, run scans against them, review the results, and receive alerts, all under a paid subscription.

My work sat where the backend services meet the interface: turning scan workflows, billing events, and onboarding rules into application logic, database records, and screens that stay consistent with each other.

02Key Challenges

Long-running scans
A scan does not finish within a single request. The workflow runs in stages (start, poll for progress, collect results) so the interface stays responsive and properties can be rescanned later.
Billing and access in agreement
Subscription changes happen in Stripe, not in the application. Lifecycle events arriving by webhook have to be translated into subscription state that the rest of the platform can rely on.
Rules that hold regardless of the client
Plan limits, property ownership, and verification requirements have to be enforced on the server, whatever the frontend sends.

03My Contributions

  • PHP and PDO-based backend development
  • MySQL database integration
  • Multi-step scanning and polling workflows
  • Property management and rescan functionality
  • Subscription billing and Stripe integration
  • Webhook processing for subscription lifecycle events
  • Customer onboarding and verification workflows
  • Email notifications and automated alerts
  • Backend validation and business rule enforcement

04Architecture

A simplified view of how a customer moves through the platform and where the backend services connect.

  1. 1

    Onboarding & verification

    Account creation and verification steps before protected features become available.

  2. 2

    Property management

    Customers register and manage the properties they want monitored, stored as related records in MySQL.

  3. 3

    Scan orchestration

    Scans are started, polled for progress, and completed in stages, with rescans available per property.

  4. 4

    Results & alerts

    Results are stored against the property and email notifications keep customers informed.

  5. 5

    Billing

    Stripe subscriptions and lifecycle webhooks keep subscription state current, which in turn determines what a customer can use.

05Engineering Decisions

Prepared statements for every query
Database access goes through PDO prepared statements, keeping user input out of SQL and giving the data layer one consistent pattern.
Webhooks as the source of billing truth
Subscription state follows Stripe lifecycle events instead of assuming a checkout succeeded, so upgrades, renewals, failures, and cancellations are reflected in the application.
Polling over blocking requests
Splitting scans into start and poll steps avoids long-held HTTP requests and gives the interface a clear progress state.
Validation at the boundary
Input and business rules are checked on the server before anything is written, so the database only receives valid state.