Branding Customization

For translation agencies, multinational teams and institutions, Transbox can be adapted to your brand and working conventions. Customization is performed by our implementation team as a dedicated build — it is not a switch inside the client.

What Can Be Customized

1. Identity

• Product name and icon: installed product name, desktop and tray icons
• Window and about information: title bar, brand and copyright on the About page
• Splash screen: logo and version information at launch

Colour scheme and theme follow the system light/dark setting; there is no separate colour-theme customization.

2. Default Configuration

• Default interface language: any of 简体中文, English, 繁體中文, 日本語, 한국어, Français, Deutsch, Español, Português, Italiano, Русский, Polski, Türkçe, Tiếng Việt, ไทย, Bahasa Indonesia
• Default service address: pre-pointed at your self-hosted server, so staff install and go
• Pre-configured engines: your MT provider credentials or custom models
• Pre-seeded corpora: ship standard memories and termbases with the installation via a prepared data backup
• Default shortcuts and selection behaviour: preset to avoid clashes with internal systems

3. Feature Scope

• Module visibility: hide unused sections (Chatbox, file tools, …)
• Capability switches: whether custom models or custom MT keys are allowed, controlled by plan and preset configuration

4. Installation and Updates

• Installer customization: setup text, default install path, shortcut names
• Silent install: unattended installation for mass deployment
• Update source: the official channel by default; switching to an internal update server is confirmed during implementation

Process

1. Requirements

1. Confirm usage scenarios, user count and deployment model (cloud service or self-hosted server)
2. Collect brand assets (logo, product name, copyright)
3. Agree the default configuration list (language, service address, corpora, shortcuts)
4. Agree which modules to hide or restrict

2. Build and Verify

1. Produce the customized build from the agreed list
2. Functional and compatibility testing, including proxy, private service address and silent install
3. Deliver a trial package for a small pilot group

3. Delivery and Support

1. Deliver the release installer and deployment notes
2. Administrator and end-user training
3. Agree the update cadence and support model

Typical Scenarios

• Translation agencies: deliver the tool under your own brand, with unified corpora and workflow
• Multinational enterprises: one internal tool with a private server and standard termbases preinstalled
• Government and institutions: intranet deployment, unified configuration, controlled updates
• Educational institutions: preset languages and corpora for teaching, with unrelated modules hidden

Notes

1. Copyright: the customized build remains Transbox's copyrighted work; the customer receives a licence within the agreed scope
2. Agreement: an enterprise licence is required, defining seats, scope of use and distribution
3. Updates: customized builds are released by us on the agreed cadence; customers should not swap core files themselves
4. Timeline: depends on the number of items and whether functional changes are needed — confirmed during the proposal stage
5. Data: customization does not change where data lives. Business data stays in the terminal's local database; with a private server, accounts and resources are managed server-side

Contact

• Business enquiries: transbox@yeah.net
• Please include: company profile and scenarios, brand assets, default configuration requirements, deployment model (cloud or private), expected user count and delivery date

We will respond with a proposal and quote after assessment.