§ Why QPrint
University print shops process thousands of jobs every week — but without a centralised data layer, operators cannot identify peak demand, catch failures early, or understand which campuses are underserved. Revenue leaks. Opportunities vanish.
QPrint Analytics is the cloud dashboard Q-Print shops sync to — giving campus administrators a single source of truth for every job, across every shop, in real time.
Campuses Monitored
Multi-university deployment
Sync Frequency
Data never more than 5 minutes stale
Job Success Rate
Reliability tracked across all active shops
Trend History
Analyse up to 90 days of print trend data
§ Data Flow
Q-Print is an end-to-end print queue management system. Every job a student submits flows through a transparent pipeline — and the aggregated intelligence surfaces here.
Student Prints
Upload PDF at campus shop
qprint-<slug>.local:3000Picks settings — colour, copies, paper size
Job submitted
POST /api/jobs/uploadFile stored + DB record created
qprint.db (SQLite) + file storageFastAPI (port 8000) confirms job queued
Admin Dispatches
QueuePanel auto-refreshes (QFileSystemWatcher)
Admin double-clicks job → JobDetailDialog
Selects printer and clicks Print
PyMuPDF renders PDF pages at printer DPI
win32print sends to physical printer (Windows)
printer_manager.pyAnalytics Sync
analytics_sync.py runs every 5 minutes
analytics_sync.pyAggregates daily job stats per shop
Pushes to cloud analytics service
POST /api/analytics/syncQPrint Analytics processes and stores data
Dashboard reflects latest insights in real time
Tracked per Shop
§ Get Running
Q-Print ships a single setup script that handles everything — Python virtualenv, npm install, config files, and directory creation. One command gets you from clone to running.
Windows only: After setup, install pywin32 manually — it is excluded from requirements.txt for cross-platform compatibility.
Clone the Q-Print repository
Run the setup script — handles everything
Windows only — install pywin32 for printing
Activate the virtual environment
Start everything — FastAPI + Next.js + Admin UI
Ports
:3000:8000Students open qprint-<slug>.local:3000 in their browser.
§ The Creator
Built Q-Print and QPrint Analytics from scratch to solve a real visibility problem observed across university campus print shop networks.
Every print shop I visited was flying blind. No numbers, no patterns, no decisions. I built Q-Print and QPrint Analytics because the data was always there — it just needed a way to speak.
Vivek Vaish
Creator, Q-Print & QPrint Analytics
§ Open Source
Both Q-Print and QPrint Analytics are open source. If your university has a different setup, or you need a feature — open an issue or send a pull request. Shop owners with technical feedback are especially welcome.
New Campus Integration
Add support for your university's print shop infrastructure or data formats.
Hardware Support
Integrate additional printer models or campus point-of-sale systems.
Analytics Features
Propose new metrics, visualisations, or reporting dimensions.
Performance
Optimise sync speed, API latency, or dashboard load time.
Bug Reports
Found an issue? Open a detailed report with reproduction steps.
Pull Requests
Fork, improve, and submit. All contributions are reviewed and welcome.