Fire engineering is a signed profession. The assessment that leaves your office carries your practice's name and your engineer's judgement — so the tool that helped produce it has no business appearing on the cover.
Branding reaches the output in several places, and a half-applied white-label is worse than none — a document with your cover and somebody else's footer on page forty is the kind of detail an approver notices and a client asks about.
Practice identity is applied consistently across the generated document, the basis of design, the dashboards and the exported artefacts. An unbranded deployment is unaffected: the neutral output is the default, and branding is additive rather than a mode that changes what the checks do.
Nothing about white-labelling touches the register. You are rebranding the document, not softening it.
Your own isolated instance, run by us. Your schemes are not co-mingled with anyone else's. The usual choice for practices without an internal platform team.
Deployed into your AWS, Google Cloud or Azure tenancy, under your existing agreements, billing and security posture. Data never leaves infrastructure you already control.
Hardware you own, inside your network. For schemes where the geometry itself is sensitive and where "the cloud" is not an acceptable answer to a client.
Ashbeck is built as a single-tenant appliance rather than a shared multi-tenant platform with isolation added afterwards. That decision costs us operational simplicity and buys you a much shorter answer when your client's security questionnaire asks who else's data sits alongside theirs.
Nothing issues itself. A document reaches issue when an engineer with the authority to do so confirms it — and the register is in front of them when they decide, with any blocker stated plainly rather than buried in an appendix.
Where a finding is overruled, that is a legitimate professional judgement and the system does not pretend otherwise. What it will not do is let a blocker pass silently. The decision to proceed against a finding is a decision somebody made, and it should look like one in the record.
White-label setup is a piece of work: identity and marks, document templates, the house conventions your reports already follow, sign-off roles, and validation that the branded output is correct in every artefact it touches. It is scoped and quoted as a one-off alongside the licence rather than assumed to be free.
We would rather set it up properly once, with your document lead in the room, than hand over a settings page and discover the discrepancy on your first issued report.
The most productive white-label conversation starts with a document you already issue, so we can talk about the specific conventions yours follows rather than about branding in the abstract.