tmobile/jazz
This system is a comprehensive serverless platform that manages the full lifecycle of cloud services across AWS and Azure. It provides a centralized API for creating, updating, and deleting serverless functions, APIs, and web applications, while handling associated resources like databases, queues, and CDNs. The platform enforces strict access control and security policies, manages user authentication and permissions, and offers monitoring, logging, and cost tracking capabilities. Additionally, it automates CI/CD pipelines and provides templates for rapid service onboarding.
56.8
Adequate · 3 August 2026
105k
lines of production code
JavaScript
with TypeScript
8
bus factor · 100 authors in all
3
measurements over time
How it got here
2018 · Platform API and UI expansion
This period focused on expanding the Jazz platform's core capabilities by introducing numerous new backend services for managing assets, environments, and user permissions, alongside a comprehensive Angular-based frontend. The work established a standardized architecture for serverless service creation, deployment, and monitoring, while simultaneously building out the user interface with new pages for service management, logging, and administration.
119 changes
2019 · Serverless and cloud infrastructure expansion
This period focused on expanding the platform's support for serverless architectures and cloud-native services. New templates and build pipelines were introduced for Node.js, Python, Go, Java, and C# across AWS Lambda, Azure Functions, and Angular/React web applications. Additionally, the codebase integrated Bitbucket and GitLab SCM integrations, automated AWS resource teardown, and implemented a secrets management API.
28 changes
Survey your own repository
tmobile/jazz was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit a419c34ce3 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.