Innago Simplifies Backup on AWS and Saves 40% with Eon

Read the full AWS + Eon case study >>

Challenge: Scaling Backups Across Kubernetes and EC2

Innago is a fast-growing property management SaaS platform serving small to mid-sized landlords. As the company matured and transitioned to microservices architecture, the team began containerizing more of its workloads using Amazon Elastic Kubernetes Service (Amazon EKS). As environments scaled, backup and restore got harder.

Initially, Innago utilized open-source database operators, such as Crunchy PostgreSQL and MariaDB Operator, to run workloads on EKS. However, they quickly realized the need for a more centralized solution to manage backups at scale, enforce cross-region policies, support granular recovery, and meet compliance expectations.

At the same time, legacy EC2 workloads were still protected via AWS snapshots and Lambda automation, which introduced risk around missing coverage, regional gaps, and lack of restore assurance.

“Defining a policy for mandatory backups, setting retention windows, and requiring a different region used to be a lot of work. With Eon, it’s simple, and even flags things our old setup couldn’t detect.”
‍
— Chris Anderson, Director of Engineering, Innago

Innago sought a unified solution across its workloads to simplify restores, meet compliance requirements, and eliminate the need for manual validation of backup coverage.

Implementation: Agentless Setup and Fast Restore Validation

Innago partnered with Eon’s solution team to provide backup coverage and restore workflows for live EKS clusters running PostgreSQL and MariaDB. The implementation required no cluster-side agents and relied on Kubernetes-native patterns, including PVC-level backup and restore.

They deleted test data, ran restores, and confirmed everything came back clean. The average restoration time for small to medium volumes was 10–15 minutes.

Eon’s responsive support helped Innago’s engineering team gain confidence in the platform from the get go.

Solution: Unified, Policy-Based Cloud Backup with CBPM

Innago implemented Eon’s platform, including its key features:

• Cloud Backup Posture Management (CBPM): Eon continuously scans, maps, and classifies Innago’s cloud resources to automatically apply the right backup policies and enforce compliance requirements, such as cross-region replication.
• Granular recovery and database-level visibility: With Eon, Innago can now restore Kubernetes workloads at the PVC, table, or file level, reducing recovery time and making compliance checks easier.
• Centralized backup operations: Instead of juggling tools across EC2 and EKS, the engineering team can manage everything through Eon’s unified console.
• Agentless Kubernetes backup: The implementation required no cluster-side agents, reducing complexity and aligning with Kubernetes-native patterns.

Results: Faster Recovery, Lower Costs, and Stronger Compliance

With Eon, Innago now has a single platform to ensure backup posture across AWS environments.

• 40% cost savings by replacing traditional snapshots and backup duplication with Eon’s backup-optimized storage tier 
• 10–15 minute restore times for common recovery scenarios
• Cross-region enforcement and retention controls for compliance (SOC 2, PCI, GDPR)
• PostgreSQL consolidation: As part of its modernization, Innago is phasing out MariaDB and consolidating on PostgreSQL—a move supported by Eon’s flexible backup workflows
• Eliminated scripting and manual checks: Eon replaced Lambda-based snapshot logic and custom tooling with fully automated backup enforcement

Why It Matters: A Scalable, Reliable Backup Posture for Growth

Innago can now scale safely, is compliance-ready, auditable, and can grow its international reach. With Eon’s CBPM in place, the engineering team no longer has to manually validate backup coverage or worry about gaps, freeing them from the burden of constant oversight.

Backup is fully automated, and a reliable part of Innago’s cloud infrastructure strategy.