Zoho Catalyst Serverless Guide 2027: Functions, AppSail and Use Cases

What is Zoho Catalyst?

Zoho Catalyst is a full-stack development platform that runs your code on Zoho's infrastructure without you managing servers. You write functions or deploy web services, and Catalyst handles hosting, scaling, logs and environments.

Each Catalyst project has a Development environment for building and testing and a Production environment for live use. Zoho's documentation says you need to add a payment method before deploying to Production. Catalyst offers a free monthly allowance with pay-as-you-go and subscription pricing beyond it, so check Zoho's Catalyst pricing page for current limits.

Which services does Zoho Catalyst include?

Catalyst covers compute, data, hosting, AI and DevOps. The table lists the services most relevant to business apps, using the names on Zoho's Catalyst site and documentation at the time of writing. The area labels are ours, for orientation.

Zoho's docs note that Integration functions are not currently available to users in the EU, AU, IN or CA data centers. Check availability for your data center before you design around any service.

When should you use Catalyst instead of Deluge or Zoho Creator?

Stay in Deluge when the logic belongs to one Zoho app and finishes quickly. Use Zoho Creator when people need forms, reports, approvals and a low-code app. Move to Catalyst when you need a real programming language, outside libraries, longer jobs, your own database tables or a public API.

We compare the three in detail in Zoho Creator vs Catalyst vs Flow, so here is the short version for Catalyst specifically.

• You need an npm, PyPI or Maven library, such as a PDF, image or encryption package.
• A job runs longer than a request-response script should, such as nightly reconciliation.
• You want a webhook endpoint that external systems call, with your own authentication rules.
• You process large files or batches that would hit Deluge statement or API limits.
• Your developers want version control, a CLI and separate test and live environments.

If none of these apply, Catalyst adds cost and skills you may not need. A well-written Deluge function is often the cheaper answer, as our Deluge scripting examples show.

What are typical Catalyst use cases with Zoho apps?

Most business uses fall into a few patterns, where Catalyst sits beside Zoho CRM, Books or Creator and does the heavy lifting.

A Deluge script in Zoho CRM can call a Catalyst Advanced I/O function over HTTPS to run logic the script cannot, then write the result back to the record. A Cron or job function can pull data from a supplier portal each night, clean it and push it into Zoho Inventory through its API. An AppSail service can host a small customer-facing web app that reads and writes Zoho CRM data. And Stratus can hold generated documents while a function links them to records.

• Webhook receiver: accept payment or shipping events from a third party, validate them, then update Zoho Books or Inventory.
• Data sync service: move records between Zoho and an ERP or database on a schedule, with retry logic you control.
• Document generation: create PDFs with SmartBrowz or a library and attach them to CRM records.
• AI step: classify or score records with QuickML or Zia Services before a CRM workflow acts on them.

How does Zoho Catalyst compare to AWS Lambda?

In concept they are close: both run your code on demand without you managing servers, and both bill on usage. AWS describes Lambda as a serverless compute service where you write a handler, connect it to a trigger from API Gateway, S3, SQS, EventBridge or many other AWS services, and pay per request and execution time.

The difference is the ecosystem. Lambda sits inside the very broad AWS platform, which suits teams already on AWS. Catalyst is smaller but sits next to Zoho apps, uses Zoho accounts and data centers, and bundles storage, auth, scheduling and hosting in one console.

Execution limits differ too. Zoho's Catalyst FAQ gives a 30-second limit for Basic I/O and Advanced I/O functions and 15 minutes for Event and Cron functions. AWS says Lambda event functions run up to 15 minutes per invocation by default. Long or heavy work on Catalyst often belongs in AppSail or job functions instead.

A practical rule: if most of the systems your code touches are Zoho apps, Catalyst keeps everything under one vendor, one login and one data center choice. If most of them are AWS services, Lambda is usually simpler. Mixed estates can use both, with each function living closest to the data it works on most.

What should you plan before you start a Catalyst project?

Plan ownership, environments and running costs before anyone writes code. Catalyst is a developer platform, so the business risk is less about features and more about who maintains the code once it is live.

Agree where the source code lives, who can deploy to Production, and how changes are tested in the Development environment first. Decide which Zoho data center the project runs in, because it should match where your Zoho apps and customer data sit. Then estimate usage: function calls, storage and scheduled jobs all count toward the free allowance and then toward paid usage.

• Name a technical owner and a backup for every Catalyst project.
• Keep secrets such as API keys out of code and in environment settings.
• Log every call to Zoho apps so failures can be traced and rerun.
• Review usage in the Catalyst console regularly so a looping function does not surprise you.
• Write a one-page runbook: what the service does, how to restart it, who to call.

How can Flowpeak help with a Catalyst project?

Flowpeak is a registered Zoho partner with Zoho-certified consultants. We decide with you whether the job needs Catalyst at all, then scope, build and document the functions and services on a fixed price in writing, paid by milestone, with 30 days of free fixes after go-live. See our Zoho Catalyst development service.

Frequently asked questions