Skip to main content

Case study · DBETA (in-house)

Bones 9: The Staff Console

Our own platform work: the Bones 9 staff console for DBETA’s team. Specified and prototyped; in development.

Bones 9 · Staff Console · Laravel

Client
DBETA (in-house)
Location
London, UK
Expertise
Internal Tools, Platform Development, Access Control
Date
1 Nov 2026

Status

In development, not yet available

This is our own platform work, not a client project. Bones 9 is in development and is not generally available, and there is no release date. The console has detailed specifications and an exploratory prototype. The specifications are still under review, and no part of them is approved for production use.

01 · Why it is needed

Our team’s side of the same system

When client organisations manage their sites through the customer portal, our team needs its own tool to run the installations we look after, answer support and handle the commercial side. That is the staff console.

Illustration · rules and review around each change

02 · What it covers

One console, three separate areas

  • operating the installations we manage
  • handling support cases raised from the portal, from first message to close
  • commercial administration

It is designed so that each person is given access to specific areas only, access is reviewed by someone other than the person holding it, and actions across the console are recorded in an audit trail.