psai

psai is an interactive music engine for videogame projects, with its clearest fit in Unity teams building scores that react to play. It is strongest when a team wants adaptive playback without adding a native-code layer to its Unity integration; its separate authoring editor and commercial-use terms need consideration.

Overview

psai gives game composers and developers a way to make playback respond to gameplay, including changes in intensity, recombination of musical segments, pauses and gameplay-driven logic. That focus makes it a specialist choice for interactive soundtracks, not a broad audio toolkit.

The regular and Pro editions share the same Unity engine. Pro adds access to the standalone editor for creating psai projects from scratch, and editor use requires Pro User Registration. A demo soundtrack and eight free music themes offer material to work with, but do not replace Pro for creating new projects.

Key features

• Adaptive playback: Intensity control and automatic musical-segment recombination can make a score track changing game conditions. This is the main reason to choose psai over a playback-only approach.
• Unity integration: The engine is written in C# without native code, and the maker says it works on all Unity target platforms. That is useful for Unity teams seeking one integration across their target builds.
• Native C++ SDK: The native version is for Windows only; interested users are asked to contact the maker about evaluation or licensing. It is not the cross-platform route offered by the Unity integration.
• Source and documentation: Customers receive the full source code; the FAQ identifies the .NET Google protobuf implementation as the only internally referenced DLL. A manual, API documentation, tutorials, a Unity forum and technical-support email provide routes to assistance, though the posted Unity Asset Store EULA commits to support only under a separate agreement.

Pricing

The free plan keeps the shared Unity engine available across projects, but does not provide the standalone editor for creating projects from scratch. The editor’s EULA also limits users who did not purchase the engine through the Unity Asset Store to non-commercial use, while allowing unlimited testing for future commercial use. Teams planning commercial editor work should resolve that distinction before adopting the authoring workflow.

Platforms

psai integrates with Unity, whose C# engine the maker says works on all Unity target platforms. Its standalone Unity Edition editor is offered for Windows and Mac and requires Pro. The native C++ SDK is limited to Windows. These are distinct routes: Unity projects have the wider stated target reach, while native integration is Windows-only.

Who it's for

psai suits videogame composers and developers building adaptive interactive soundtracks in Unity, especially when they value a C# implementation without native code and can use the existing engine at no further cost or royalties. It is a weaker fit for teams that need to create projects from scratch without Pro, need a native SDK beyond Windows, or require guaranteed support without a separate agreement.

Pros and cons

• Pro: The regular and Pro versions share the Unity engine, and Unity use across projects carries no further costs or royalties.
• Pro: Intensity control, segment recombination, pausing and gameplay logic give composers several ways to make music respond to play.
• Con: Creating projects from scratch requires Pro, so the free engine alone is not a complete authoring path.
• Con: The editor’s non-commercial restriction applies to users who did not buy through the Unity Asset Store, complicating commercial workflows.
• Con: The native C++ SDK is Windows-only, and support under the Unity Asset Store EULA depends on a special agreement.

Alternatives

For a wider comparison, browse Game Audio Middleware.

• Audiokinetic Wwise is worth considering if its free Indie plan’s stated game-production budget limit of less than $250K, unlimited sound files and per-title license suit your project.
• Reactional Engine offers a free plan with forum and Discord support, but requires a Reactional splash screen; consider it if those terms suit your team.
• Amplitude Audio SDK is a free, open-source option under Apache-2.0; choose it if that licensing model matters more than psai’s dedicated Unity authoring route.
• OpenAL Soft is a free LGPL-licensed implementation of the OpenAL 3D audio API; consider it for that API rather than psai’s interactive-music focus.
• SoLoud is free for commercial use, modification and redistribution under the ZLib/LibPNG license; it may suit teams prioritizing those permissions.
• Steam Audio SDK is available free to all developers under a license agreement; consider it if that broad free availability fits your needs.
• Unity Version Control is a separate tool for version control, not a direct substitute for an interactive music engine.
• FMOD Studio is another game-audio option; consider it if its per-game Indie licensing terms fit your project.

Verdict

Choose psai if you are composing or developing adaptive music for Unity and want a shared, no-royalty engine with gameplay-responsive playback. Look elsewhere if you need to author new projects without Pro, need a native SDK beyond Windows, or cannot work within the editor’s commercial-use conditions.