A multi-device teleprompter application that enables real-time teleprompter control between devices. One device (computer) acts as a controller to edit scripts and manage playback, while one or more other devices (phones/tablets) display the teleprompter text.
This project was made to facilitate recording videos for my YouTube channel where I use my phone on a basic teleprompter in front of my camera and need to control it from my computer running OBS. With this project I can simply navigate to a URL on my phone and manage everything from my computer without touching the phone again until I'm done.
Multiple teleprompter clients are supported to account for multi-camera setups with multiple teleprompters.
| Landing Page | Controller Mode | Teleprompter Mode |
 |
 |
 |
| Select your role to get started | Edit scripts and control playback | Display the scrolling text |
- Docker
- Docker Compose
The application ships as a single container. Copy compose.yaml and run:
docker compose up -dThe app will be available at http://localhost:8080.
| Environment Variable | Description | Default |
|---|---|---|
PORT |
HTTP listen port | 8080 |
OIDC_ISSUER_URL |
OIDC issuer URL (e.g. https://keycloak.example.com/realms/myrealm). Setting this enables multi-user mode. |
(unset — single-user mode) |
OIDC_CLIENT_ID |
OIDC client ID (required when OIDC_ISSUER_URL is set) |
— |
OIDC_CLIENT_SECRET |
OIDC client secret | — |
OIDC_REDIRECT_URL |
Absolute callback URL, e.g. https://tp.example.com/auth/callback (required when OIDC_ISSUER_URL is set) |
— |
OIDC_SCOPES |
Space-separated scopes to request | openid profile email |
By default there is no authentication and no user separation: everyone who opens the app shares the same script and playback state (single-user mode), exactly as before.
Setting the OIDC_* environment variables switches the app into multi-user mode, authenticating against any OIDC provider (e.g. Keycloak) via the authorization code flow with PKCE. There is no local/password auth — OIDC is the only login method.
In multi-user mode:
- Every user gets their own session (one per user, created on first visit) at
/session/<id>, with its own script, teleprompters, and playback state. - Other users navigating to your session URL get a 404 — sessions are private by default.
- The session owner can invite other users by email from the controller sidebar ("Session Members"). Once invited, a user can open the session link (which the owner shares with them) and join as a controller or teleprompter. Access can be revoked the same way.
- All state (sessions, memberships, logins) is in-memory and resets when the container restarts.
Example Keycloak setup: create a confidential OpenID Connect client with Standard flow enabled and https://<your-host>/auth/callback as a valid redirect URI, then run:
OIDC_ISSUER_URL=https://keycloak.example.com/realms/myrealm
OIDC_CLIENT_ID=teleprompter
OIDC_CLIENT_SECRET=<client secret>
OIDC_REDIRECT_URL=https://tp.example.com/auth/callbackThis code has been mostly AI generated and used as a playground/testbed. My manual intervention has been minimal, mostly doing cleanup. Thus, I take no "ownership" over this code. Feel free to do whatever. As the LICENSE states: "This is free and unencumbered software released into the public domain".