For your IT person
How Wenbru TMSis built and hosted.
Where it runs, what it is built with, and how we host it.
Back to Wenbru TMSWhere it runs
WhereDetail
- Management web applicationBrowser-based and responsive; sidebar by business purpose; every link shown only when you hold the capability and the module is on.
- Tool Cupboard tablet stationA shared, paired shop-floor tablet with touch-first chrome; sign-in by tile and cupboard password, never a web login.
- TV production boardAn auto-refreshing wall display for the shop, shown by a display account carrying no restricted data.
- Installable PWA and Android appAdd to Home Screen for a full-screen app with your icon; an Android wrapper of the same site, distributed internally.
What it is built with
- Python 3.11 · Django 5.2 — one server-rendered application, no SPA build chain
- PostgreSQL 16 in production; row locking and concurrency tested against PostgreSQL
- Docker Compose: one application container and one database container per customer
- Gunicorn behind nginx with TLS; WhiteNoise static files — no CDN, no telemetry
- PWA manifest and service worker; Android Trusted Web Activity wrapper
- Deliberately not used: microservices, queues, Kubernetes
How it is hosted
We host it. Your data sits in its own database and is backed up every day.
- One customer, one isolated cell: its own database, media volume and deployment identity. No shared-database multitenancy, no tenant column anywhere.
- Deployment identity is recorded once and never changes; the environment is explicit and fail-closed — the application refuses to start without it.
- Hosted by Wenbru as a dedicated cell: Docker Compose on a Linux host behind nginx with TLS.
- Releases are built from a tagged commit into a tagged image and verified before deploy; rollback is re-tagging the previous image.
- Daily backups with a signed manifest carrying identity, migration state and checksums; a restore refuses another customer’s backup.
- Four append-only evidence trails: domain audit, stock ledger, operation time record and configuration audit. Corrections are new rows; nothing is edited in place.
- More than 800 automated tests in the documented full-suite runs, including two-connection PostgreSQL concurrency tests.
Talk to us
Show us one job.
Send one job the way you run it today. We will show you how it runs in Wenbru.