Accounts & entitlements
D1 users, workspaces, plan limits, cloud roster and usage tracking.
See exactly what RankLens still needs.
This page separates completed code from one-time external connections. Secrets are never shown here; it only reports whether a connection exists and whether RankLens has recorded a successful run.
— live— required launch items leftInfrastructure cost today: ₹0
Team seats
Workspace roles, invite-code UI and seat enforcement.
RUM enforcement
Sampling, project isolation and monthly plan caps are enforced server-side.
Monitoring worker
Uptime cron, D1 history, scheduled checks and RUM collector.
Native browser checks
RankLens can run browser-based performance checks without requiring a paid third-party service.
Google PageSpeed API
Optional additional Lighthouse/PageSpeed coverage.
Google CrUX API
Optional field Core Web Vitals from the Chrome UX Report API.
Email alerts
Optional verified-sender connection for downtime email alerts. Customer support already has an in-app owner inbox.
Looker Studio
Connector backend + downloadable Apps Script source are complete.
One free Google deployment click remains.
Bot & abuse protection
Cloudflare Turnstile, server-side token verification and rate limits protect public actions.
Razorpay subscriptions
Recurring checkout, signed payment verification, webhook verification and cancellation-at-cycle-end are connected.
Public merchant identity
For customer transparency, publish the final legal/proprietor name and customer-facing business contact details used for the merchant account.
Waiting for final merchant identity/contact confirmation.
What still needs your involvement
1
Confirm merchant identity + support details
Publish the same legal/proprietor identity and customer-facing contact information you intend to use for the Razorpay merchant account. RankLens will not invent these details.
2
Verify one controlled Live payment
Razorpay Live credentials are connected. Complete one real subscription payment and verify payment capture, webhook delivery, account upgrade and cancellation behavior before promoting checkout broadly.
Live payment verification3
Optional: Google PSI + CrUX keys
These improve Lighthouse/PageSpeed and field Core Web Vitals coverage. They are not required for secure billing.
PS_KEY · CRUX_KEY4
Optional: email alerts + Looker Studio
Connect a verified email sender for monitoring/support alerts, and deploy the Looker Studio connector if you want reporting integration.
Download connectorWhy there is no third billing Worker: RankLens already enforces plan limits in the account D1 + monitor D1 path. A second enforcement hop would duplicate state, add latency and create another service that could fail. We keep one source of truth instead.