Web performance observability
Autostrada
A web performance platform with a React dashboard, a NestJS service, and AWS infrastructure defined as code.
I designed and built this project independently, using my own resources.
Explore the project
Public repositories
Infrastructuregaulatti/autostrada- Dashboardgaulatti/autostrada-frontend
- APIgaulatti/autostrada-service
The source spans infrastructure, dashboard, and API repositories. No working public demo is linked.
Technologies
01 / Context
The problem behind the project
A one-off performance report is hard to act on without a history of scans, a clear target model, and a dashboard for comparing results.
Autostrada groups three repositories into one web-performance product: the dashboard, the application service, and infrastructure. The operating question is how a site changes over time, rather than what a single Lighthouse run scored.
The project connects measurements with target, scan, project, and access-management models so performance observations can become navigable history.
02 / Implementation
Design and implementation
I built the dashboard, service, and infrastructure components for collecting and exploring website-performance results.
I built the React/TypeScript dashboard, NestJS backend, and CDK infrastructure definitions. The dashboard uses authenticated routes, data tables, sorting/pagination, Redux/Saga side effects, and feature controls.
The service coordinates scan-related work and stores results, while the frontend exposes reports and target management. Cognito handles user identity, and service boundaries support REST/gRPC integrations around collection and analysis.
03 / Architecture
Architecture and workflow
Define targets and access
Authenticated users manage the sites and project context that scans belong to.
Coordinate measurement
The backend organizes scan work and consumes Lighthouse/PageSpeed-related results.
Store and inspect history
Reports and tables make stored results available for comparison and operational follow-up.
Provision deliberately
Infrastructure definitions describe the AWS environment separately from the application repositories.
04 / Approach
Engineering decisions
Separate collection from presentation
The NestJS service manages targets, scans, and results; the React dashboard presents the performance history.
Infrastructure belongs in source
The infrastructure repository describes compute, storage, authentication, and networking using AWS CDK.
05 / Evidence
Evidence and outcomes
The public repositories expose the three-part architecture, scan/service models, dashboard routes, and infrastructure tests. They show implementation scope without establishing a public service’s current uptime or usage.
This is distinct from the employer-owned performance work in my résumé. The portfolio page documents the independent Autostrada codebase and does not reuse an employer impact metric as a product result.
Source and technical notes
06 / Current scope
Where it stands
Retained for recovery. Automatic deployment is disabled pending verification.
Collection, storage, and a reporting interface do not automatically establish that two lab runs are comparable. Performance interpretation still depends on consistent targets and measurement conditions.
No public adoption, benchmark improvement, or ongoing production service is claimed for this independent project.