Case study · DBETA (in-house)
Bones 9: The Customer Portal
Our own platform work: the Bones 9 customer portal for client organisations. Specified and prototyped; 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 portal has a page-by-page specification and a working prototype. The specification is still under review, and 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 handle all of it in one place.
02 · What it covers
What a client organisation will manage
The specification sets out each page of the portal. It covers:
- the organisation’s profile, users, contacts and responsibilities
- its Bones installations, whether managed by us or self-hosted
- entitlements, releases and downloads
- domains, going live and backups
- support tickets
- orders, billing and invoices
Support tickets raised here are handled by our team in the staff console.