One Year On How Kaluza Scaled Their Jira Integrations with Getint

Over a year later, we’re circling back to see how that partnership has grown. The result? A story of scale, stability, and strategic alignment between Kaluza and Getint.

One Year On – How Kaluza Scaled Their Jira Integrations with Getint

Revisiting Kaluza’s Integration Journey

Over a year ago, Kaluza - a leading B2B energy platform - was at a pivotal moment. After moving to its own dedicated Jira instance, the company faced a critical need: maintain seamless collaboration with their sister company, still operating on a separate Jira system. This was the spark that began Kaluza’s search for a robust integration tool.

In our original case study, we chronicled Kaluza’s selection process, where they evaluated Exalate, Backbone, and Getint. Ultimately, Getint was chosen for its flexibility, ease of use, and no-strings-attached approach to partner integration.

Today, over a year later, we’re circling back to see how that partnership has grown. The result? A story of scale, stability, and strategic alignment between Kaluza and Getint.

connect jira issue page - jira data and jira software connector

About Kaluza: Powering the Future of Energy Management

Kaluza operates at the forefront of the energy transition, providing business-critical tools to manage electricity and gas for enterprises. Their platform helps clients visualize and regulate energy flows through applications and APIs, making Kaluza a key player in ensuring energy reliability across global markets.

Their clientele includes large enterprises in the energy sector - household names that, due to confidentiality, remain unnamed but represent some of the most demanding and regulated environments in the world.

For Kaluza, any integration must meet strict enterprise-grade standards - especially when it comes to security, uptime, and scalability.

jira integrations - connect jira issues with another jira project

The Initial Challenge: A Seamless Jira-to-Jira Connection

Kaluza’s original challenge was straightforward on paper but complex in execution: establish a two-way integration between their newly independent Jira instance and their sister company’s Jira environment. The solution needed to:

  • Ensure real-time synchronization of tickets, comments, and fields.
  • Maintain separate operational spaces - no unnecessary visibility across companies.
  • Be scalable for future needs, including integrating with additional platforms.

After testing multiple solutions, including Exalate and Backbone, Kaluza selected Getint for its:

  • Multi-platform capabilities: Support for Jira and beyond 
  • Centralized, user-friendly UI: No heavy scripting, no need for third-party installations.
  • Empowerment model: Allowing non-technical users to manage and configure integrations.

The Last Year: From One Connection to a Network of Integrations

Scaling Beyond the Pilot

The first Jira-to-Jira connection was just the beginning. Over the last year, Kaluza’s integration landscape has grown dramatically:

  1. Initial Phase: One project, one connection between Kaluza and its sister company.
  2. Scaling Phase: Multiple integrations rolled out across various third-party partners.
  3. Current State: A fully operational integration network with ongoing expansion.

Each new integration followed a refined process:

  • Discovery & Alignment: Renato, Kaluza’s IT Engineer, held alignment meetings with both internal teams and external partners to understand each side’s Jira setup - fields, workflows, permissions, and data sensitivity.
  • Test & Validate: Getint’s low-code platform enabled quick configuration and testing, typically taking a single day from setup to deployment.
  • Live Rollout: Once both parties approved the test runs, integrations went live - without disrupting day-to-day operations.
“What started as a single connection became a network. Requests from different teams kept coming in once they saw how smooth the process was,” Renato explains.
jira rest api integration - integrating jira with jira cloud and jira service management

Why Getint Continues to Deliver for Kaluza

1. Ease of Use Meets Enterprise Complexity

While Kaluza operates in a complex regulatory environment, Getint’s UI-first approach ensures integrations remain accessible to non-technical users. Renato highlights:

“I didn’t want to be the sole person managing integrations. With Getint, I can empower others to self-serve. It’s intuitive, flexible, and doesn’t require scripting.”

This contrasts sharply with competitors like Exalate, where Groovy scripting is often necessary, or Backbone, which lacked the flexibility Kaluza needed.

2. No Heavy Lifting for Third Parties

One of the original dealbreakers with other platforms was the requirement for third-party installations. Exalate, for example, needed a node installed on the partner's infrastructure.

Getint sidestepped this entirely:

“We didn’t want to ask our partners to install anything. With Getint, it’s all managed from our side, with secure API key access for external parties.”

This frictionless approach strengthened Kaluza’s relationships with their partners by reducing barriers to collaboration.

3. Security and Compliance Built-In

Operating in the energy sector means navigating stringent compliance and security reviews. Getint passed all of Kaluza’s internal audits, including legal, IT security, and compliance:

“When auditors ask how we manage third-party communication, we show them Getint. It’s secure, clear, and meets all our requirements.”

