Functions
Serverless code. There are function types triggered by an HTTP request, an event, a scheduled job or a Zoho service event. Written in Node.js, Java and Python; you do not set up a server to publish an endpoint.
Zoho Catalyst is the Zoho cloud platform that brings serverless functions, application hosting, database, file storage, identity management and AI services together in a single console. Work that cannot be solved with CRM, Desk or Books settings and with Deluge is written here in your own code; managing servers, operating systems and scaling does not stay with you. The structure you build runs under an organization tied to your Zoho account.
DEVELOPER PLATFORM
Zoho Catalyst brings serverless functions, application hosting, database, file storage, identity management and AI services together in a single console. Setting up servers, maintaining operating systems and managing scaling does not stay with you.
Catalyst does not replace a ready-made Zoho application. It is the layer where work that cannot be solved with the application's own settings or with Deluge runs in its own code. The structure you build lives under an organization tied to your Zoho account; development and production are separate environments.
PLATFORM
The following are the platform's own components. A project never opens all of them at once; as many as the work requires are picked, and the rest stay off.
Serverless code. There are function types triggered by an HTTP request, an event, a scheduled job or a Zoho service event. Written in Node.js, Java and Python; you do not set up a server to publish an endpoint.
Hosting a full application. A continuously running server comes up with Node.js, Java and Python runtimes or with your own Docker image. It runs for as long as it is up, not on demand.
Relational database. Tables, typed columns and a SQL-like query language called ZCQL. There is a role and permission layer per table; which operation an application user can perform is defined separately.
Schemaless table storage. For records in JSON form that need no fixed structure and are accessed by partition key. Preferred when relational queries and joins are not needed.
Object storage. Files such as images, PDFs and CSVs are kept in a bucket structure. Time-limited signed links can be generated for upload and download, so the file is shared directly without passing through the server.
In-memory key-value store. For session information, temporary tokens and short-lived state. Records have a lifetime and drop on their own when it expires.
User and session management. Sign-up, sign-in, session verification and sign-out flows; a hosted sign-in screen or your own interface. Social sign-ins and working with external identity providers are supported.
OAuth token management for external services. The authorization of calls going to Zoho applications or third-party APIs is kept here; token refresh is not left to the code side.
Event bus. An event that occurs at a publisher passes through filtering and transformation and is delivered to a webhook, a function or a flow. Its configuration is handled from the console.
Scheduled and queued jobs. Tasks that run at set intervals, batch jobs and the background queue are managed from here; the scheduled function type does the same job.
Ready-made AI endpoints: text extraction from documents with OCR, text analysis, object detection, barcode reading, face analysis and content moderation. With QuickML a prediction model can be trained on your own data; the LLM Serving section of the console lets you call language models hosted on the platform. Some of these services vary by data center.
Headless browser and document generation. You connect to a remote browser running in the cloud; PDFs and screenshots are produced from HTML, a URL or a template. Browser automation and data collection components are here as well.
Front-end hosting. Interfaces written with frameworks such as React, Next.js, Vue, Angular, Svelte and Astro are taken live through a Git connection, and preview deployments are produced.
Official SDKs for Node.js, Python, Java, web browser, Android, iOS and Flutter. Linking a project, running locally and deploying are done with the Zoho Catalyst command line tool.
USAGE
Catalyst does not replace a ready-made Zoho application. It is the layer where work that cannot be solved with the application's settings or with Deluge runs in its own code. The typical types of use are these.
An event on the CRM, Desk or Books side calls a Zoho Catalyst function. Calculation and decision logic that needs an external library, runs long or does not fit within in-app code limits runs on the platform side and returns its result to the Zoho record.
A two-way bridge between Zoho and an external ERP, accounting service, payment provider or marketplace. Authorization is kept through Connections, field mapping and the retry queue on the platform.
Overnight reconciliation, regular data sync, scanning of expired records, sending reminders. Scheduled jobs and queue management come from the platform's own components.
Documents such as quotes, reports, contracts and form output are converted to PDF from HTML or a template. The generated file is stored in object storage and shared with a time-limited signed link.
A custom widget or tab that opens inside the Zoho interface. Hosting the screen is on the Slate side, the data and logic behind it live in functions and the database; the user never leaves Zoho.
Pages that customers, dealers or employees sign in to. User management is on Authentication, file exchange on object storage, page hosting on Slate; Zoho data is connected through the API.
Processing an uploaded file, converting it to text with OCR, classifying it and attaching the result to the relevant record. Steps are triggered by events, state is kept in the database, and the job is retried on error.
HOW WE WORK
The steps are the same in every project; the scope becomes clear in the written proposal after discovery.
Your existing Zoho setup and the process are reviewed. Whether the work is solved with the application's own settings, with Deluge or with code in Zoho Catalyst is decided here. Moving everything to code is not the goal.
Which component will be used is put in writing: will the data be relational or schemaless, will the work call for a serverless function or a continuous server, where will files be stored, how will identity be resolved, which event will trigger what.
The organization and project are linked, and the development environment is brought up. Tables, buckets and cache segments are defined; access permissions, authorized domains and cross-origin settings are made.
Code is deployed to the development environment and tried there. Environment variables, function security rules, API gateway routes and rate limits settle into place at this stage.
Once validation is done, the structure is moved to the production environment. Production is a separate environment: it carries its own credentials and its own environment variables, social sign-in and domain mapping are done again, and billing must be enabled. That is why promotion is not a one-click copy but a step run with a checklist.
After release, logs, alerts and performance monitoring stay on. Subsequent changes are again made in the development environment, tried, then moved to production; nothing is written directly to live.
The Zoho Catalyst decision is made not out of a wish to write code but where the work does not fit the ready-made settings. The examples below show that limit.
PROBLEM
Application documents arrive as email attachments; each file is opened and read by hand and attached to the relevant record one by one. A missing document is only noticed at the next step.
SOLUTION
The uploaded file lands in object storage and a function is triggered. Text is extracted with optical character recognition, the document is classified by type and attached to the relevant Zoho record; on error, the job is retried from the queue.
PROBLEM
Matching between the order record on the Zoho side and the marketplace and shipping services is done by hand. When a service does not respond, the transaction is left half done and nobody notices.
SOLUTION
A bridge is built between the two sides: authorization is kept in connections, field mapping and the retry queue run on the platform. A scheduled job reconciles, and a record that does not match lands as an alert.
PROBLEM
The quote output does not fit the ready-made template; the team prepares the document outside and uploads it back into the system. Which version was sent cannot be tracked.
SOLUTION
The document is generated from a template, stored in object storage and shared with a time-limited signed link. The button that starts generation sits inside the Zoho screen, and the user does not leave the interface.
1
At the same table as your team in Istanbul, remotely in other cities and abroad; with real data.
2
Every structure we build is in your hands, in writing.
3
Watch-and-apply recordings for every screen.
4
Quick answers to anything left unclear after training.
5
Is the team actually using the system? We measure it.
Every company whose setup we did gets base support through three channels after go-live; it is part of our responsibility and is not priced separately. The WhatsApp channel and phone stay open for as long as we are your partner; feature and customization requests by email in the first 6 months are part of the setup, while new modules and integrations are priced separately.
01 · Email
First 6 months after go-live, for your existing setup. Write to us; the request is logged and planned.
02 · WhatsApp channel
A channel set up for your company, open for as long as we are your partner. Your team asks, small fixes happen on the spot.
03 · Phone
Open for as long as we are your partner. When something stops work or management needs an answer, call us directly.
Coverage
WhatsApp channel and phone
Email · features and customization
After go-live, for every company whose setup we did. None of the three channels is priced separately; the 6-month scope covers feature and customization requests.
Managing a healthcare group with seven branches, the hardest part was seeing the whole picture. Each branch kept its own records and the same patient's data lived in different places. Two and a half years ago we moved to Zoho CRM with our Zoho Authorized Partner İsa Demirci and his team, and that picture changed. Today all seven branches run on a single system. I follow the entire group from one screen, while branches and teams see only their own areas through role-based permissions. The question of what a patient experienced at which branch is now answered by the system itself, not by phone traffic. Two and a half years is not a short time. The system has run reliably throughout, and whenever we needed him, İsa Bey was always reachable. We wholeheartedly recommend them to any multi-site healthcare organisation.
In health tourism the patient journey is long and has many steps: the first message, the assessment, the quote, travel, treatment day and the follow-ups after it. Working with Eksenium, we did not have to explain this journey to them from scratch. Without us telling them, they knew which information must not get lost at which stage, and where patients wait and where they drop off; our conversations were always about the details of our own business.
Eksenium is one of Zoho's Authorized Partners in Türkiye. You can see our listing, certifications and client reviews in Zoho's partner directory.
Our listing in the Zoho partner directory



Brands that trust us













We build it, improve it, keep it alive.
No system stays standing without someone behind it. We stay with every structure we build after delivery: monitoring, fine-tuning, and making sure your team truly adopts it.
Let's talk through your current process and assess together what Zoho would bring to your business. No sales pressure. A written proposal within 48 hours.
More questions? Write to us · we reply within 24 hours.
No. Zoho Catalyst is not a ready-made application but Zoho's developer platform. It does not come with an interface you open and use like CRM or Desk; you define what it does. Serverless code, application hosting, database, file storage, identity management and AI services are gathered in a single console. If the application's own settings or Deluge are enough, there is no need for Catalyst; Catalyst is for work that goes beyond that limit.
30+
projects
99%
client satisfaction
3 channels
post-implementation support
We prepare a concrete proposal and a live demo based on your current system, your goals, and your timeline. No commitment before the contract.