Jeremy Nees shares a quick update on Eon IO a year after its launch and the “cloud backup posture management” concept. He highlights Eon’s “five days summer of shipping,” noting the platform’s expansion into broader platform services and developer-oriented backup capabilities, including near-instant EC2 instance restore using a lightweight hypervisor with read interception while data rehydrates in the background. He covers Eon’s new Microsoft 365 backup and recent Google Workspace support, extending Eon’s protection from IaaS into SaaS. He then explains Eon’s live data lake approach: converting backup data into a cloud-based data lake on an Eon storage tier, exposing it via interfaces like MCP Iceberg S3 and the Eon API with automatic data type conversions and schema inference, and integrating into existing analytics catalogs (e.g., Databricks). He also discusses Eon’s claim that storage savings can offset backup costs, making it effectively cost-neutral while enabling granular recovery and analytics/AI use of backup data.