Customer Spotlight: Jora AI

Before moving to Control Plane, Jora's entire infrastructure - AI automation scripts, back end, and front end - was hosted on Google Cloud Platform (GCP). The company had been using GCP since its earliest days, running everything in a single region.

The problem was that Jora's technology stack wasn't a great fit for the GCP services they were using. Jora's application is built on a Java framework that benefits from long-running processes, but GCP's simplest deployment option - Cloud Run - is designed for serverless, short-lived workloads. Jora was essentially using Cloud Run as a persistent server because the alternative - manually managing Kubernetes clusters through GCP - would have been a massive operational burden for a small team.

This mismatch meant Jora was paying more than they should have been for less performance than they needed.

Jora began migrating to Control Plane by first moving their development environment. Today, Jora runs its AI automation scripts, back end, and front end on Control Plane, while keeping its database on a managed service. Jora maintains a copy of the database in Canada for data sovereignty and another collocated with their Control Plane servers for low-latency performance.

Control Plane runs Kubernetes under the hood across multiple clouds and cloud regions, but abstracts away the complexity, giving Jora ideal infrastructure for a global app without the hassle of K8s management.

One of the deciding factors in choosing Control Plane was its native support for infrastructure as code. Unlike competitors that relied on community-maintained tooling, Control Plane offered an official, first-class way to define and manage infrastructure programmatically.

One of the most impactful benefits has been the elimination of GCP's complex permission and networking layers. On GCP, Jora had to manage granular service account permissions, API gateways, load balancers, and intricate networking definitions. Control Plane's Universal Cloud Identity abstracts all of that away.

Jora now manages only DNS settings and workload definitions. Networking, image management (Control Plane hosts Docker images at no extra cost), and identity management are handled by the platform. New team members find the system far more intuitive than GCP's sprawling configuration requirements.

The move to Control Plane has delivered significant cost savings for Jora. By properly matching their workload requirements to an infrastructure platform designed for long-running services, Jora reduced their cloud spend by approximately 60%.

More importantly, Jora is getting significantly more value for that lower price. On GCP, the team was constrained by Cloud Run's serverless model. On Control Plane, they run two persistent back-end instances with proper CPU scaling.

While Jora currently runs in a single region, the move to Control Plane has positioned them for effortless expansion when the time comes. Adding additional regions would require virtually zero configuration beyond enabling the new location - a capability that was a key factor in choosing the platform.

The multi-cloud architecture also provides resilience. If one cloud provider experiences an outage, Jora has the ability to shift workloads to another provider - a safety net that would have required significant engineering investment to build on GCP alone.