Does Kuroco have server redundancy?

Kuroco uses Google Cloud's features for redundancy (Google Kubernetes Engine, App Engine, Cloud Functions, Cloud SQL, Memorystore, Cloud Storage, Filestore, BigQuery, Pub/Sub, Cloud Scheduler, Google Cloud Armor, Cloud Logging, etc.). In addition, CDN is used as standard for API access from the front-end system.

Redundancy Configuration Diagram

The following diagram shows the configuration of the public SaaS version built in the Tokyo region (asia-northeast1). The Kuroco application runs on a GKE cluster and is made redundant across three zones.

For the configuration diagram of the private SaaS version built on AWS, see Is an on-premises version available?.

For more details, refer to the Kuroco infrastructure performance overview.

Reference

• Redundancy Configuration Diagram
  "Kuroco Infrastructure Performance Overview" material [7p] (public SaaS version), [8p] (private SaaS version)
  https://kuroco.app/files/sheets/ja/kuroco_infrastructure.pdf
• Response Flow When an Issue is Found
  "Kuroco Infrastructure Performance Overview" material [12p]
  https://kuroco.app/files/sheets/ja/kuroco_infrastructure.pdf
  Note: In case of a failure, if our company determines that notification to the entire company is necessary depending on the degree of impact, we will notify everyone by email or announce it on the support site.
• Contact information
  Support

Related documents

• Disaster Recovery (DR)
• Security
• Is an on-premises version available?
• Support