Alpha · version 0.1.24 · open source, Apache-2.0
POps is a free, open-source platform that brings inventory, remote commands, software deployment, exam mode and signed updates together on your own server. It is built for school IT teams and stays transparent to the students and teachers at the keyboard.
Demo sign-in: user demo, password demo. Read-only, about 50 simulated PCs, reset every night.
One web panel instead of separate tools for inventory, remote help, software deployment, exams and updates: an open-source RMM made for schools.
Hardware, installed software and Windows Update state, plus who is signed in and which PCs are off, at a glance.
Send a command to one PC, a lab or all of them, and see the output, the exit code and who sent it.
Upload an MSI or a script, or pick from the winget catalog, and send it to a lab. Files are checked with SHA-256 before anything runs.
Vision v2 gives you live screen, mouse and keyboard, with several monitors and the clipboard. A session starts only when the user accepts it or after an on-screen notice.
Limit a lab’s network to an allow list for the length of an exam. When time is up, the PCs return to normal on their own.
Each PC verifies the signature of an agent release itself. If a new version does not come up, the previous one is restored automatically.
Quarantine a PC with a lock screen and network isolation. The DNS policy detects and reports visits to listed domains.
Automate with a versioned REST API v1 and API tokens; sign in to the panel with LDAP/Active Directory or OpenID Connect.
Also: file transfer, Wake-on-LAN, help desk, licence tracking, reports, per-PC capability switches, an English and Turkish panel, and a first Linux agent for Pardus and Debian.
Screenshots of the current version, with the demo’s made-up school. Click a screenshot to enlarge it.
Every PC in one list. Click one to see its hardware, exam state and recent jobs in a side panel.
The lab’s seating plan. During an exam you see the time left, the allowed addresses and each PC’s exam state.
POps is designed to start with one lab and grow. Because it is alpha software, we recommend a pilot in a single lab first.
For ICT teachers and teachers who look after the school’s computers: the lab’s inventory, software installs and exam day in one panel.
For IT teams that support public (MEB) schools: remote support, an audit log and district → school organisational units. Several schools on one server has not been tried in the field yet; start with one school.
For schools with their own IT team: no licence fee, and the data stays on the school’s own server.
For IT departments that run computer labs. POps started in a Turkish state university’s IT department.
In a school, the person at the keyboard is often a student. POps gives administrators strong tools and makes sure everyone knows when those tools are used.
A remote screen session starts when the user accepts a prompt that names the administrator and the reason. A mandatory session shows a full-screen countdown, and its reason is recorded.
The tray icon is always visible and there is no keystroke logging. From the tray, the user can see the remote actions taken on the PC in the last 30 days.
Remote terminal and screen view can be turned off on each PC at install. The server can only switch them off, never back on.
A privacy notice template and a data inventory for KVKK, Türkiye’s data protection law, come with the docs. Each PC also writes remote actions to its own Windows event log.
No cloud account. Your data stays on the school’s own server, and all of the source code is open.
The panel loads nothing from other hosts, so it works on the school’s LAN with no internet connection.
KVKK notice template (Turkish) →Positioning: POps next to classroom tools →FAQ →
Designed to keep limits even if the server is taken over: any single layer is assumed to fail.
Agent releases are ed25519-signed in CI and verified by both the server and the PC. The signing key never reaches the server. Release tags are SSH-signed.
Security-relevant actions go to a SHA-256 hash-chained audit log; editing it breaks the chain.
Optional TOTP two-factor sign-in, LDAP/Active Directory and OpenID Connect, and superadmin, admin and viewer roles.
Every change is scanned with CodeQL, and the repository is rated by OpenSSF Scorecard. GitHub Actions are pinned to commit SHAs.
The code that parses agent messages, request models and the signed release manifest is fuzzed with Atheris in CI.
Backend dependencies are hash-locked, and the Docker images ship with an SBOM and build provenance.
Threat model and remaining risks (SECURITY.md) →OpenSSF Scorecard result →Report a vulnerability: security@pashacore.com.tr →
Try the demo first. If you like it, start with one lab.
On a Linux server with systemd (AlmaLinux, Rocky, RHEL, Debian and Ubuntu are tested), the install script sets up PostgreSQL, the Python environment, the web server and HTTPS. Docker Compose works too.
Sign in to the panel as admin, change the password and turn on 2FA. Then create an enrollment token for a lab on the System page.
Install the MSI on each Windows 10/11 PC with the server address and the token; the .NET runtime comes with it. A .deb package covers Pardus and Debian.
git clone https://github.com/PashaCore/POps.git
cd POps
sudo Installer/server/install.sh
# prints the panel admin password at the endQuick startInstallationDockerGetting startedAll documentation
Demo sign-in: user demo, password demo. Read-only, about 50 simulated PCs, reset every night.
Yes. POps is open-source software under the Apache-2.0 licence, with no licence fee. The source code is on GitHub; you can copy it, change it and run it on your own server. The real cost is the IT work to install and maintain the server.
The first Linux agent is a .deb package for Pardus 23 and later, Debian 12 and Ubuntu 24.04, with inventory and remote commands. Screen view, quarantine and the tray are Windows-only for now. The agent has run on Debian 12 and in CI, not yet in a Pardus lab.
It does not replace Veyon. Classroom tools such as Veyon let a teacher watch screens, show their own screen or lock PCs during a lesson. POps is for the IT team that runs the lab: inventory, software deployment, updates, remote support and an audit log. Both can run on the same PCs.
No. A routine remote screen session starts when the user accepts a prompt that names the administrator and the reason. A mandatory session (for example during an exam) first shows a full-screen countdown, and its reason is recorded. The tray icon is always visible, there is no keystroke logging and screen frames are not stored.
The server is installed with one script, and the agent with one MSI command per PC. Our pilot school guide plans about one hour for the installation day of a 10-PC lab when the preparation is done in advance; that is a plan, not a measurement.
The obligations under KVKK, Türkiye’s data protection law, belong to your school; POps is designed to make them easier. Data stays on the school’s own server, the docs include a privacy notice template and a data inventory, and remote actions are shown to the user and written to the audit log.
Yes. POps is designed to run on the school’s LAN without an internet connection: the panel loads nothing from other hosts, the certificate can come from a school certificate authority created on the server, and agent updates can be uploaded in the panel by hand.
In measurements, one server process brought 5,000 simulated agents back within 11 seconds of a restart. For up to 500 PCs, a VM with 2 vCPUs, 4 GB of memory and a 40 GB SSD is recommended. District → school organisational units exist, but several schools on one server has not been tried in the field yet.
POps is Apache-2.0 licensed. The code, the roadmap and the discussions are on GitHub; write in English or Turkish.
Figures come from GitHub and refresh every 15 minutes.
Source code, release notes and signed packages.
Go to the repository →Ask questions, share ideas and tell us how it works in your school.
Join the discussions →What comes next and why, in discussion 114.
See the roadmap →Issues labelled “good first issue” are picked for newcomers; docs and tests are welcome too.
Find an issue →The whole path from enrollment to a signed update and rollback has been run on real Windows PCs, but POps is not yet hardened for large or enterprise production. Known limitations:
POps started in a real computer lab at a Turkish state university’s IT department. This project is the open-source redesign of that work, developed by Pasha Core.