PRICING & DEPLOYMENT

A deployment model that fits your product.

From trial to delivery, define your environment, product scope, and expected scale before choosing an integration path.

ON-DEVICE

On-device SDK

Bring speech and translation to the device.

Evaluated by licensing and delivery scopeFor smart hardware, mobile apps, and offline interactions.
  • Select SDKs and models for your target platform
  • Request a trial license through your project
  • Download released, authorized resources
  • Verify device performance and model compatibility
Request an on-device trial
PRIVATE DEPLOYMENT

Private deployment

Deploy in an agreed environment with clear responsibilities.

Quoted by project and deployment scopeFor teams with defined network, environment, and operational needs.
  • Evaluate computing resources and network boundaries
  • Define integration scope and deployment topology
  • Agree on updates, monitoring, and operational ownership
  • Confirm delivery and support per project
Discuss deployment requirements

There is no published standard price or package allowance. Trial duration, resources, commercial licensing, fees, and support depend on approval and mutual agreement.

A CLEARER COMPARISON

Choose the path.Then plan the scale.

Compare the conditions that matter for integration.

Evaluation areaOn-device SDKCloud APIPrivate deployment
Runs onThe target deviceConfigured cloud inference servicesAn agreed deployment environment
Confirm firstDevice platform, memory, and model compatibilityNetwork, language pairs, and service authorizationCompute resources, network, and operational ownership
Delivery and integrationSDKs, models, and signed licensesAPI contracts and project credentialsDelivery within the agreed scope
Data flowConfirm actual SDK behaviorRequest text is sent to the inference providerConfirm against deployment topology and interfaces
Commercial assessmentLicensing scope and deliverablesService scope and request volumeDeployment scale and support scope
MAKE THE FIRST CONVERSATION COUNT

A useful conversation starts with these details.

You do not need a complete technical proposal. Describe how your product will be used, and we can narrow the choices together.

01

Product and platform

Device model, operating system, application type, and preferred integration method.

02

Languages and use cases

Languages to transcribe or translate, operating conditions, and the core experience.

03

Scale and boundaries

Expected device count or request volume, network conditions, and data requirements.

04

Timing and collaboration

Your validation and delivery timeline and technical point of contact.

A FEW GOOD QUESTIONS

Trials and fees.

Clear answers to key questions make the next step easier.

Discuss your requirements
01Can I purchase or top up online?

The platform currently supports projects, trial approval, licensing, and usage records. Online payments, top-ups, invoicing, and automatic billing are not available. For commercial service, please Contact sales to confirm the solution and contract scope.

02When can I start after requesting a trial?

Track approval in the console after submitting your request. Authorization is issued after approval; SDKs and models must also be published and available to your account. Confirm approval timing and resource availability with the technical or sales team.

03Are cloud usage records a bill?

No. Usage records show character counts and request statuses to help evaluate integration. Billing units, prices, periods, and settlement methods require a separate agreement.

04Can I combine offline and cloud capabilities?

Combined integration can be discussed during evaluation. Confirm licensing, data flows, and fallback behavior for each capability. Actual support depends on the delivered SDKs, models, and cloud services.

BUILD SOMETHING THAT MATTERS

Find the right way to integrate.

Start with your product requirements to set clear expectations for deployment, licensing, and delivery.

Discuss integration requirements