Yasu's AI Agent Lands in Slack to Intercept the $512 Billion Cloud Waste

The Dutch startup's €850,000 pre-seed round backs a bet that developers, not FinOps, should stop the bill before it's run.

About Yasu

Published

You push a pull request. A Slack message pings, not from a colleague, but from an AI agent named after a Japanese term for peace. It has reviewed your code and found an idle RDS instance, a potential $1,200 monthly overrun. It suggests a fix, offers to create a ticket, and asks for your approval to act. This is the moment Yasu is engineered for, a quiet intervention in the developer’s native habitat before the cloud invoice arrives [TechFundingNews, 2025].

The wedge is in the workflow

Yasu’s bet is not on better dashboards. It’s on intercepting waste at the point of creation, inside the tools where engineering decisions are made. The company builds autonomous AI agents that integrate directly into Slack and GitHub, scanning code and infrastructure changes for inefficiencies on AWS, Google Cloud, and Azure [TechFundingNews, 2025]. The promise is a shift from reactive FinOps, analyzing last month’s bill, to proactive cost intelligence woven into the CI/CD pipeline.

The founding team, Vikram Das and John in ’t Hout, brings a classic operator-technologist pairing to the problem. Das spent two decades in cloud engineering, including a stint at AWS [Venturing with Vishesh podcast, 2026]. In ’t Hout, the CTO, builds the system meant to stop it. Their early €850,000 pre-seed round, led by Akka with participation from Empower Impact and Antler, signals investor belief in the ‘shift-left’ approach [Tech.eu, Nov 2025].

A crowded field with a new angle

The cloud cost optimization space is dense with established players like CloudZero. Yasu’s differentiation hinges on automation and developer experience. The company claims its agents can recover over 15 engineering hours per week and drive 30-35% cost savings, translating to over €300,000 in annual savings per customer [TechFundingNews, 2025].

  • Integration depth. Shallow integration risks noisy, irrelevant alerts that developers will mute.
  • Developer trust. Engineers are wary of automated systems touching production infrastructure.
  • The competitive moat. While first to market with an ‘AI Cloud Engineer’ framing, the concept is easily replicable by larger incumbents.

The funds are earmarked for European expansion and adding support for platforms like Azure and Snowflake [TechFundingNews, 2025]. The recent posting for a Founding Commercial Lead role suggests the next phase is about moving from technical build to commercial proof [Antler job board].

The question in the Slack channel

For all the talk of autonomous agents and billions in waste, Yasu is ultimately answering a simpler, cultural question. It asks whether the responsibility for cloud spend can, or should, be fully delegated back to the engineering team. The success of its AI agent won’t be measured in percentage points saved, but in whether that Slack message feels like a helpful nudge from a teammate, or just another notification to ignore.

Read on Startuply.vc