Skip to main content

Case study · DBETA (in-house)

Bones 9: The Customer Portal

Our own platform work: the Bones 9 customer portal for client organisations. Designed and prototyped; specification in draft; in development.

Bones 9 · Customer Portal · Laravel

Client
DBETA (in-house)
Location
London, UK
Expertise
Client Portal Architecture, Platform Development
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 Customer Portal is in development: the screens are designed and can be clicked through as a prototype using sample data, and the page-by-page specification is still a draft. No part of it is approved for production use.

01 · Why it is needed

One place for everything behind a site

A website on Bones 9 comes with more than pages: an account, people who need access, an installation to keep up to date, support and billing. The customer portal is being designed so a client organisation can see much of it in one place.

Illustration · the customer portal, with example data

02 · What it covers

What has been designed so far

The draft specification sets out each page of the portal. The screens designed so far cover:

  • an overview of what needs attention, the organisation’s profile and contacts, and the people who can use the portal
  • its Bones installations: requesting a managed one, registering a self-hosted one (self-hosting is planned, not yet available), activation, recovery and transfer
  • entitlements, and requesting a change to them
  • release notes, channels and downloads
  • domains, and going live with a custom domain
  • evidence of backups and recovery drills
  • raising, following and replying to support tickets
  • reviewing our team’s requests to access an installation
  • invoices, payment status and billing contacts
  • account settings

Some further actions, including inviting users and ordering or paying in the portal, have been proposed but are not decided.

Raising, following and replying to tickets in the portal is designed. How support requests reach our team in the staff console is still being decided.