---
title: "Player architecture and security"
slug: "player-architecture"
updated: 2025-12-05T08:36:59Z
published: 2025-12-10T14:08:19Z
canonical: "docs.grassfish.com/player-architecture"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grassfish.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Player architecture and security

The Grassfish player’s architecture supports security measures.

****Player software****

The player software consists of:

- Web service
- FAST Broker
- Add-on system for extensions

****Internal communication****

Internal communication can be handled via Message Queuing Telemetry Transport (MQTT), for example.

****HTTP port****

The player web service's HTTP port can be closed or restricted as needed.

****API authentication****

Authentication to the player API is available; SSH access can be controlled or disabled.

****Local storage****

Local player storage holds the media necessary for operation. Expired content is replaced with new content or deleted.