For your IT person

How Wenbru SBMSis built and hosted.

Where it runs, what it is built with, and how we host it.

Where it runs

WhereDetail

Public website on your domainHomepage, product catalogue with variants, quote-request basket, booking and contact forms, e-signature pages, app download page.
Web portalDashboard, quotes, website requests, invoices, customers, leads, bookings, equipment register, workshop, catalogue admin, reports, staff, archives, audit trail.
Android field appClient-branded per deployment; technicians’ jobs, quotes, job cards, equipment, leads; owner dashboard and approvals; installed from your download page.
Documents and e-mailQuotations, tax invoices, statements and equipment registers on your letterhead, sent with signing links.

Next.js (React, TypeScript) with Tailwind CSS
PostgreSQL 17 with row-level security behind a Supabase-compatible data API; all money stored as integer cents
Expo / React Native Android app; release-signed APK from your download page
PDF generation server-side; transactional e-mail; Expo push notifications
Signed JWT sessions with revocation; bcrypt; input validation; rate limiting on public forms and login
Docker Compose stack per client for Wenbru-hosted deployments; a dedicated managed project per client for the cloud flavour
Continuous integration with automated tests and an artifact identity scan that fails the build if any client identity is found in the product image

We host it. Your data sits in its own database and is backed up every day.

Isolation model: each client gets a separate deployment with its own database, own storage, own generated secrets and own domain and branding. A new deployment starts from an empty baseline, never from another client’s data. This is the Wenbru-hosted model, proven in acceptance with two independent test deployments.
One product, many clients: a single generic product image is run per client with a validated configuration file. Two independent test deployments were run from the identical image and proven unable to reach each other.
Configuration, not code: identity, legal details, banking, domain, brand palette, letterhead, equipment vocabulary, asset-tag prefix and optional modules are per-client configuration, recorded as revisions.
Fail-closed: with no valid configuration the server refuses to serve; there is no fallback identity.
Wenbru-hosted: a five-container stack per client on its own private network; the host’s public web server is the only ingress. Cloud flavour: a dedicated managed project per client with provider-managed TLS.
Backups: nightly database dump, encrypted client-side and pushed to a per-client off-site destination; every hosted deployment is restore-tested before it is marked ready.
Append-only audit log for logins, quote and invoice changes, payments, voids, staff and catalogue changes; a separate movement log for every equipment change.

Talk to us

Send one job the way you run it today. We will show you how it runs in Wenbru.