Written from the verified transcript and checked against it. Every figure links to the moment it was said.
Michael Cannon-Brookes said Atlassian acquired The Browser Company for a little over $600 million a year ago to rebuild the web browser for knowledge workers, not consumers. He argued that technological disruption moves the interface stack up, and the browser is now the front surface for 80-90% of a knowledge worker's day, where tabs are applications and documents, not web pages. He positioned Dia as a 'doer' rather than a browser, with features like live tab groups that auto-open and close documents across Google Drive, Confluence, and SharePoint, plus AI that reads text to understand meaning. The most popular feature is the morning brief, which scans calendars, messaging, and documents to prioritize tasks. He emphasized that Dia runs locally, maintains a context graph of people relationships across SaaS apps, and does not replace tools like Slack or Confluence. He noted Dia is in beta on Windows with GA very soon, and used daily on Mac by a huge number of people.
Key takeaways
Dia's most popular feature is the morning brief, which uses AI to read millions of words and prioritize daily tasks across SaaS apps.
Dia is in beta on Windows with general availability coming very soon, and is used daily on Mac by a huge number of people.
Atlassian acquired The Browser Company for a little over $600 million a year ago to build a browser for knowledge workers, not consumers.
Dia maintains a constant context graph of people relationships across all SaaS applications, deduplicating and normalizing data to prioritize tasks.
Dia's live tab groups automatically open and close tabs for documents across Google Drive, Confluence, and SharePoint based on user activity.
So, Dia is the browser you acquired a company called The Browser Company, I think for a little over 600 million. That was a year ago. We spent a lot of time with The Browser Company when they were working on their products. And you know, at first they were building a consumer product. And then the notion that what they were building was more like an operating system came into focus as we covered Dia in their product strategy. And most of those conversations and most of that coverage, most of which was done by my colleague David Pierce, was happening simultaneously with Google search traffic dropping, right? And the very notion of the browser as an information document viewer was changing in big ways. If you think the homepage of Chrome opens to Google and that's going to take you to a bunch of webpages, well, actually Google has a lot of ideas in between there that is changing traffic on the web. And yet at the same time the web as an application environment is a thing that can make AI agents vastly more capable because the applications all live somewhere that they can go trust them. It was just obviously explosive at that time. You and I are talking, it's like a week or two into Meta launching Muse. And the power of Muse is that Mark Zuckerberg has given everybody 8 gigs of RAM and 8 gigs of storage in the cloud with the web browser. And now you have an agent that can just go use a web browser for you. And this is like very powerful and Amazon is furious about it and has blocked this web browser. Do you have Dia because you need to control the application layer or is it something bigger than that?
I think two things are important to understand. When you get technological disruption, one thing that happens is we all move up the interface stack a level, right? Not a lot of people competing about DOS or operating systems anymore. In the modern internet world, one way to move up the interface stack is to move towards the browser. Features that were inside of applications move to being inside of the browser as we increasingly learn and operate that way. I think second, the biggest thing that's changed and you know, usually people's habits change is what happens. Knowledge workers, yourself, myself, everybody, we spend 80% of our lives in a browser. But we're not reading articles all the time. We are sometimes. We're not reading web pages, we're using applications. We're using Gmail and Google Calendar. We have Slack open. We're using the Atlassian platform. All of our applications and Salesforce and you know, watching videos like Loom and interacting with those videos back and forth. That set of tabs is no longer a set of web pages. It is a set of documents and applications that have massive power underneath them. We're trying to rebuild the web browser in a totally new form for knowledge workers who live in applications, who have their browser open 80-90% of their day as their front surface area and want a better way of managing those applications and getting work done across those applications. The browser has some incredible power to be able to do that. It requires us to understand SaaS apps very deeply, which we do. It requires us to understand enterprise security very deeply, which we do. It requires us to not chase the consumer audience. Chrome, Safari are built the way they are because they have to cater from 5-year-olds to 100-year-olds who are doing less work-related knowledge tasks and are doing more browsing and entertainment and other tasks. That doesn't mean that someone who's a knowledge worker in a corporate job isn't looking at YouTube or Facebook sometimes, but it's not the purpose of their job. So, we believe we can build a better browsing experience, a better work experience, right? One of the pitches we had for the product is we're not building a browser. We're building a doer. Right? It's a totally different thing. We're helping you do things. We're not helping you browse passively. And hence why tabs and split screens and pin tabs and groups and AI and dynamic tab groups, live tab groups as we have of the documents you have is a great example, right? Our documents live tab group in Dia shows you the documents it will automatically open and close tabs if you want to think about it that way for you across any content application. Google Drive, Confluence, SharePoint, any application you use that has documents, if someone comments or shares a document with you, the tab automatically gets opened by your web browser. And if you're done with it somewhere else, it automatically gets closed by your web browser. Because that is a set of documents I'm currently working on. Same for pull requests or anything like this. Then we add AI over the top. AI lets us change how we use these knowledge applications in insane ways. The browser has your entire history of what you've done. It has skills. It has an ability to run AI. Like you can use Dia to make Minesweeper. And you can use Dia to make Minesweeper out of the tasks that you did in the last week. And it'll go start a computer underneath the browser. It'll run a bunch of code generation. It'll create an application for you that plays Minesweeper based on the tasks you have completed in the last week. Now, I don't think that's a very useful application, but the fact that it can do it is amazing. When you apply that to what you can do, so the most popular feature of Dia is the morning brief. People are blown away and often suspicious about how we can understand what you need to do today with a fidelity and a design quality and an experience that makes it a joyful experience when it pops up every morning. Mine opened about 45 minutes ago. That is a design challenge. That is an amazing team of designers that are thinking about our most used application surface area and reimagining it for knowledge workers and for the AI era simultaneously with access to every SaaS application that you have open on your computer in a way that corporate security is going to say, 'This is a good idea and I trust it.' And that is the mission we embarked on a year ago, Browser Company embarked on 3 years ago. And it's usable today. It's coming out on Windows any day now. It's in beta on Windows, GA is very very soon. And it's used on a Mac by a huge number of people on a daily basis and only increasing.
Let me just push a little bit on moving up the stack to the next level of user interface. You could argue that already happened with web browsers, right? Windows was disrupted by the very presence of the web browser. The iMac was only successful because the most interesting thing you could do with a computer at that time was go on the web. And so the presence of the web browser on the Mac allowed a bunch of applications to move away from Windows binaries to being web apps and then cloud apps and now productivity apps in the cloud. The web as an application environment is probably more vital and important than ever before, right? It is the thing you're describing. It's where all the applications live and a custom web browser designed to do work is very important. At the same time I would just say like didn't that already happen? Are you actually moving up the stack or are you just building a more custom web browser? Or is AI changing that in some other way?
4 more exchanges in this transcript
Sign in free to read the rest of this interview. No card required.
Cannon-brookes, M. (2026, September 28). Atlassian CEO Mike Cannon Brookes talks Dia Browser on Decoder [Interview transcript]. Chris Messina. CEOInterviews.AI. https://ceointerviews.ai/interview/2944603/
MLA
Michael Cannon-brookes. "Atlassian CEO Mike Cannon Brookes talks Dia Browser on Decoder." Chris Messina, 28 Sep. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/2944603/.
BibTeX
@misc{cannonbrookes2026_2944603,
author = {Michael Cannon-brookes},
title = {Atlassian CEO Mike Cannon Brookes talks Dia Browser on Decoder},
howpublished = {Interview transcript, Chris Messina. CEOInterviews.AI},
year = {2026},
month = {sep},
url = {https://ceointerviews.ai/interview/2944603/},
note = {Speaker-attributed transcript with timestamps}
}