Vertical Studio Uptime SLA and Availability | Zoho Vertical Studio Help

Vertical Studio Uptime SLA and Availability

Vertical Studio is hosted on enterprise-grade infrastructure designed for reliability and continuous operation. Both your work in the Developer Console and your subscribers' apps running in their organizations operate under a 99.9% monthly availability guarantee. This commitment means your development environment and production deployments receive the same level of protection.
The underlying architecture features geographic redundancy, automated failover systems, and continuous monitoring. If infrastructure issues occur in one location, operations automatically shift to backup systems with no or minimal disruption. This design allows you to build and publish apps with confidence, knowing that service continuity is built into every layer of the platform.

Checking System Status

Real-time availability data is published at https://status.zoho.com/. Head over to this page and look for the component listed as Zoho platform. Both Vertical Studio and subscriber organizations operate under this component. You can filter data by time period to review historical performance and incidents. Use this information before scheduling critical deployments or subscriber upgrades.

The Availability Guarantee

The platform targets 100% uptime and guarantees a minimum of 99.9% monthly availability. Actual downtime, if any, will vary based on unforeseen incidents and is not expected to occur regularly.
When calculating availability, certain types of downtime do not count toward this calculation:
  1. Scheduled maintenance windows: System updates are announced at least 48 hours before they occur, giving you time to plan.
  2. External events beyond platform control: Network provider outages, natural disasters, coordinated attacks, or similar circumstances.
  3. Issues originating from your own systems: Problems with your hardware, software configurations, or network setup.

Infrastructure Design

The 99.9% availability target is supported by architectural choices designed to prevent and recover from failures:
  1. Multiple data centers: Infrastructure is distributed across geographically separated data centers. Each region has a primary data center that handles production traffic and a secondary that maintains a copy of all data.
  2. Automated failover: If the primary data center becomes unavailable, systems automatically switch to the secondary. This handoff requires no manual intervention and minimizes service interruption.
  3. Traffic distribution: Incoming requests are spread across multiple servers using load-balancing technology, preventing any single server from becoming a bottleneck.
  4. Active monitoring: Continuous system monitoring watches for performance degradation, errors, or infrastructure problems. Issues are detected and escalated to engineering teams within seconds.
  5. Data synchronization: Data changes in the primary data center are continuously replicated to the secondary, ensuring both locations maintain current information.

AI Services and Availability

If your packaged app includes AI-powered features like predictive scoring or text generation, those features are built as independent services that operate separately from the core platform. Each AI service has its own monitoring and can experience availability issues independent of the main system.
This isolation is intentional. If an AI service becomes unavailable, your app and your subscribers' workflows continue operating normally. They can create records, update data, and trigger automation without waiting for AI services to recover. The AI features become unavailable, but the app does not stop functioning. This architectural choice means reliability issues in one AI service do not cascade into failures elsewhere on the platform. The 99.9% availability target applies to the core platform. AI services add capabilities on top of that baseline and have their own health checks and monitoring.

Your App and Availability

The 99.9% availability guarantee covers both sides of your work as a developer - your development experience in the Developer Console and the runtime experience of your subscribers using your packaged app.
Vertical Studio Developer Console: When you create, test, and publish your packaged app, you work within an environment protected by the availability guarantee.
Subscriber organizations: When your subscribers install and run your app in their organizations, they receive the same level of protection.
Both environments rely on the same redundant data centers and failover systems. Any scheduled maintenance is announced 48 hours in advance and affects both your console access and subscriber operations across all data center regions. This means you can confidently build features and publish updates knowing that the platform supporting both development and production has predictable reliability characteristics.