CrawlClick

Security posture

Trust boundaries before trust claims.

CrawlClick is designed so that a compromised header, retry, tenant or dependency cannot quietly become a billable insertion, duplicate payment or publisher outage.

Crawler identity

Verify, then classify.

User-agent matches are only a hint. Vendor ranges, forward-confirmed reverse DNS and request signatures supply the actual evidence.

Publisher origin

Public HTTPS only.

Origins must be distinct verified subdomains. DNS is resolved once and private, loopback, metadata and special-use addresses are rejected before connecting.

Edge trust

Separate tenant from attestation.

A one-time site token selects the verified tenant but cannot authorize billable traffic alone. The independent platform credential stays only in the CrawlClick-controlled Worker and proxy, so a revenue recipient cannot forge network identity.

Tenant boundary

Organisation-scoped reads.

Commercial API sessions resolve to one organisation and role. Site, campaign, funding and analytics operations enforce that boundary.

Stripe boundary

Canonical and idempotent.

Signed raw webhooks retrieve canonical Stripe objects, bind them to stored attempts, and use durable idempotency keys for refunds and payouts.

Availability

Fail open to the real page.

The managed edge preserves the publisher response when CrawlClick times out or refuses to serve. Monetization cannot become the site availability dependency.

Where does high-volume evidence live?

Crawls, referrals and insertion events live in object storage. Serving snapshots are immutable and stateless compute reads them without contacting Postgres.

Where does relational state live?

Postgres holds identities, memberships, verified sites, Stripe state, the operation outbox and one balanced transaction per settlement window. The ledger grows with money movements, not impressions.

Invite-only pilot

Review the architecture against your pilot.

Selected participants receive the concrete integration checklist and can raise origin, data-flow or payments questions before enabling traffic.