Skip to main content
The Brand name and logo settings let you customize how your OASM instance is presented across the console. You can set the instance name and upload a logo so that the product reflects your organization instead of the default OASM branding. The settings live in the console under Settings → Brand name and logo.

​
Why branding matters

For many deployments, presenting the platform under your own identity is as important as the functionality itself:
  • Self-hosted deployments — Operators often deploy OASM for an internal security team. Setting the name and logo makes the instance feel like part of the organization’s tooling rather than an unconfigured default.
  • Multi-tenant instances — When the same instance serves several teams or departments, distinct branding clarifies which instance a user is looking at and reduces confusion between environments.
  • White-label setups — Managed security providers and consultancies can rebrand the console for their customers, presenting the platform under the provider’s own identity.
Branding is configuration, not customization of the codebase — no rebuild or redeploy of the application is required to change it.
When you run OASM on your own infrastructure, the default branding identifies the instance as OASM. Setting your organization’s name and logo makes the console immediately recognizable to your internal team and avoids confusion with any other instance you operate. See Deployment for the hosting options.
If the same deployment serves multiple teams, environments, or customer accounts, distinct branding per instance helps members tell which environment they are signed into at a glance — reducing the risk of acting on the wrong tenant.
Managed security providers and consultancies can present the platform under their own identity. Members and customers see your name and logo in the console chrome and on the login screen, while the underlying workspace and security data remain fully functional.

​
Update your branding

1

Open the branding settings

In the console, navigate to Settings → Brand name and logo.
2

Set the name

Enter your desired instance name in the Name field.
3

Upload a logo

Click Choose logo file and select an image from your computer. Supported formats are JPG, PNG, GIF, and WEBP.
4

Save

Click Save to apply the changes to the console.
Changes take effect immediately after saving. There is no restart or redeploy required — branding is applied from the console settings on the next load of the interface.
If you have not uploaded a logo yet, the console shows the empty state: “No logo uploaded yet. Supported formats: JPG, PNG, GIF, WEBP”. You can save a name without a logo and add the logo later using the same page.

​
Where your branding appears

Once saved, the name and logo appear throughout the console interface:
  • The name is shown in the console chrome (headers, titles, and other interface chrome).
  • The logo is displayed in the navigation, on the login screen, and in the browser tab.
Because branding applies to the whole console, choose a name and logo that are recognizable at small sizes — the logo in particular is shown at a small scale in the navigation.
The login screen uses the same branding as the rest of the console. When your members sign in, they see your name and logo rather than the default OASM branding — useful for making self-hosted or managed instances feel like part of your own tooling.
A little preparation goes a long way, because the logo is shown at small sizes in the navigation and browser tab:
  • Use a high-resolution source image so it stays sharp when scaled down.
  • Prefer a transparent background (PNG or WEBP) so the logo sits cleanly on any console theme.
  • Keep the design simple and legible at small sizes — avoid fine detail or thin text that blurs.
  • Check that the logo reads well on both light and dark themes.
Recommended workflow: export your logo as a transparent PNG (or WEBP), at a size that stays readable at the small navigation scale, and verify it against both light and dark themes before uploading.

​
Updating or removing branding later

Branding is not permanent — you can change it any time from the same page:
  • Change the name: edit the Name field and click Save.
  • Replace the logo: click Choose logo file and select a new image, then Save.
  • Remove the logo: clear the uploaded logo and Save. The console shows the empty state again (“No logo uploaded yet. Supported formats: JPG, PNG, GIF, WEBP”) until you upload a new one.
Branding changes apply to the whole console immediately after saving. No redeploy or restart is required.

​
Branding in context

The Brand name and logo settings are part of the workspace configuration in the console. They are a presentation layer on top of the platform:
  • Workspace settings control the functional configuration of your workspace — see Workspace.
  • Deployment determines where your instance runs, which is what most instances want to brand — see Deployment.
  • Branding itself is independent of your scan targets, assets, and findings; it only changes how the console looks.
This separation matters for multi-tenant and white-label scenarios: you can present the same platform under a different identity per customer or team without changing the underlying workspace configuration.
A managed security provider deploys OASM for a customer and wants the console to look like part of the customer’s own stack. They set the Name to the customer’s product name and upload the customer’s logo, then save. From then on, the customer’s team sees that name and logo in the console chrome, in the navigation, and on the login screen — with no code changes and no impact on the underlying workspace, targets, or findings.

​
Troubleshooting

Compress or re-export the image at a smaller size, then try again. Most modern image editors can export a web-optimized PNG or WEBP under 1 MB.
Only JPG, PNG, GIF, and WEBP are accepted. Re-export the image in one of these formats (for example, convert an SVG or BMP to PNG) and upload it again.
The browser may be serving a cached version of the console. Do a hard refresh (for example Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on macOS) to load the updated branding.
The console scales the logo down for the navigation and browser tab. Re-export the logo from a higher-resolution source and use a transparent PNG or WEBP for the sharpest result.
Yes. The Name field and the Logo upload are independent. Save the logo by itself, or the name by itself, in any combination.
Branding is a console-wide setting: the name and logo apply to the whole instance for all members. It is separate from per-user settings such as profile details and permissions.
No. Branding is stored as part of the console settings, so it survives application upgrades and restarts. You only need to re-upload a logo if the instance was reset or redeployed from a clean state.

Workspace

Manage workspace-level settings and configuration alongside branding

Deployment

Self-hosted deployment options where custom branding matters most