Tenant isolation
Protected operations resolve the authenticated user and verify membership for the resource workspace instead of trusting a submitted workspace ID.
Security architecture
SEO automation needs explicit data and execution boundaries
The product treats every website, report, job, provider connection, and future agent action as a workspace-scoped resource.
Credential protection
Provider refresh tokens are encrypted on the server and are never returned to the browser or written to normal logs.
Crawler egress protection
Requests, redirects, DNS results, private networks, link-local ranges, and cloud metadata targets pass strict SSRF checks.
Durable job control
Expensive crawls, browser runs, syncs, and reports run outside request threads with atomic claims, leases, retries, cancellation, and recovery.
Canonical persistence
Production targets standard PostgreSQL. The embedded PGlite adapter is reserved for local development workflows.
Abuse and cost limits
Rate limits, crawl caps, active-job limits, usage meters, and entitlements are enforced at the API boundary rather than only hidden in the UI.
Current deployment boundary
The application and its PostgreSQL database run on the operator's computer, with HTTPS access through Cloudflare Tunnel. Encrypted database and recovery archives are created daily for off-machine synchronization. Availability depends on this computer, power and network access. A complete recovery on another machine has not been verified. New registrations and payments are disabled; no availability SLA is offered.