Security is enforced through API key-based authentication, allowing partners to revoke access at any time, maintaining data sovereignty.

4. Unshakeable Stability and Proactive Updates

Over the year, Getint has delivered 99.99% uptime with no disruptions - even during bi-weekly updates:

“We don’t even notice the updates except when new features appear. Nothing ever breaks.”

This seamless update process ensures that Kaluza’s integrations remain reliable and up-to-date, without introducing risk or downtime.

5. Support that Feels Personal

Getint’s support team has been instrumental in Kaluza’s integration success:

“Support is not just responsive - it’s personal. Whether via email or jumping on a call, I always felt like a priority.”

This customer-centric approach goes beyond ticket resolution. It’s about building lasting partnerships.

Preparing for the Future: Beyond Jira-to-Jira

While Jira-to-Jira integration was the initial scope, Kaluza’s future roadmap includes more diverse system integrations:

  • Upcoming Integrations: Jira to ServiceNow, among others.
  • Goal: Expand the seamless data flow across platforms with different workflows and structures.
“With Getint’s support for platforms like ServiceNow, we’re confident about what comes next.”

Conclusion: A Partnership that Scales with Business Needs

Over the last year, Kaluza’s relationship with Getint has evolved from a single Jira-to-Jira connection to a critical integration framework, powering collaboration across multiple third-party partners.

For Kaluza, Getint has delivered:

  • Scalability – Easy expansion across new projects and partners.
  • Security and Compliance – Meeting rigorous energy sector standards.
  • Stability and Support – A reliable platform with personal, responsive customer care.

Want to see how it all started? Check out our original Kaluza case study or watch our interview with Renato.

Looking ahead, Kaluza continues to trust Getint to support their growing integration needs - bridging systems, empowering teams, and driving business-critical collaboration.

FAQ: Jira-to-Jira Integrations with Getint

1. Why did Kaluza choose Getint over Exalate and Backbone?

Kaluza conducted a thorough evaluation of three integration platforms - Exalate, Backbone, and Getint. While all offered Jira-to-Jira integration capabilities, Kaluza needed more:

  • Scalability beyond Jira, with future plans to integrate with ServiceNow.
  • Ease of use, empowering non-technical users through a centralized UI, without relying on complex scripting.
  • No installations required on the partner's infrastructure.

Getint stood out for meeting all these requirements, providing a frictionless, scalable solution that aligned with Kaluza’s vision.

2. How long does it take Kaluza to implement a new integration using Getint?

On average, it takes one business day to fully configure, test, and deploy a new Jira-to-Jira integration with Getint.

Renato, Kaluza’s IT Engineer, typically follows this process:

  1. Alignment call with the internal team and external partner to discuss scope, fields, and workflows.
  2. Configuration and testing in a sandbox environment.
  3. Approval and rollout to production.

This quick turnaround is possible thanks to Getint’s low-code, UI-driven approach, allowing for rapid setup without the need for custom scripting or lengthy development cycles.

3. How does Getint ensure the security of Kaluza’s integrations?

Security is paramount for Kaluza, given their role in the energy sector. Getint’s architecture supports API key-based authentication, ensuring:

  • No direct access between Kaluza and third-party Jira instances.
  • Data flows only as configured - nothing more, nothing less.
  • Partners can revoke API keys at any time for complete control.

Getint successfully passed Kaluza’s rigorous security audits, which involved reviews by legal, IT security, and compliance teams. The solution ensures that data privacy and integrity are always maintained.

4. How does Getint handle updates, and do they affect Kaluza’s integrations?

Getint follows a bi-weekly update cycle, continuously improving the platform and adding new features. These updates are designed to be non-disruptive:

  • No downtime during updates.
  • No breakage of existing integrations.
  • New features appear seamlessly, enhancing the user experience without requiring reconfiguration.

As Renato puts it:

“We barely notice the updates - except when helpful new features appear. Everything keeps running smoothly.”

5. Can non-technical users at Kaluza manage integrations through Getint?

Absolutely. One of the main reasons Kaluza selected Getint was its user-friendly interface:

  • Non-technical users can configure mappings between fields, manage workflows, and adjust settings without needing to write code.
  • Renato has been working on empowering other teams within Kaluza to manage integrations themselves, reducing IT bottlenecks and spreading ownership.

This approach supports Kaluza’s goal of decentralizing integration management, ensuring that teams across the business can self-serve when needed.

Exeperience a smarter way to integrate & synchronize.

Discover the power of seamless connections, bridging your favorite tools for optimized workflow and productivity. Unleash the potential of unified platforms with Getint.