webscraping-dashboard repository. It gives users a single interface for working with task definitions, executions, templates, datasets, analytics, and billing-related views.
What the dashboard is for
The dashboard exists so users can work with the platform without building their own frontend first. It provides a high-level operating surface for:- Creating and managing tasks
- Browsing templates
- Launching or monitoring executions
- Reviewing datasets and exported outputs
- Inspecting usage and billing views
How the dashboard fits into the platform
The dashboard is not the source of truth for the scraping system. It is the user-facing client of the platform APIs. At a high level, it talks to:- Auth for sessions and identity
- Task Service for tasks, executions, templates, results, and datasets
- Analytics Service for usage reporting
- Billing Service for wallet and credit views
Why this separation matters
The separation between dashboard and backend services keeps the platform flexible:- Users can work through the dashboard
- Teams can build their own frontend against the same APIs
- Backend services remain the source of truth