Services
Custom domains for conglomerates and large enterprises, offered by invitation. BrandPort works with your existing application. It does not host the customer’s website.
Served from the nearest of 300+ edge locations worldwide.
Your app would be served from the edge location nearest each visitor, among 300+ edge locations worldwide.
Service lines
Domain white-label
Customers use your app on their own domain (for example erp.company.com), branded as theirs, at speed close to direct. BrandPort works with any web app, whether no-code, low-code or custom-built.
Firewall and traffic limits
Protection profiles (Standard, Strict, Government, and custom), fair-use limits, blocking of hosting-network traffic and fake bots, managed rules, human verification, and an “under attack” mode.
Add-on modules
A floating feedback button, ticketing, backups to cloud storage, and status and maintenance pages.
BrandPort for SaaS
SaaS companies offer custom domains to their own customers automatically, from inside their settings page.
Website and government firewall
Any organisation’s website behind BrandPort for caching, forms and protection.
What is true today
- Automatic HTTPS Certificates are issued for each customer domain.
- Customer-owned domain The customer keeps their own address.
- Every domain manually approved A domain goes live only after it is approved by hand.
- Zero-trust staff admin Staff admin access is locked behind zero-trust access.
- Global CDN BrandPort runs on a global CDN.
- 300+ edge locations worldwide Visitors are served from the nearest of 300+ edge locations worldwide.
How it compares on speed
Sample test from one test location, Nov 14, 2026
In this sample test, BrandPort matched the sample app served direct on page start, and served repeat app loads about twice as fast as a leading custom-domain proxy (0.37s vs 0.72s). These figures are from that test only and may differ in other regions.
| Host | Page start (warm) | App script, repeat |
|---|---|---|
| Sample app, direct | 0.40 | 0.64 |
| Sample app via BrandPort | 0.34–0.40 | 0.37 |
| A leading custom-domain proxy | 0.57–0.62 | 0.72 |
On repeat loads of the app script, BrandPort measured 0.37s against 0.72s for the other proxy, about twice as fast. BrandPort matches the sample app served direct on page start. These results are from one test location and may differ in other regions.
Times are in seconds, from a sample test at one test location, 14 November 2026.
Request a briefing
By invitation. Tell us which service you want to discuss.