Branding & Custom Domains
Brand once. Apply consistently.
Your brand should not stop at the login screen. Hamiltonn Cloud is designed to apply supported customer identity across applications, portals, custom domains, communications, documents and installed PWA experiences from one structured branding system.
Brand profile
Northstar Finance
app.northstar.example
Northstar · NF
Portal · PWA · Email · Documents
What is white-label branding?
Make Hamiltonn-powered software look and feel like part of your organisation.
White-label branding applies your organisation's customer-facing identity to software developed and maintained by Hamiltonn Cloud.
Supported branding can include company identity, logos, colour settings, domains, portal identity, application identity, communications and business documents. The goal is consistent customer recognition without turning every tenant into a separate software project.
Central configuration
Branding should be configuration — not repeated development work.
A scalable white-label platform should not require source-code edits every time a new logo, colour or domain is added. Hamiltonn treats customer identity as structured tenant configuration that feeds supported product experiences.
One source of brand configuration. Multiple customer touchpoints.
Brand profile
- Company & product identity
- Logo, icon & colours
- Domains & application name
- Email, documents & legal details
Visual identity
A brand system built for software, not just a homepage.
Organisation identity
Keep legal name, trading name, product name and support identity as structured values rather than treating them as interchangeable text.
Logo system
Primary logo, compact mark, favicon, PWA icon, email logo and document identity can use appropriate asset variants.
Colour system
Apply primary, secondary and accent values through controlled design tokens rather than hard-coded page edits.
Typography
Maintain a strong core type system so customer branding does not introduce layout, licensing or accessibility problems.
Design system
Customers choose the brand. The platform protects usability.
Hamiltonn's frontend should map customer branding into controlled design tokens so hover, focus, disabled, selected and text-contrast states remain coherent across the application.
Colour choices can be validated for contrast and accessibility rather than allowing a brand setting to make the product unreadable.
brand-primary brand-secondary brand-accent logo-primary logo-compact app-name
Custom domains
Put the platform on your domain.
Supported deployments can use customer-owned domains or subdomains such as app.yourcompany.com, portal.yourcompany.com or another verified hostname appropriate to the product.
Add domain
Enter the hostname to connect.
Verify control
Use the required DNS record to prove domain control.
Configure routing
Associate the verified hostname with the correct tenant environment.
Enable HTTPS
Provision the supported TLS configuration.
Validate
Check routing, certificate and customer identity.
Activate
Publish the customer-facing domain.
Domain control is verified before activation so one customer cannot claim another organisation's hostname.
Application identity
Carry the brand through the complete product journey.
Customer portal
Login, registration, dashboard, navigation, profile, documents, support, empty states and customer workflows.
Staff & admin
Staff login, operational dashboards, customer management, projects, reporting and configuration.
Browser identity
Application name, title, favicon and customer domain remain aligned with the tenant brand.
Authentication states
Invitations, password reset, verification, account recovery and access-denied experiences remain recognisably part of the same product.
Installed experience
Your identity should survive installation.
For Hamiltonn products delivered as progressive web applications, the tenant brand can flow into the installed application experience: app name, short name, icon, theme and launch identity.
PWA manifests and icons should resolve to the correct tenant when the same Hamiltonn platform powers multiple branded domains.
App name
Northstar
Home-screen identity
Square icon · theme · branded launch
Platform communications should look like part of the same product.
Supported Hamiltonn-generated emails can use the customer's approved sender identity, logo, brand wrapper, support information and message templates.
Sender identity
Display name, approved sender address and reply handling under the customer communication model.
Domain verification
Customer sending domains can use appropriate DNS authentication such as SPF, DKIM and DMARC within the email architecture.
Reusable templates
Separate the brand wrapper from welcome, invitation, verification, quote, project, security and operational message content.
Documents
Brand the records customers download and keep.
Supported generated documents can combine a shared document structure with tenant branding and dynamic customer or transaction data.
Financial documents
Statements, confirmations, reports and customer notices.
Business documents
Quotations, invoices, booking documents, reports and operational records.
Legal identity
Registered company information, addresses, registration numbers and required disclosures can remain separate from the trading brand.
Brand hierarchy
One brand across products — or brands above brands.
A customer can reuse one organisation identity across Financial Cloud, Business Cloud and AI Cloud, while agency and reseller models can support additional customer-level branding beneath the partner.
Organisation default
Canonical company identity inherited across products.
Product override
Use a related product name or selected brand variation where the business needs it.
Agency → client
Support separate client brands under an agency or reseller relationship without changing Hamiltonn's core product code.
Governance
Preview, validate and publish — instead of editing the live brand blindly.
Draft
Edit identity without immediately changing production.
Preview
Review portal, mobile, PWA, email and document surfaces.
Validate
Check assets, contrast, domain, email identity and required company fields.
Approve
Use permissions or approval workflow for sensitive brand changes where required.
Publish
Activate the new brand configuration.
History
Keep important brand changes traceable and recoverable.
Brand security
White label should not enable impersonation.
Sensitive brand configuration such as domains, email senders and legal identity should use authentication, permissions, verification and audit controls.
Customers are responsible for having the right to use the company names, logos, trademarks, domains and other assets they provide.
- Domain ownership verification
- Verified email identity
- Role-based branding permissions
- Required legal and regulatory disclosures remain visible where applicable
Search & AI boundaries
Public brand content can be discoverable. Private tenant data stays private.
Public marketing pages can be indexed by search and AI systems where intended. Authenticated customer portals must remain protected by access controls and should never expose private tenant data merely to improve discoverability.
Public content
Crawlable HTML, canonical URLs, structured data and deliberate search visibility.
Private application
Authentication and authorisation protect customer data regardless of crawler behaviour.
Customer console
Give customers control without giving them source-code access.
The Hamiltonn branding console can become the operational centre for company identity, logos, colours, domains, application identity, email, documents, legal details, preview and brand history.
Branding
Overview · Company Identity · Logos · Colours · Domains · Application · Email · Documents · Legal · Preview · History
Implementation
From brand assets to a production identity.
Company details
Set canonical organisation and contact information.
Visual identity
Upload logos and select supported theme values.
Application
Configure app name, favicon, PWA and portal identity.
Domain & email
Verify digital and communication identities.
Documents
Set document branding and required company details.
Preview & publish
Validate major touchpoints before activation.
Choose the level of control
Branding changes identity. Headless changes the entire interface.
FAQs
Branding & Custom Domain FAQs.
What can I customise in Hamiltonn Cloud?
Supported branding can include company identity, logos, colours, custom domains, application identity, email branding, documents, portals and PWA settings.
Can I use my own domain?
Yes. Supported deployments can use customer-controlled domains or subdomains after domain verification and technical configuration.
Can the installed PWA use my company identity?
Yes, where PWA functionality is available. Supported tenant-specific app names, icons and theme settings can be applied to the installed experience.
Can emails come from my own domain?
Customer sending domains can be supported after the required domain and email authentication configuration is completed.
Can documents use my branding?
Yes. Where Hamiltonn generates documents such as quotations, invoices, statements or reports, supported templates can apply customer-specific branding and company information.
Can an agency manage different brands for different clients?
Yes. Agency and reseller models are designed to support distinct client environments and branding beneath the partner relationship.
Can I redesign the entire Hamiltonn UI?
Managed White Label uses Hamiltonn's supported interface and branding system. For complete frontend control, use the Headless/API model.
Can I claim any domain I want?
No. Customer domains must be verified before activation, and customers must have appropriate rights to the brand assets and domains they provide.
Make the platform unmistakably yours.
Bring your company identity, domain and customer experience into Hamiltonn Cloud through a structured white-label branding system.