Capabilities
Pro-code, cloud-powered platform providing Function-as-a-Service (FaaS) and Platform-as-a-Service (PaaS) for building scalable serverless applications. Services include Authentication, DataStore (relational), NoSQL (announced August 2025), Stratus (object storage), Functions, Events & job scheduling, AppSail (container hosting), static hosting, AI/ML services (object detection, prediction models), CLI, and real-time monitoring. Auto-scaling infrastructure. ([Catalyst serverless docs](https://docs.catalyst.zoho.com/en/serverless/getting-started/introduction/))
Key integrations
All Zoho apps via APIs, Zoho Creator, any REST endpoint
Platform availability
The table below records native platform support as of April 2026, per the master reference. A denotes an officially shipped native app or supported surface; a denotes that the platform is either unsupported or that status is not disclosed.
| Platform | Native app |
|---|---|
| Web | |
| iOS | |
| Android | |
| iPadOS | |
| Android Tablet | |
| macOS | |
| Windows |
Source note
[Catalyst docs](https://docs.catalyst.zoho.com/en/serverless/getting-started/introduction/); [Catalyst blog](https://catalyst.zoho.com/blog/blog/Catalyst_NoSql_data_storage.html).
Where Zoho Catalyst shows up in the rest of the Encyclopedia
The encyclopedia indexes references to Zoho Catalyst across the 112 chapters and 681-entry feature atlas. Jump to the full passage for context.
- Catalyst and Creator hybrid patternsCreator integrations and extensibilitycreator
Catalyst and Creator hybrid patterns are architectures that combine Creator's low-code app layer with Zoho Catalyst serverless functions, storage, or backend services for heavier custom development. Within Creator integrations and extensibility, it is most useful when it validates how Creator becomes the custom app layer around CRM, finance, ERP, payment gateways, mobile SDKs, and external APIs. Poorly designed use of this feature usually appears later as bad reports, hidden manual work, duplicate data, or brittle automation. For adoption, document Catalyst and Creator hybrid patterns in the words users use, not only the words administrators use. Train the relevant roles on what changes for them, then document owner, edition dependency, data inputs, downstream reports, and change-control path; additionally, add an acceptance test and a monitoring or review mechanism. Source anchors: creator_features (https://www.zoho.com/creator/features/).
- Catalyst SignalsZia Agents platformai
Catalyst Signals are eventing or signal-style patterns from Zoho Catalyst used to notify applications or agents that something occurred and downstream handling is needed. Within Zia Agents platform, it is most useful when it protects agent building blocks: instructions, knowledge, tools, guardrails, identity, deployment, testing, logs, costs, and change management. Poorly designed use of this feature usually appears later as bad reports, hidden manual work, duplicate data, or brittle automation. For governance, Catalyst Signals should have a named steward and a small regression test. The steward should test trigger criteria, recursion prevention, failure handling, and log visibility; they should also treat generated or predicted output as assisted judgment unless an approval gate explicitly makes it autonomous. This prevents the feature from becoming invisible configuration that only one administrator understands. Source anchors: zia_agents (https://www.zoho.com/agents/), zia_agent_studio (https://www.zoho.com/agents/create-agents.html), zia_crm (https://help.zoho.com/portal/en/kb/crm/zia-artificial-intelligence/nextgen-agentic-ai/articles/zia-agents-in-zoho-crm).