Private Deployment
Deploy the server in your own environment and point the client at it
Private Deployment
Transbox is a desktop client plus a server. Private deployment places the server on your own infrastructure while the client stays a desktop application — accounts, plans and online services simply point at your server.
The client is a Windows desktop application; there is no web client. Private deployment does not change that: staff still install the client, with the service address preset to your server.
Architecture
| Component | Description |
|---|---|
| Server | Website, registration and sign-in, plans and credits, admin console, bilingual documentation site |
| Client | Windows desktop app, connecting to your server via the service address |
| Data | Business data (projects, corpora, translations) stays in the client's local database; account and plan data lives on the server |
Differences from the public service
| Aspect | Public service | Private deployment |
|---|---|---|
| Accounts | Official server | Your own server |
| Plans and credits | Official plans | Defined and issued by you |
| Client connection | Built-in address | Preset or manually entered address |
| Business data | Local to the terminal | Local to the terminal (unchanged) |
| MT / LLM | Platform models + your own keys | Your own keys and models |
Server Requirements
Starting points — size them against concurrency and corpus volume:
- OS: Linux (Ubuntu 20.04+ / CentOS 7+, …) or Windows Server
- Runtime: Node.js plus a relational database (PostgreSQL by default, as with the official server)
- Network: clients must reach the server address; for intranet-only use, ensure the office network is routable
- Egress: if the server calls external MT/LLM APIs, allow those domains
What Gets Deployed
Server
- Site and account services (registration, sign-in, password reset)
- Plans, credits and entitlements
- Admin console (users, plans, announcements, tickets)
- Documentation site (Chinese and English)
Client
- Installer distribution (silent install available for mass deployment)
- Preset service address, so staff need no manual configuration
- Optionally preset MT credentials, custom models and seed corpora
Deployment Steps
1. Assessment
- Confirm user count, concurrency and whether dual internal/external access is needed
- Verify the server network can reach required external services
- Decide the account source (self-managed accounts, or integration with an existing identity system — the latter needs separate evaluation)
2. Build
- Prepare servers and the database
- Deploy the server application and initialise the database
- Configure the domain and HTTPS
- Complete base configuration with an admin account (plans, announcements)
3. Client Onboarding
- Enter the server address under Settings → Network & advanced → Online service
- Restart the client and sign in with an enterprise account
- Or ship a customized installer with the address already preset
4. Validation and Rollout
- Pilot: sign-in, translation, projects, corpora, backup
- Verify the MT and LLM paths (own keys or internal models)
- Distribute and train
Collaboration Model
With a private deployment, accounts and plans are managed by your server, while translation collaboration stays file-based: export XLIFF or Excel from a project, distribute it, and merge the returned work with Import translations.
Security Recommendations
- Transport: serve over HTTPS and enter an https address in the client
- Accounts: create separate accounts per team; avoid shared admin accounts
- Keys: MT and LLM credentials live on the terminal — use disk encryption and access control
- Backups: export client data regularly via Data backup; back up the server database per your policy
- Network: for intranet-only use, restrict sources at the firewall
Typical Scenarios
- Finance / healthcare / government: data and accounts stay in your environment, satisfying internal "no data leaves the intranet" requirements
- Large enterprises: unified accounts, plans and terminology standards
- Translation agencies: host client projects and corpora on your own server, delivering the client under your brand
Contact
- Email: transbox@yeah.net
- Please include: company size and business scope, existing IT infrastructure, network and compliance requirements, expected user count, whether identity integration is needed, and delivery date
We will provide a deployment plan, resource list and quote.