TENRYU TEI — Home

SOFTWARE · VOICE · COMMUNICATION

Add to your productcommunication and intelligent voice.

For software companies, device makers, and teams that need custom work. We build real-time voice communication, AI speech systems, cross-platform updates, and ARM terminal software. Each project moves forward with a defined scope and acceptance criteria.

View the four services Discuss your project

Development and integration across platforms iOS Android Windows macOS Linux ARM Linux

WHAT WE BUILD

Four services, each aimed at a concrete development problem.

Commission a single module, or integrate with a product you already have. Platforms, features, and delivery scope are confirmed before work starts.

01

Real-time voice communication modules

Add voice calls and push-to-talk to an existing app, business system, or device, so different endpoints can connect in real time.

  • WebRTC
  • Push-to-talk
  • Multi-device access

Scope

Voice calls and session management, push-to-talk, device interoperability, network-state handling, and integration with existing accounts and business APIs.

Deliverables Communication modules for the agreed platforms, interface notes, an integration example, and joint-test records.
For team coordination, device intercom, and remote conversation

02

AI speech recognition and synthesis

Bring transcription, spoken text, and dialogue into a product. The approach follows the language, noise, and deployment conditions you actually have.

  • ASR / TTS
  • Audio noise reduction
  • LLM integration

Scope

On-device or cloud speech recognition, text-to-speech, Japanese voice assistants, audio preprocessing, and large-language-model integration. Offline operation is assessed on the target device.

Deliverables A working speech pipeline, calling interfaces, deployment notes, and an evaluation on the agreed samples.
For transcription, voice assistants, and interactive terminals

03

Updates to existing cross-platform software

Extend the code and product you already have: add voice features, fix audio problems, or adapt communication and system compatibility.

  • Mobile / desktop
  • Audio diagnosis
  • Protocol adaptation

Scope

Feature work on Windows, macOS, Linux, Android, and iOS; capture and playback fixes; protocol changes; and OS-version adaptation.

Deliverables Code changes within the agreed scope, builds for the target platforms, a change note, and regression records.
For product iteration, compatibility fixes, and multi-device expansion

04

Embedded ARM voice terminals

Port voice and communication software onto a specified ARM Linux device, and connect that terminal to upstream services.

  • ARM Linux
  • Driver adaptation
  • On-device optimization

Scope

Software porting, audio device and driver adaptation, speech-algorithm integration and performance work, remote communication, and service API connection. Hardware limits and whether a model can run are checked first.

Deliverables A build for the agreed hardware, deployment and startup notes, and device joint-test and performance records.
For smart speakers, intercom terminals, and voice devices

HOW WE WORK

Agree the scope, then validate and deliver.

Start from a goal that can be accepted. After we understand the current environment, the main problem, and the result you expect, we set the approach, the fee, and the delivery points.

You can start with a paid technical trial

When model results, device compatibility, or the communication approach are still uncertain, we can agree a small proof of concept first and use the test results to choose the development path.

  1. STEP 01

    Confirm the need and the environment

    The target features, existing systems, device conditions, and hoped-for timing.

  2. STEP 02

    Proposal and quote

    Development boundaries, deliverables, acceptance criteria, and a staged plan.

  3. STEP 03

    Build and integrate

    Work proceeds by the agreed milestones, checked on the target devices and real samples.

  4. STEP 04

    Accept and hand over

    Acceptance against the agreed criteria, handover of software and documents, and the support arrangement that follows.

A small proof of concept or a module can be planned over 2–6 weeks. The actual time depends on scope and dependencies. A full system is planned separately.

BEFORE WE START

Questions you may want answered before we start.

Can we commission only one module?

Yes. We can build a single voice, communication, or adaptation module, or integrate it into a system you already have. Interfaces, target platforms, and acceptance conditions need to be confirmed first.

How are fees and schedule set?

We estimate from the number of platforms, the feature scope, the state of existing code, and the test conditions. A clear request gets a project quote. If the scope is still unclear, a paid technical trial can come first. Fees, payment points, and timing follow the plan or contract both sides confirm.

Can AI speech and language models run locally?

Some can. It depends on the processor, memory, language, model license, and response-time requirements. On ARM devices especially, we test how it actually runs before choosing fully local, cloud, or a mix.

Do you hand over source code, and how is maintenance arranged?

The source handover, intellectual property, third-party licenses, and maintenance support are set in the contract. Different ways of working can have different delivery and support scopes.

LET’S DISCUSS YOUR PROJECT

Tell us the problem you are solving.

Whether the requirement is already clear, or you want to validate one technical approach first, you can write to us. The target platforms, the current problem, and the result you expect help us judge the development scope.

Japan TENRYU TEI Co., Ltd.
Japan · Naha, Okinawa
tenryutei.com/en/

“Consult by email” opens your mail app. You confirm sending. This page does not submit or store what you enter.