Live demo¶
The public demo is a real ShinyHub installation running a curated fleet of R and Python applications.
Explore anonymously¶
Public applications open without an account. They use synthetic bundled data and run on an application origin isolated from the dashboard and API.
The fleet includes examples built with Python Shiny, R Shiny, Dash, and Streamlit. The experimental agent capabilities demo has a scripted assistant that can explain synthetic dashboard data, change the selected view, and undo that change. Agent integration is for evaluation and may change; do not depend on it for critical workflows. This public demo uses no model API key or paid model requests. Applications hibernate when idle, so the first request may briefly show ShinyHub waking the process.
Explore the control plane¶
Choose Continue as Demo Viewer for one-click access to the real control
plane. No account is created. The resulting session has the global viewer
role: it can inspect applications and viewer-safe operational state but cannot
deploy, change configuration, manage users, or create credentials. No signup or
third-party identity is required.
The collapsed manual-login fallback uses username demo-viewer and password
explore-shinyhub-demo. This credential is intentionally public and carries
the same read-only permissions.
The shared demo intentionally does not accept visitor-provided code. A writable sandbox would require a separate, disposable tenant boundary rather than broad permissions on this instance.
Safety boundaries¶
- Every public identity starts as
viewer. - Application containers have fixed CPU, memory, session, and replica limits.
- The fleet is reconciled from version-controlled manifests.
- The public agent demo rejects model and external-agent credentials at startup.
- Demo data is synthetic and can be replaced during reconciliation.
- Administration uses a separate non-public credential.
Want to run the same stack yourself? Start with the Docker Compose installation.