Catalyst AppSail — persistent backend PaaS with managed runtimes (Node.js, Java, Python) and custom Docker containers. Trigger on 'AppSail', 'persistent server', 'Docker on Catalyst', 'X_ZOHO_CATALYST_LISTEN_PORT', or 'long-running process on Catalyst'. Do NOT use for stateless request/response hand

How It Works 1. Identify the runtime — Managed runtime (Node.js, Java, Python) or custom Docker container. 2. Load references/appsail basics.md — for PORT config, environment variables, Dockerfile requirements, and deploy commands. 3. PORT rule — Always use process.env.X ZOHO CATALYST LISTEN PORT , never hardcode PORT or 3000 . 4. AppSail vs Functions decision — If the user is unsure which to use, apply this matrix: Catalyst Functions AppSail Code structure Catalyst specific templates required Any framework, any format, fully independent Use case HTTP handlers, events, cron, Zoho integrations Persistent servers, long running processes, Docker Billing Per API call Per instance uptime Dependency management Handled by Catalyst You manage all libraries and frameworks Triggers Use this skill for: "AppSail", "persistent server", "Docker on Catalyst", "backend hosting", X ZOHO CATALYST LISTEN PORT , appsail:add , "catalyst managed runtime", "deploy Express app", "AppSail vs Functions", "long running process on Catalyst", or "containerized app on Catalyst". References Reference Load when the query is about… references/appsail basics.md Runtimes, project structure, app config.json fields, Node.js/Docker templates, SDK version references/appsail deploy.md Deployment commands (Path A/B/C), env variables, health checks, AppSail URL pattern, configurations references/appsail crossorigin.md Slate + AppSail cross origin errors, CORS setup via MCP, catalyst auth , custom domain SSL

catalyst-appsail