AI Character Vendors That Shut Down: How to Protect Your Game

Hume is switching off its EVI and TTS APIs, and the account data behind them is deleted once access ends. Any game that gives a character a voice through Hume has weeks, not months, to move. It is the latest in a run of AI character and voice vendor shutdowns.

Hume is not an outlier. Since 2024, a string of AI character and voice vendors have shut down, pivoted or retired the tools game developers built on, while the games using them were still in production. Games take years to make. AI vendors can change course in a quarter. This post lays out what happened, what a shutdown actually costs a team, and how to choose a platform that will not leave your game stranded.

AI character vendor shutdowns since 2024

Three patterns run through this list. Some companies ran out of money (Replica, Coqui, Soul Machines). Some found a more profitable market and left voice or characters behind (Resemble, and Inworld's move away from its no-code studio). And some were large companies trimming a side project (Meta's hosted Llama API). None of these vendors had games as their whole business when they changed course.

What a shutdown takes from a game team

The obvious loss is the API. The less obvious losses are the ones that hurt during production.

Generated audio you never exported. Replica users were told to download their files before the cutoff. Teams using Replica through third-party plugins reported losing in-progress voice work when the servers went dark.

Characters that only existed in the vendor's tool. A character defined in a hosted studio is a set of prompts, settings and knowledge files on someone else's servers. When Inworld retired Character Studio, those characters had to be rebuilt as Runtime templates in code.

Account data. Hume deletes account data after its APIs close. Voice settings, configs and logs go with it.

Your integration. SDK calls, callbacks, lip sync hooks and audio pipelines all assume one vendor's response format. Swapping vendors means rewriting the glue code, not just changing a URL.

Schedule. A forced migration lands in the middle of a milestone, not at a convenient moment. Every week spent rebuilding is a week not spent on the game.

Licence assumptions. Coqui's XTTS weights were usable commercially only with a licence Coqui sold. With the company gone, there is nobody to sell one.

Six questions before you choose a vendor

Ask these before you commit a character, a voice or a release date to any platform.

1. Are games the core business? A vendor that serves games as one vertical among many is the first to drop it when another market pays more. Look at the docs: are there engine SDKs, sample scenes and game-specific features, or is the engine plugin an afterthought?
2. Can you keep a copy of your work? You should hold your voice samples, generated audio, knowledge documents and a written definition of each character in your own storage.
3. Is there an exit path? Can you prototype on local models, or move the backend onto your own infrastructure if the cloud service changes terms?
4. Does it cover more than one engine? If a character only exists inside one SDK, an engine change and a vendor change become the same problem.
5. Does it depend on another company's accounts? Platforms that require every player to sign up for a third-party account add a second point of failure between your game and its characters.
6. What does a shutdown notice look like? Read the terms for notice periods and data retention. Hume gave a fixed cutoff and deletes data after it.

How Neocortex answers them

Games are the whole product. We build AI characters for games: Unity (Unity 6, six sample scenes), Unreal Engine 5, Godot (beta) and a Web API you can call from any language.

Characters are data you can see. Every character is a visual graph of nodes: Agent, Personality, Emotion, Knowledge, World, Objects, Intents, Actions, Language, Accent and Voice. Knowledge comes from PDF and TXT files you upload and keep. Nothing important hides in a prompt only the vendor can read.

Your voice sources stay yours. Custom voices are cloned from a short sample you have the rights to, or designed from a text description. The source sample stays in your own storage.

Exit paths exist. You can prototype text chat with local models through Ollama in Unity, and self-hosting is available as a Custom (enterprise) arrangement for studios that need it.

No third-party player accounts. Players open your game and talk. Your plan pays for usage, and nobody else's sign-up screen stands between them and your characters.

One character, every engine. The same character works across Unity, Unreal, Godot and the Web API, so moving engines does not mean rebuilding your cast.

Moving off a vendor that is closing: five steps

1. Export everything today. Download generated audio, voice samples you own, knowledge documents, prompts and any conversation logs you are allowed to keep. Do this before the cutoff, not on the last day.
2. Write each character down. Capture personality, backstory, what they know, how they speak, and what they can do in the game. This document is the real asset, whatever platform comes next.
3. Rebuild the character as nodes. In Neocortex, the description goes into the Agent node, the setting into World, documents into Knowledge, and abilities into Intents and Actions. Pick or clone a voice in the Voice node.
4. Swap the integration. Replace the old SDK calls with the Neocortex Unity, Unreal or Godot SDK, or the Web API. Replies come back as lines with an emotion tag and named actions with a target, such as opening a specific door, which map onto most existing animation and gameplay hooks.
5. Test before you ship. Talk to each character in the browser editor first. In-editor testing never uses credits, so writers and designers can iterate as much as they need before the build changes.

Migration guides by vendor

• Inworld AI alternative
• Replica Studios alternative
• Hume EVI is shutting down
• Resemble AI alternative
• Coqui XTTS alternative
• Soul Machines alternative

Our recommendation

Treat every AI vendor as something that might change under you, and choose one where that change would hurt least. That means a platform built for games, characters you can read and rebuild, voice sources you own, more than one engine, and an exit path through local models or self-hosting. That is the platform we build. Start with one character on the free plan, test it in the browser, and bring it into your engine when it sounds right. Moving a larger project? Talk to us.

Details come from vendor documentation and public reporting, checked October 2026.

Frequently Asked Questions