Renderers
The Renderer service generates the visual output that display devices show. By default, Inspire includes a single Renderer instance. You can add more instances for horizontal scaling and load balancing across large deployments.
Navigate to Settings > Renderers to manage Renderer instances.
Requires the Admin role and the DIRECT_RENDERER entitlement (Professional plan and above).
Cluster Overview
The top of the page shows four summary cards:
| Metric | Description |
|---|---|
| Instances | Total number of configured Renderer instances |
| Healthy | How many instances are reachable (e.g. “2/3”) |
| Endpoints | Total active endpoints across all instances |
| Clients | Total connected display clients across all instances |
Instance Health
Each Renderer card shows real-time health metrics when the instance is reachable:
| Metric | Description |
|---|---|
| CPU | Current CPU utilisation (amber above 80%) |
| Memory | Memory usage in MB (amber above 2 GB) |
| Endpoints | Number of active endpoints on this instance |
| Clients | Number of connected display clients |
| Uptime | How long the instance has been running |
Health data auto-refreshes every 60 seconds. Click Refresh to manually update.
Unreachable instances show an “Offline” badge and a message to check the service.
Connection Modes
Each Renderer instance has a connection mode:
| Mode | Description |
|---|---|
| Proxy | Display traffic routes through the Edge server. Simpler to set up — no public URL needed. |
| Direct | Displays connect to the Renderer’s public URL directly for lower latency. Falls back to Edge automatically if the Renderer is unreachable. |
Direct mode requires setting a Public URL that display devices can reach.
Adding a Renderer Instance
- Enter the internal address of the Renderer (e.g.
http://renderer-2:8080) - Optionally enter a Public URL for direct connections (e.g.
https://renderer-2.example.com) - Select the connection mode (Proxy or Direct)
- Click Test to verify connectivity before adding
- Click Add to register the instance
The test checks whether Edge can reach the Renderer at the given address and reports the Renderer version if successful.
Editing a Renderer Instance
Each instance card has editable fields for the public URL and connection mode. Change the values and click Save to update. Click Discard to revert.
Removing a Renderer Instance
Click the delete icon on any instance card. You cannot remove the last remaining instance — at least one Renderer must always be configured.
Removing a Renderer instance while it has active clients will cause those clients to reconnect to another available instance. There may be a brief interruption.
Scaling Guidance
| Deployment Size | Recommendation |
|---|---|
| Up to 50 endpoints | Single Renderer instance is sufficient |
| 50-200 endpoints | Add a second instance for redundancy |
| 200+ endpoints | Scale horizontally — one instance per 100-150 endpoints |
Each Renderer is stateless. New instances can be added or removed at any time without downtime. Edge automatically load-balances endpoints across available instances.