Tucked away among a thousand other moments at Atlassian’s Team ’26 conference in Anaheim on May 1st, the announcement was made. The Atlassian Marketplace launched Riffle Resilience, a Dallas-based startup that most people outside the operational resilience community had never heard of. Atlassian Ventures also acknowledged that it had written a check in the same sentence.
Observing these developments gives the impression that the smaller announcements frequently have greater significance than the keynote demonstrations. On their own, marketplace launches seldom garner media attention. However, a Marketplace launch combined with funding from the parent company’s venture arm usually has some significance. It conveys a belief—or at least a working hypothesis—about the future course of the ecosystem.
Riffle is developing within a less glamorous category. For many years, operational resilience has been confined to binders. exercises at the table. PDFs with version numbers that have not been updated since the last reorganization. Everyone who has attended a business continuity meeting is familiar with the routine: the same vendor lists, the same slides, and the same uneasy sense that nothing would really work if something went wrong on a Sunday at two in the morning.
One of the cofounders, Shane Mathew, stated it clearly in the announcement. Teams don’t move into a different setting when disruptions occur, he claimed. They utilize the tools they already have. Although it’s a brief remark, it sums up the problems with the majority of resilience programs. They take a seat next to the work. It is not where they reside.
Riffle is attempting to integrate the discipline into Jira, Jira Service Management, and the workflows where engineers and operators actually work. mapping of value streams. tracking of dependencies. Coordination in real time during incidents. The argument is that, rather than being a quarterly compliance ritual managed by a team that most employees never meet, resilience becomes a layer of how work operates.
The question of whether it works is another. It’s a risk to build natively on Atlassian’s Forge platform; it will become easier as Atlassian makes investments in Forge, but it will become more difficult if businesses begin to favor custom AI stacks created outside of the marketplace model. Riffle might have timed it perfectly. Banks throughout Europe are still struggling to comply with the requirements of the Digital Operational Resilience Act, which went into effect in January of last year. Riffle claims that it already has design partners in industries like healthcare, manufacturing, and financial services where downtime has serious repercussions.
The other cofounder, Aaron Callaway, described the business as “AI-native,” a term that has largely become meaningless in the last two years. His comment about realistic, quantifiable use cases that teams can implement today, however, was the more intriguing part of it. That’s a stealthy attempt at the larger AI market, where a large portion of sales remain in pilot purgatory.
Riffle’s strategy is in line with the direction of work within the Atlassian ecosystem, according to Georgia Zhang, director of Atlassian Ventures. Although venture executives seldom commit to specifics, Atlassian Ventures has been selective about who it supports. businesses that expand the platform. companies that increase the stickiness of Jira and Confluence within businesses.
The amount of contemporary enterprise software that is being rebuilt in this manner is difficult to ignore. Instead of being stand-alone products, they are integrations added to systems that users are already accustomed to. With Atlassian’s approval and a small portion of its funds, Riffle is placing that wager. The question of whether businesses truly transfer their resilience work from the binder to the workflow is still up for debate.
