Actors Management Portal

The same scraper logic often lives in several Apify accounts, and keeping those copies in step by hand is slow and error-prone: shared helper files drift, dependency versions diverge, and a fix landed in one account is forgotten in another. Account tokens expire silently and break automations, and there is no single view of whether every actor is healthy. Managing many accounts needs one place to see status, one way to push a change everywhere, and a safe store for credentials.

The backend is FastAPI with async SQLAlchemy on PostgreSQL. Account credentials are encrypted at rest with Fernet and never leave the server; the frontend only sees account labels and health. A health check validates tokens on load and surfaces expired ones with a guided re-authentication flow.

Templates group actors across accounts. A template declares shared file patterns; a sync picks a source actor and pushes matching files to every linked actor, optionally regenerating a per-account README. Auto-detect proposes template mappings by matching actor names across accounts. Build-all triggers builds for the whole group, and bulk maintenance toggles run as Celery tasks with rate limits and retries.

An in-browser editor fetches an actor's source, marks unsaved changes, shows a diff, and saves straight back to Apify. Analytics pulls per-account actor statistics with a cache whose TTL depends on whether the month is still open. Pricing templates define pay-per-event tiers that can be attached to actors.

The actor-building agent runs probe, generate, validate, local test with a bounded fix loop, code review, and UX review, then pauses at an approval gate before publishing and running a remote test. Every step appends to a job log that the UI polls. The LLM layer is switchable across four providers, and image generation produces README covers.