Private deployment

Translation that stays inside your environment

Run Bluente in a dedicated instance, your own cloud or entirely on-premise. Use models your institution has already approved while Bluente preserves the document around every translation.

Discuss private deployment Review security

No credit card required · Your first translation in minutes.

Trusted by teams at

Your models. Bluente’s document layer.

Add document intelligence to models you already trust

Your approved model handles language. Bluente handles the document around it: OCR, parsing, reading order, terminology, tables, clause numbering, reconstruction and quality checks. A 400-page scanned facility agreement comes back as a usable document, while the model and the content remain inside your chosen environment.

Runs against models you already host and have already cleared
Avoid introducing another general-purpose model solely for translation
Documents never cross the perimeter, and no outbound call carries their content
Hardened, minimal container images built to pass your scanning and provenance checks

Discuss private deployment

Your perimeteryour models

Docs in

→

Never leave

Built for the documents a bank actually moves

Credit and lending files

Credit proposals, facility agreements and counterparty financials out of Mandarin, Japanese and Korean — with the tables, footnotes and number formats intact for the analyst who has to spread them.

Onboarding and KYC packs

Certificates of incorporation, registers, board resolutions and beneficial-ownership evidence, arriving in whatever language and whatever scan quality the jurisdiction produced them in.

Fund and investor documents

Prospectuses, KIIDs, subscription documents, information memoranda and board packs, where a share-class fee table that shifts by one row is a distribution problem.

Corporate actions and trade finance

Corporate action notices, trust deeds, letters of credit and shipping documents — frequently faxed, photographed or scanned decades ago, and unreadable to text-first tools.

Regulatory submissions and policy

Filings and internal policy that must reach every regional entity in the wording the regulator already approved, not a fluent paraphrase of it.

Whatever the scan quality is

OCR recovers reading order and block geometry before anything is translated. Recognition is the first capability most private deployments drop; here it ships in every shape.

Security review, already documented

Give architecture, risk and procurement teams the evidence they need without reconstructing the service from sales material.

Architecture and processing

Service description, processing locations, data flows, retention controls and deployment diagrams — plus the compute, storage and network requirements for the option you choose.

Subprocessors, access and audit

The complete provider chain, contractual retention terms, access controls, audit rights and incident-notification provisions in a form your third-party risk team can review.

Deployment, updates and exit

Containerisation plan, security-scanning requirements, upgrade and rollback responsibilities, and the treatment of terminology, training material and tuned profiles when the service ends.

Choose the deployment that matches the rule

Start with the policy or client requirement that created the constraint. Then choose the lightest deployment that satisfies it.

Deployment	Where documents sit	Who operates it	The trade-off
Multi-tenant default	Our environment, region-pinned, isolated per workspace, auto-deleted within 24 hours	Bluente	None in capability. Full language set, every feature, updated continuously. Clears most outsourcing policies, and it is worth checking whether yours is one of them before you spend a quarter on the alternatives.
Single-tenant	A dedicated instance, isolated from other customers	Bluente	Higher cost. Updates arrive on an agreed schedule, which suits a change-control regime better than continuous release does.
Your own cloud	Your Azure or AWS tenancy. Documents never leave your account.	Shared	You carry infrastructure cost and an upgrade window, and it typically registers as material outsourcing. Feature coverage can lag the hosted product.
On-premise	Inside your network, no outbound connection required. Runs against your own hosted models.	You	The largest capability gap and the slowest to update. Right when a client mandate, a regulator or a group policy forbids everything above.

Scope the requirement before the infrastructure

The requirement is usually narrower than the request

Private deployment gets asked for when the actual clause covers one book of business or one document category — not the whole bank.

Splitting the workflow is faster to approve

Multi-tenant for the routine 90%, private for the sensitive tail. Cheaper to run, far easier to keep current, and a much shorter risk assessment.

Bring the clause, not the assumption

Outsourcing policy, client mandate or regulator's guidance — whichever created the requirement. Most of these end somewhere cheaper once the actual wording is on the table.

Four questions every private deployment should answer

Resolve these before architecture becomes a contract and a contract becomes infrastructure.

What exactly leaves the network?

Telemetry, licence checks and model updates all make outbound calls in some products. A deployment that is private for documents but chatty about metadata is a different product, and a different entry in your register. Ask what those calls contain, and get it in writing.

Which languages are actually available?

Private deployments generally run a subset of the hosted set. Ask for the pair list for the deployment you are buying — not the marketing list — and check it against the corridors your business actually trades in.

How do updates reach it, and who rolls them back?

Establish who initiates an upgrade, what the testing window is and what the rollback path is before signing. A continuous-release product dropped into a change-control regime is a problem you will own, not the vendor.

What does it cost to leave?

What happens to a tuned model, your training corpus and your glossary on exit. Your outsourcing policy almost certainly requires a documented exit plan — write it now, while you still have room to negotiate, not at renewal.

What does not change, whichever you pick

Format preservation

Tables, clause numbering, headers, footnotes and tracked changes survive identically in every deployment shape.

Your terminology

Defined terms, entity names and do-not-translate lists are enforced the same way regardless of where the software runs.

The reviewer stays

On anything filed, signed or distributed to investors, a bilingual review step remains part of the process. No deployment shape changes that.

Frequently asked questions

Can it run on the models we already host?

Yes, and for an institution that has already been through model governance it is usually the fastest path. We provide the document layer — parsing, OCR, terminology, reassembly and quality — and call the models you have already approved, where you already host them. Nothing new goes to your committee.

Is on-premise available today?

Yes. All four shapes ship: multi-tenant, single-tenant, your own cloud tenancy, and fully on-premise inside your network with no outbound connection required.

What do you give our third-party risk team?

Service description, processing locations, the full subcontracting chain including every model provider and the zero-retention terms we hold with each, audit rights, incident notification terms and exit provisions — in the form your register asks for. You remain the regulated entity; our job is to make your filing straightforward rather than archaeological.

Does it satisfy our outsourcing policy?

That is your assessment to make, and it depends which shape you choose and how your policy defines material outsourcing. What we can do is give your risk function everything it needs to make the call quickly, and tell you honestly where each option is likely to land.

How do people sign in?

Single sign-on via SAML or OIDC against your existing identity provider, with MFA for anyone outside SSO, role-based permissions, and audit logs covering uploads, downloads, administrative changes and retention events.

Can we start hosted and move later?

Yes, and it is usually the right sequence. Prove the output on your own credit files and scans first, then decide whether the sensitive tail genuinely needs to move.

What are the infrastructure requirements?

Stated per option — compute, memory, storage, and GPU where recognition-heavy workloads are in scope. Your infrastructure team gets the numbers, the architecture and infrastructure diagrams, the containerisation plan and the deployment playbook before the technical review rather than during it.

Does private deployment change pricing?

It can. It depends which shape you pick and who carries the infrastructure. Talk to our forward deployed team and they will work it through with you.

Keep the document where policy requires it

Bring the rule that created the constraint. We will design the deployment around it — and preserve the document around every translation.