The CMX Story: How a Platform Became an Agency
This is the history of how CMX grew from a public chat project into the work we do today. For the current direction, see What’s Changed at CMX.
How CMX Started
CMX wasn’t founded as a digital agency. It began as a public chat service, and keeping it usable meant dealing with problems a design preview couldn’t reveal. People notice quickly when a connection fails or a conversation becomes difficult to moderate.
That experience is part of the history behind our client work today. The timeline below follows how the platform changed and how CMX gradually moved beyond it.
2020: The Spark
CMX started as a public web chat project. Visitors could enter a room and talk with other people in real time. The first version kept the experience straightforward.
Operating the rooms raised practical questions about navigation, moderation and keeping a service usable while people were online. Those were some of the first lessons that later carried into website work.
2021: Learning Systems
As the community developed, the work extended beyond the public chat interface. CMX began using moderation tools, uptime checks and logs to help manage the service.
Keeping a live product running involved fixing issues, documenting changes and coordinating the work behind the scenes. That experience later informed how CMX approached projects and technical support.
2022: Structure and Scale
CMX continued working on its chat and community systems, including logging and connections with Discord. Cross Chat was part of the broader experimentation with communication across servers.
Projects like these raised questions about permissions, message routing, reliability and moderation across different spaces. The old Cross Chat bot is no longer an active CMX product, but the engineering lessons remain relevant.
2023: Rebuilding the Platform
CMX worked on a redesign of its chat platform and changes to the systems supporting it. The project involved interface work, testing and the routine problems that come with maintaining software for a community.
Planning changes, tracking issues and keeping documentation became part of the work. Those habits would later be useful on client website and software projects.
2024: Trust, Safety and Research
Moderation and account safety had been ongoing concerns for the chat platform. CMX also explored trust and investigation work under the name CXI, with attention to public information, verification and online risks.
That experience informed the direction of today’s OSINT services. The current offering is built around checking sources, showing evidence and explaining what a finding does or doesn’t establish.
2025: Moving Into Client Work
During 2025, websites, content, research and technical implementation became a larger part of CMX’s work. Experience from operating the chat platform shaped how the team approached maintaining websites, coordinating changes and handing projects over.
CMX was changing direction, and the public chat service would eventually become part of the company’s history rather than its main offering.
Technical Lessons
Running the platform involved keeping a public service available, investigating faults, handling moderation and making changes without losing track of what had been done. Chat and Discord integrations also introduced practical work around permissions, routing and reliability.
Those lessons still matter when CMX takes on a website or system project. The requirements, risks and testing are different each time, so the work starts with understanding the actual problem.
2026: CMX Changes Direction
By 2026, the public chat platform was no longer the center of CMX. The work that grew around it had become more important: websites, design, SEO, automation, infrastructure, research, and the systems needed to run those projects well.
The website changed with that reality. Older chat and community material remains part of the history, but CMX now presents the services and technical work people can actually hire us for. What’s Changed at CMX explains that transition directly.
The product work also changed. We are building Continuum, a system designed around longer running goals, changing plans, unfinished work, authority, and verified outcomes. The CMX platform architecture page explains how Continuum, Coordinator, Authority, Runtime, Human Attention, and the infrastructure underneath them fit together.
Continuum extends the work beyond live conversations. It’s being designed to keep unfinished responsibilities available while plans change, without depending on one chat session to remember what happened. That is a different kind of product from the original public rooms, though the experience of running those rooms remains part of its history.
For current client work, see CMX services.
