asciinema server exposes terminal history through more than one surface
asciinema records terminal sessions and can host them on a self-managed server. The recordings can include command output, hostnames, paths, tokens, database queries, and debugging details that never belonged in a ticket.
The count-only observations from 2026-11-15 used page 1, pagesize 1, and sub_type=all. app="asciinema" returned 0, title="asciinema" returned 91, and http.body="asciinema server" returned 114. These are small enough for manual validation and broad enough to include documentation.
Inventory every admin path
asciinema server documentation describes an admin panel for users, recordings, streams, authorized CLIs, visibility, and account deletion. It also warns that the dedicated admin endpoint performs no authentication, so anyone who can reach its port has full admin access.
Place that endpoint behind an authenticated proxy or bind it only to an administrative network. Do not assume that the normal web login protects a separately exposed port. Review the process arguments, firewall rules, container ports, and reverse-proxy routes that could publish it.
Uploads need their own policy. The documentation says uploads do not require authentication by default. Set the server option that requires authentication if anonymous uploads are not intended. Review whether a new signup can upload, stream, or create public recordings.
Treat recordings as sensitive evidence
Recordings can reveal secrets in terminal output even when the title is innocuous. Set a retention period, review private and unlisted recordings, and remove material that is no longer needed. Protect the object store and database backups as copies of the same content.
Review the API and authentication model. The API uses account credentials for some operations and documents an install identity for CLI uploads. Record which identities are authorized, how they are revoked, and which recording visibility they can choose.
Test visibility and administration
Create a private recording and request it as a different user. Try the admin endpoint from a non-administrative network. Upload with and without authentication according to policy. Check that each result is logged with the account and the recording identifier.
asciinema is useful because it captures context that logs miss. That same context explains why the server, upload path, admin port, and recording retention need one security review.

