Third-Party Services & Licences
Last updated: When we remember to update it (which is not as often as it should be)
THIS PAGE (THE “LICENCES PAGE”) PROVIDES AN OVERVIEW OF THE THIRD-PARTY SERVICES, PLATFORMS, APIS, LIBRARIES, FRAMEWORKS, PACKAGES, TOOLS, AND OTHER EXTERNAL RESOURCES THAT THE SERVICE INTEGRATES WITH, DEPENDS UPON, REFERENCES, OR OTHERWISE USES IN ITS OPERATION. THE OPERATORS ARE GRATEFUL TO THE DEVELOPERS, MAINTAINERS, CONTRIBUTORS, AND COMMUNITIES BEHIND THESE PROJECTS AND ACKNOWLEDGE THAT THE SERVICE WOULD NOT BE POSSIBLE WITHOUT THEIR WORK. THIS LIST MAY NOT BE EXHAUSTIVE, AND THE OPERATORS ENCOURAGE USERS TO REFER TO THE RESPECTIVE PROJECT DOCUMENTATION FOR COMPLETE AND ACCURATE LICENSING INFORMATION.
SECTION 1. EXTERNAL SERVICES AND PLATFORMS AND THE THIRD-PARTY SERVICES THAT THE SERVICE INTEGRATES WITH, DEPENDS UPON, OR OTHERWISE INTERACTS WITH IN THE COURSE OF ITS OPERATION
1.1 Discord
Discord
Communication platform for community interaction, support, music requests, and server administration. Discord provides the chat, voice, and community infrastructure that enables Users to interact with each other, submit song requests, vote on songs, receive notifications, and communicate with the Operators. The Service integrates with Discord through a custom Discord bot that listens for commands in designated channels, processes music requests, displays now-playing information, and provides administrative functionality. Discord is a proprietary service owned and operated by Discord Inc.
1.2 Groq
Groq (Groq Inc.)
AI inference platform providing ultra-fast access to the Llama 3.1 8B language model for song suggestion generation and content moderation. Groq's LPU (Language Processing Unit) hardware enables rapid AI inference that powers the AutoDJ system's intelligent music selection. The Service sends song context and moderation prompts to Groq's API, which processes them and returns suggestions and family-friendly assessments. No personal user data is transmitted to Groq. Groq is a proprietary service owned and operated by Groq Inc.
1.3 Last.fm
Last.fm
Music metadata, artist information, album art, track identification, and recommendation API for AutoDJ integration. Last.fm provides the comprehensive music database, listening statistics platform, and recommendation engine that powers the AutoDJ system's music selection algorithm. Through Last.fm's API, the Service can access detailed metadata about millions of tracks, including artist names, album titles, track lengths, genre classifications, popularity metrics, and related artist recommendations. This data enables the AutoDJ system to make informed decisions about which music to play, to group similar tracks together, and to provide contextually relevant recommendations to Users. Last.fm is a service owned and operated by Last.fm Ltd., and its API wrapper is licensed under the MIT License.
1.4 YouTube
YouTube (Google LLC / Alphabet Inc.)
Video streaming platform used for music video integration, audio source retrieval, content discovery, metadata enrichment, and alternative streaming sources. YouTube serves as a primary source of audio content for the Service, with the YouTube Embedded Player used to stream music videos and audio tracks. The Service accesses YouTube's vast catalog of music content, including official music videos, user-uploaded content, live performances, and audio-only uploads. YouTube provides the infrastructure for hosting, transcoding, and delivering audio-visual content to Users across the globe. YouTube is a proprietary service owned and operated by Google LLC, a subsidiary of Alphabet Inc.
1.5 Supabase
Supabase (Supabase Inc.)
Open-source backend-as-a-service platform providing file storage and hosting. Supabase Storage is used as the Service's file storage backend, hosting uploaded assets such as images, logos, and other files. Files are stored in the erlc-fm public bucket and served with global CDN distribution. Supabase is available under the Apache 2.0 License for the open-source self-hosted version, with the managed cloud service being proprietary.
1.6 Render
Render (Render Services Inc.)
Cloud hosting platform for backend services, API servers, databases, background workers, cron jobs, and web services. Render provides the hosting infrastructure for the Service's backend components, including the Discord bot, API servers, database connections, and background processing tasks. Render offers managed PostgreSQL databases, Redis instances, and other infrastructure services that support the Service's data storage and processing needs. Render is a proprietary service owned and operated by Render Services Inc.
1.7 MongoDB
MongoDB (MongoDB Inc.)
NoSQL database platform for data storage, document management, query processing, aggregation, and real-time analytics. MongoDB is used as the primary database for the Service, storing user data, music metadata, request logs, listening statistics, configuration settings, and other persistent data. MongoDB Atlas (the cloud-hosted MongoDB service) provides managed database infrastructure with automatic scaling, backups, monitoring, and security features. MongoDB is available under the Server Side Public License (SSPL) for the community edition, with MongoDB Atlas being a proprietary service.
1.8 GitHub
GitHub (GitHub Inc. / Microsoft Corporation)
Source code management, version control, issue tracking, project management, continuous integration and deployment (CI/CD), code review, and collaboration platform. GitHub hosts the Service's source code repository, manages version history, tracks issues and feature requests, facilitates code reviews, and powers the CI/CD pipeline that automatically builds, tests, and deploys changes to the Service. GitHub Actions provides the workflow automation that enables automated testing, linting, building, and deployment of the Service. GitHub is a proprietary service owned and operated by GitHub Inc., a subsidiary of Microsoft Corporation.
1.9 LrcLib
LrcLib (LrcLib.net)
Open lyrics API providing synchronized (LRC) and plain-text song lyrics. LrcLib is used by the Service's full-screen player to fetch and display lyrics for the currently playing song in real time, with line-by-line highlighting synchronized to the music. The Service sends the current song title and artist name to LrcLib's API to retrieve matching lyrics. No personal information is transmitted to LrcLib. LrcLib is an open-source project.
1.10 Node.js
Node.js (OpenJS Foundation)
JavaScript runtime environment that executes server-side code, powers the backend infrastructure, runs the Discord bot, handles API requests, manages database connections, and processes background tasks. Node.js is the foundation upon which the Service's backend is built, providing the asynchronous, event-driven runtime that enables efficient handling of concurrent connections, real-time streaming, and I/O-intensive operations. Node.js is available under the MIT License.
SECTION 2. OPEN-SOURCE SOFTWARE PACKAGES AND THE SPECIFIC NPM PACKAGES, LIBRARIES, FRAMEWORKS, AND DEPENDENCIES THAT THE SERVICE USES, ORGANIZED BY CATEGORY AND INCLUDING VERSION INFORMATION AND LICENSING DETAILS
2.1 Runtime and Framework Dependencies
next (v15.x) — MIT
The React framework for production-grade web applications, providing server-side rendering, static site generation, API route handling, file-based routing, image optimization, font optimization, middleware, edge functions, incremental static regeneration, and a comprehensive plugin ecosystem. Next.js is the core framework upon which the Service's web interface is built, handling routing, rendering, data fetching, and deployment optimization. Developed and maintained by Vercel Inc. and the open-source community.
react (v19.x) — MIT
The library for building user interfaces with a declarative, component-based architecture, virtual DOM implementation, hooks system, context API, suspense, concurrent rendering, and a vast ecosystem of third-party components and tools. React provides the core UI rendering engine for the Service, enabling the creation of reusable, composable, and maintainable user interface components. Developed and maintained by Meta (Facebook) and the open-source community.
react-dom (v19.x) — MIT
The React package for DOM-specific rendering methods, including client-side rendering, hydration, event handling, and portal management. react-dom provides the bridge between the React component tree and the browser's Document Object Model (DOM), enabling the rendering of React components to the browser and handling browser-specific interactions and optimizations.
typescript (v5.x) — Apache 2.0
A typed superset of JavaScript that compiles to plain JavaScript, providing static type checking, type inference, generics, interfaces, enums, decorators, and advanced type system features. TypeScript is used throughout the Service to provide type safety, improve code quality, enable better tooling and IDE support, and reduce the incidence of runtime errors. Developed and maintained by Microsoft Corporation.
2.2 Discord Integration Dependencies
discord.js (v14.x) — MIT
A powerful JavaScript library for interacting with the Discord API, providing support for slash commands, context menu commands, message components (buttons, select menus, modals), embeds, attachments, interactions, voice connections, webhooks, and real-time gateway events. discord.js is the core library that powers the Service's Discord bot, enabling it to listen for commands, process music requests, display now-playing information, manage queues, moderate content, and interact with Users in Discord servers. Developed and maintained by the discord.js community.
2.3 Database and Data Management Dependencies
mongoose (v8.x) — MIT
An elegant MongoDB object modeling tool for Node.js, providing schema validation, query building, population, middleware (hooks), virtuals, discriminators, indexing, transactions, and aggregation pipeline support. Mongoose provides a structured, schema-based approach to interacting with MongoDB, enabling the Service to define data models, validate data, build complex queries, and manage relationships between different types of data. Developed and maintained by the Automattic team and the open-source community.
2.4 Styling and UI Dependencies
tailwindcss (v3.x / v4.x) — MIT
A utility-first CSS framework for rapidly building custom user interfaces with a design system approach, responsive breakpoints, dark mode, arbitrary values, custom variants, and a Just-in-Time (JIT) compiler that generates optimized CSS at build time. Tailwind CSS provides the styling foundation for the Service's web interface, enabling rapid development of responsive, consistent, and maintainable user interfaces through the use of composable utility classes. Developed and maintained by Tailwind Labs.
postcss — MIT
A tool for transforming CSS with JavaScript plugins, providing autoprefixing, minification, nesting, custom properties, and advanced CSS processing capabilities. PostCSS is used in the Service's build pipeline to process and optimize CSS, ensuring cross-browser compatibility and optimal performance.
autoprefixer — MIT
A PostCSS plugin that parses CSS and adds vendor prefixes to CSS rules using values from Can I Use, ensuring that the Service's stylesheets work correctly across different browsers and browser versions. Autoprefixer eliminates the need for manually adding vendor prefixes to CSS properties, reducing development time and preventing cross-browser compatibility issues.
2.5 Additional Dependencies and Tools
@types/node — MIT
TypeScript type definitions for Node.js, providing type information for all Node.js core modules, APIs, and globals. These type definitions enable the Service to maintain type safety when interacting with Node.js runtime features.
@types/react — MIT
TypeScript type definitions for React, providing type information for React components, hooks, props, state, context, events, and other React APIs. These type definitions enable the Service to maintain type safety when building React components and using React features.
@types/react-dom — MIT
TypeScript type definitions for react-dom, providing type information for DOM-specific React APIs, rendering methods, event handling, and portal management. These type definitions enable the Service to maintain type safety when using DOM-specific React features.
eslint — MIT
A pluggable linting utility for JavaScript and TypeScript that analyzes code for potential errors, style violations, anti-patterns, and best practice deviations. ESLint is used in the Service's development workflow to enforce code quality standards, maintain consistent coding style, and catch potential issues before they reach production.
eslint-config-next — MIT
The official ESLint configuration for Next.js projects, providing recommended linting rules, React-specific rules, accessibility rules, and Next.js-specific rules that help maintain code quality and catch common issues in Next.js applications.
SECTION 3. ADDITIONAL THIRD-PARTY RESOURCES AND THE BROADER ECOSYSTEM OF OPEN-SOURCE SOFTWARE, TOOLS, AND SERVICES THAT SUPPORT THE OPERATION AND DEVELOPMENT OF THE SERVICE
3.1 Development and Build Tools
In addition to the packages and services listed above, the Service relies on a variety of development and build tools, including but not limited to: npm (the Node.js package manager), Turbopack (the Rust-based bundler used by Next.js), Git (the version control system), and various command-line utilities and shell scripts that automate development, testing, building, and deployment tasks. These tools are essential to the development workflow but are not directly used in the production operation of the Service.
3.2 Operating System and Infrastructure
The Service runs on Linux-based servers and containers, utilizing the Linux kernel, system libraries, GNU core utilities, and various open-source system software. The specific Linux distribution, kernel version, and system configuration may vary depending on the hosting provider and deployment environment. The Operators are grateful to the thousands of contributors who develop and maintain the open-source software that forms the foundation of the modern internet.
SECTION 4. GENERAL PROVISIONS, ACKNOWLEDGMENTS, AND THE LEGAL FRAMEWORK GOVERNING THIS LICENCES PAGE
4.1 Completeness and Accuracy Disclaimer
This Licences page is provided for informational purposes only and may not be complete, accurate, current, or exhaustive. The Operators make no representation or warranty that: (a) this list includes all third-party services, packages, libraries, frameworks, or dependencies used by the Service; (b) the version numbers, licence types, or other information provided herein are accurate or current; (c) the use of any third-party resource complies with its applicable licence terms; or (d) any third-party resource is used in accordance with its intended purpose or licence conditions. The Operators encourage users to refer to the respective project repositories, websites, and documentation for complete and authoritative licensing information.
4.2 Acknowledgements
The Operators wish to express their sincere gratitude and appreciation to the developers, maintainers, contributors, documenters, testers, supporters, and communities behind every open-source project and third-party service that the Service uses. The Service stands on the shoulders of giants, and the Operators are acutely aware that without the countless hours of unpaid or underpaid labor contributed by individuals around the world to free and open-source software, the Service would not exist. The Operators encourage all Users who benefit from open-source software to consider contributing back to the projects they depend on, whether through code contributions, documentation improvements, bug reports, financial support, or simply by expressing gratitude to the maintainers who keep the digital world running.
4.3 Contact Information
If you have any questions, concerns, corrections, updates, or other communications regarding this Licences page, or if you believe that any licensing information provided herein is incorrect, incomplete, or outdated, please contact the Operators through the official Discord server, accessible at https://fm.erlc.dev/discord. The Operators will make reasonable efforts to review and address any concerns raised and to update this page as appropriate.
This Licences page is a small token of gratitude for the vast ecosystem of open-source software and third-party services that make erlc.fm possible. Every package listed here represents countless hours of labor, love, and dedication from developers around the world. If you are a maintainer of any project listed here (or of any project not listed here that the Service uses), please accept the Operators' heartfelt thanks. You are the reason the internet works as well as it does. The Operators hope that the Service's existence, in some small way, justifies the effort you have put into your own work.