What Happened to NeoSpeech?

For many IT teams, LMS administrators, and organisations running long-standing speech-enabled applications, NeoSpeech (opens in a new tab) is a familiar name. Its voices, including well-known ones like Julie and Paul, powered e-learning modules, IVR prompts, assistive tools and embedded systems for more than a decade.

Today, NeoSpeech no longer exists as a standalone provider. The technology behind it is still very much alive, but the brand itself has been folded into ReadSpeaker as part of a consolidation strategy.

If your organisation still relies on NeoSpeech or VoiceText voices, knowing how the transition unfolded—and where to find support now—is essential for long-term continuity.

A Quick Summary

• NeoSpeech was acquired under HOYA Corporation (opens in a new tab) as part of a broader speech-technology expansion.
• HOYA later consolidated NeoSpeech, VoiceText, Voiceware, rSpeak, and ReadSpeaker into one unified brand: ReadSpeaker.
• NeoSpeech.com now redirects to ReadSpeaker because ReadSpeaker is the official home of all former NeoSpeech technologies, voices, and support resources.
• In 2025, ReadSpeaker was acquired by Marunouchi Capital (opens in a new tab), strengthening long-term investment in neural TTS and enterprise deployments.
• Organisations still using NeoSpeech engines can migrate directly to ReadSpeaker’s modern neural TTS portfolio.

How It Happened: The Consolidation Timeline

2017: HOYA Enters Speech Technology

HOYA began its expansion into voice technology through a series of acquisitions that brought together the teams and assets behind NeoSpeech, VoiceText, Voiceware, rSpeak, and ReadSpeaker.

These acquisitions laid the foundation for a unified global TTS roadmap.

(Official press release: HOYA Corporation, July 2017 (opens in a new tab))

2019: One Brand, One TTS Portfolio

By 2019, HOYA formally consolidated its speech brands under a single identity: ReadSpeaker.

For customers, this meant:

• shared linguistic resources,
• unified engineering and voice development,
• consistent product strategy across all legacy brands.

NeoSpeech’s voice libraries, TTS engine, and language data were absorbed into ReadSpeaker’s development pipeline. The NeoSpeech name was retired, but the technology continued inside the broader ReadSpeaker portfolio.

(Industry reference: Speech Technology Magazine announcement, 2019 (opens in a new tab))

October 2025: ReadSpeaker Joins Marunouchi Capital

In 2025, ReadSpeaker was acquired by Marunouchi Capital.

The acquisition did not change the earlier NeoSpeech consolidation; instead, it strengthened the long-term investment outlook for:

• neural voice development,
• on-premise and embedded TTS,
• enterprise-grade deployments.

Why NeoSpeech.com Redirects to ReadSpeaker.com

NeoSpeech.com points to ReadSpeaker because ReadSpeaker is now responsible for all NeoSpeech support, licensing, and successor voice technology.

For organisations still searching for:

• NeoSpeech voice downloads
• pricing or upgrade paths
• VoiceText engine replacements
• documentation for older integrations

…the correct provider today is ReadSpeaker.

What This Means for Organisations Still Using NeoSpeech or VoiceText

Even though the brand no longer exists, many systems still run on older NeoSpeech engines. We regularly see this in:

• Adobe Captivate e-learning courses
• SAPI5-based applications
• legacy Windows environments
• embedded devices relying on VoiceText engines
• custom IVR and telephony systems built 10–15 years ago

Here’s how ReadSpeaker supports those environments today.

1. Modern Neural Replacements for NeoSpeech Voices

ReadSpeaker provides neural voices designed to maintain continuity with well-known NeoSpeech characteristics.

For example, organisations moving from the legacy “Julie” voice can adopt a modern neural successor that preserves tone and clarity while offering significantly more natural output.

Suitable for:

• LMS and e-learning workflows
• video narration and training content
• mobile apps (iOS, Android)
• accessibility tools and screen readers
• simulation and voice-driven interfaces

2. Migration Paths for Legacy Engines

ReadSpeaker supports organisations transitioning from NeoSpeech or VoiceText by helping with:

• mapping existing voice configurations,
• handling format differences (e.g., SAPI5 vs API-based synthesis),
• updating pipelines from desktop SDKs to cloud or server-based engines,
• enabling real-time synthesis where previously only batch output existed.

Teams inheriting older systems often find the migration process more straightforward than expected.

3. More Languages and Voice Options

NeoSpeech offered a relatively limited catalogue.

ReadSpeaker now provides 50+ languages and regional variants, including Neural Standard and Neural Premium voices that didn’t exist when NeoSpeech was active.

For global organisations, this means a consistent TTS provider across all regions.

4. Deployment Flexibility

One major benefit of the consolidated ReadSpeaker portfolio is the ability to deploy the same high-quality voices across:

• cloud and API-based environments,
• fully offline and embedded systems,
• secure on-premise servers,
• hybrid architectures,
• scenarios requiring ASR/TTS integration.

This is particularly important for regulated industries and environments that previously depended on NeoSpeech’s standalone engines.

5. Long-Term Continuity and Support

With ReadSpeaker’s expanded engineering roadmap — now backed by Marunouchi Capital — organisations gain continuity, stability, and the assurance that neural voice development will continue for years to come.

This is something NeoSpeech could not have provided independently.

Are NeoSpeech Voices Still Available?

Not under the NeoSpeech brand.

However, ReadSpeaker offers:

• neural successors inspired by legacy NeoSpeech voices
• voice preservation options for regulated workloads
• guidance for teams transitioning from ageing NeoSpeech TTS engines

The goal is continuity without compromising on modern quality standards.

FAQ

What happened to NeoSpeech?

NeoSpeech was acquired under HOYA and later consolidated into the ReadSpeaker brand.

Does NeoSpeech still exist?

No. Its technology now lives inside ReadSpeaker.

Why does NeoSpeech.com redirect to ReadSpeaker?

Because ReadSpeaker is the official successor and custodian of all NeoSpeech technologies.

Can I still get NeoSpeech voices?

Equivalent or enhanced neural voices from ReadSpeaker are available.

Can ReadSpeaker replace my NeoSpeech or VoiceText engine?

Yes — ReadSpeaker provides full migration support for legacy deployments.

Does ReadSpeaker support e-learning, voiceover, and mobile workflows?

Yes. These remain core use cases for the modern portfolio.

Ready to Move From NeoSpeech to a Modern TTS Platform?

NeoSpeech may no longer be available as a standalone product, but its technology continues inside ReadSpeaker’s TTS platform.

If your organisation still relies on NeoSpeech or VoiceText voices, we can help you plan a smooth migration and identify the best neural replacements for your workflows.

Talk to our team about the right TTS solution for your organisation.