ioMarket is where you extend ioMoVo. The Marketplace tab holds integrations and add ons: storage back ends, AI services, translation, transcription, publishing destinations, and more.
How the catalog is grouped
Integrations are grouped by where they attach. Some belong to ioCloud, the content ioMoVo stores itself. Others belong to ioHub, which is how ioMoVo reaches systems and storage you already own.
That grouping is a useful shortcut when you are hunting. If you are trying to connect something you already run, look under ioHub first.
Filtering
You can narrow the catalog by category. The current filters include Indexing, Translation, Transcription, AI, LLM, Publish, Drive, AWS, MS Azure, Google, and Oracle.
The provider filters (AWS, Azure, Google, Oracle) are the quickest route when you already know which cloud you are standardized on and just want to see what attaches to it.
Before you enable something
Two things worth settling first:
Credentials. Most integrations need an account and a key on the other side. Have that ready, and decide who owns it, because a personal key on a production integration becomes a problem the day that person leaves
Cost. Services that process content per asset, such as transcription or translation, bill against your own account. Understand what a full library pass will cost before you run one
The other two tabs
Playbook Marketplace offers prepackaged domain taxonomy and knowledge you can switch on instead of building from scratch. Asset Marketplace offers licensed stock content, with royalty free, rights managed, and Creative Commons licensing clearly marked. Check the licensing on any asset before you use it in a client deliverable.
If something you need is not listed
Check whether it exposes a standard interface first. An S3 compatible storage endpoint, for example, does not need its own listing. Beyond that, ioMoVo has an API, so a bespoke connection is usually possible. Tell your ioMoVo contact what you are trying to connect and why.