open-webui/terminals — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2026-04-27
Give each user logging into Open WebUI their own isolated container with separate files and resource limits.
Set up a data-science policy with extra processing power and pre-installed Python packages for one group of users.
Set up a restricted sandbox policy with limited network access and storage for a different group of users.
Let students in an educational setting each get their own workspace without interfering with one another's runaway processes.
| open-webui/terminals | liuboyu/hyperledger-fabric-docs-zh_cn | video-db/skills | |
|---|---|---|---|
| Stars | 84 | 84 | 84 |
| Language | Python | Python | Python |
| Last pushed | 2026-04-27 | 2018-01-10 | — |
| Maintenance | Maintained | Dormant | — |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 1/5 | 3/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an Open WebUI Enterprise License for production use, plus Docker or Kubernetes infrastructure already running.
Terminals gives every Open WebUI user their own private, isolated container that spins up on login and tears down when they leave, so teams can share compute without users interfering with each other.
Mainly Python. The stack also includes Python, Docker, Kubernetes.
Maintained — commit in last 6 months (last push 2026-04-27).
Requires an Open WebUI Enterprise License for production use, no other license terms were stated in the explanation.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.