Msty review

Msty is a multi-product AI workspace, not a single hosted model API or a library. Studio is a desktop workspace for chatting with local and online models, organizing knowledge, creating media, and reusing prompts. Studio Aurum adds Studio Web. Go provides bounded agent workflows through desktop or mobile. Nexus is described as a local AI control center for managing model runtimes, providers, keys, policies, app tokens, and usage. Stack is a knowledge layer for packaging approved sources into versioned Knowledge Stacks; the product is marked coming soon, while its team and enterprise plans are listed.

In a stack, Msty sits between users and their models, workflows, and approved knowledge. It aims to consolidate model choice and work context, rather than replace model providers. Teams considering it as infrastructure should distinguish the desktop workspace from Nexus's gateway role and Stack's planned retrieval layer, then verify which components fit their deployment.

The integration surface named by Msty is Nexus's API-first access, app tokens, and model-provider connections. Stack is described as accessible to approved AI apps, and Go lists Discord, Telegram, and WhatsApp integrations. The product pages also link to Studio, Go, and Nexus documentation for setup and guidance. Before building a client, confirm supported API protocols, SDKs, and programming languages in those docs; the vendor's product descriptions do not establish those details.

Nexus's stated controls cover runtimes, providers, keys, policies, app tokens, and usage, which makes it the product to investigate for centralized model access. The homepage does not name a CLI, REST interface, webhook contract, or plugin system, so do not assume those are available. Ask the vendor for endpoint documentation, authentication flows, versioning, error behavior, and examples in your language. For Stack, confirm how approved apps retrieve Knowledge Stacks and whether access is synchronous or otherwise exposed.

Studio Free costs $0 and includes core Studio Desktop features, local and online model chat, Persona and Crew Conversations, Agent Mode, and Knowledge Stacks. Studio Aurum is $149 per user, billed yearly, equivalent to $12.42 per user per month; it adds Studio Web, Azure and Bedrock providers, Studio Assistants, Forge Mode, and power-user features. A one-time Aurum Lifetime option is $349 per user. Studio Enterprise & Teams is custom-priced and requires at least five seats.

Go Free is also $0, with beta agent workflows, local or online models, messaging integrations, shortcuts, Memory Bank, Playbooks, and tasks. Go Teams and Go Enterprise are listed as planned and custom-priced. Nexus Preview pricing is not published; Stack Teams, Stack Enterprise, and the Enterprise Bundle are custom-priced. Msty does not publish request, compute, or overage rates in the listed plans. Ask whether model-provider charges are separate, and how usage is metered, before estimating production costs.

Msty does not publish an open-source license in its product and pricing information, so treat it as proprietary unless the vendor confirms otherwise. Studio supports local models, and Nexus is described as a local AI control center; those capabilities do not establish that the full Msty stack can be self-hosted. The vendor lists customer-controlled storage as a governance control, but does not publish deployment requirements or data-export formats here.

Ask how to export chats, prompts, agent workflows, audit logs, and Knowledge Stacks, and whether exports retain version history and permissions. Migration difficulty will depend on how much work relies on Msty-specific personas, agent workflows, and knowledge packaging. If a project depends on Nexus policies or Stack retrieval, confirm the available export path and replacement options before storing long-lived business context there.

Msty lists useful governance controls: SSO and team access, model and feature controls, administrative audit logs, customer-controlled storage, and a DPA. Studio Enterprise & Teams includes SSO integrations, role-based access control, user and team management, audit logs, and shared team resources. The vendor says formal SOC 2 and ISO 27001 certification is not yet complete, so regulated buyers should assess their own requirements and ask for current security documentation.

The published plan information does not include API rate limits, service-level commitments, availability targets, retention periods, or usage overages. Nexus is in preview and Stack is marked coming soon, so confirm production availability and support scope rather than designing around roadmap features. Ask how online model-provider failures, credential rotation, audit-log retention, and usage limits are handled. The listed custom pricing for team and enterprise products also means costs at scale require a vendor quote.