DLK Studio
← All case studies
Case study · ongoing

Super 5

WHS + security ops platform · Multi-tenant SaaS

One platform for WHS governance, security ops, and venue compliance — built so a single login serves a security company OR a venue, with role-aware modules each side actually uses.

The problem

AU venues and security companies juggle 5+ disconnected tools — incident reports in one app, guard rosters in another, WHS hazard logs in a spreadsheet, sign-in books on paper. Existing 'one-stop' platforms either treat venues + secco as the same user (they aren't) or force one side to use the other's workflow. Audit time is a nightmare.

What we built

Multi-tenant architecture where the same user account can belong to BOTH a security company (SECCO) AND a venue with different roles in each. Modular by function — WHS governance, VenueGuard (rostering + assignments), Fire Watch, Security Ops, Compliance IQ — venues + seccos each see only what's relevant. Built with audit-grade decision traceability (Swiss-cheese failure prevention, psychosocial risk modelling, foreseeability tracking) for AU WHS Act compliance.

Results

What it delivered.

  • Multi-tenant architecture with VENUE and SECURITY_COMPANY org types
  • Single user can hold roles across both org types (e.g. a guard who also manages a venue)
  • 5 functional modules (WHS · VenueGuard · Fire Watch · Security Ops · Compliance IQ)
  • VenueGuard blocker engine: 14 rules covering licences, training, evidence, availability
  • Bi-directional invite flows — venues invite seccos, seccos request venues
  • Currently in active build — early-access customers onboarding
Tech stack
Next.js 14Postgres (Neon)PrismaNextAuthMulti-tenant row-level securityVercelAnthropic Claude (WHS reasoning)

Want one for your industry?

The same playbook applies anywhere with real-world workflows and paying customers. Let's talk.