Deployment and White-Label

Every firm on Bitment runs on its own dedicated environment (see Security and data for the infrastructure detail), reachable at its own subdomain and, if the firm wants it, wearing its own name and icon rather than Bitment's. This page covers what that setup looks like and what onboarding involves.

Where to find it

Your firm's environment is set up by the Bitment team as part of onboarding; there's no self-service stack creation inside the product today. The desktop app, if your firm uses it, is downloaded from a link the Bitment team gives you, or from your firm's own sign-in page.

Key concepts

Stack: the complete, isolated set of infrastructure serving one firm.
White-label branding: replacing Bitment's own name and icon with your firm's, wherever the product shows a name to a user.
Release line: the version history for one firm's desktop app, tracked independently of every other firm's.

Your firm's own subdomain

A firm's stack is reachable at <yourfirm>.bitment.co. Because every firm gets its own dedicated stack, this isn't a shared domain with routing underneath it: the subdomain points at that firm's own load balancer and application server, described in Security and data.

Bitment also keeps one stack of the identical design for its own internal testing. It is not a customer environment and holds no customer data.

White-label branding

A firm can have Bitment show up as its own product rather than as "Bitment":

The browser tab title, the installable app name (when a user adds Bitment to their home screen or desktop as a Progressive Web App), and the desktop app's own name and icon can all carry the firm's name and logo instead of Bitment's.
Branding is driven by the firm's name; the visible brand name can also be set separately from the internal name used in configuration, if a firm wants a different public-facing name than its internal label.
A firm that doesn't supply its own logo and icon set keeps Bitment's stock icons; the firm's name still applies to the visible text either way.

Desktop app downloads and updates

Each firm that uses the desktop app gets its own signed build, carrying that firm's own branding. It's downloadable from your firm's sign-in page or account dashboard.

The desktop app updates itself. When a new version is available, it's offered shortly after you open the app; choose to install and relaunch, or dismiss it and get offered again later. You can also check for updates on demand from the app's menu.
Most product improvements need no update at all. The desktop app loads the product from your firm's own server, so day-to-day feature changes are simply there the next time you open it. An update to the desktop app itself is only needed for changes to the app wrapper.
Each firm's desktop app carries its own version line, independent of every other firm's. Firms don't share a single release number; each stack's release history is its own.

What onboarding involves

Getting a new firm live on Bitment is handled by the Bitment team, not self-service:

The Bitment team provisions the firm's dedicated stack (its own isolated infrastructure, subdomain, and certificates).
They create the firm and its owner account.
They stage the firm's team members (created ahead of time, without needing an invite email sent immediately), who are then walked through activation once the firm is ready to go live.
They provision the credentials and connections the firm needs: AI provider credentials, and any third-party integrations (email, calendar, messaging, and so on) the firm wants connected from day one.
Optionally, they set up the firm's white-label branding and its desktop app release line.

If your firm needs a new environment, or changes to an existing one (a new integration, a branding update), that request goes to the Bitment team rather than being something a firm administrator configures directly today.