The first version of Directus was written in ActionScript. This is the sort of detail that instantly carbon-dates a software project. It also gives Ben Haynes’s story its proper scale. In 2004, the iPhone did not exist, “headless CMS” was not yet cocktail-party vocabulary, and Haynes was running a small digital consultancy in New York. His team made websites, installations, internal tools and whatever else clients such as Google, Prada, AT&T and SoulCycle required. The work changed. The boring beginning did not.
Every project needed data storage, authentication, connectivity and some safe place for a client to manage the finished thing. Engineers could use tools such as phpMyAdmin. A museum curator, marketer or studio manager generally could not. So the agency kept building bespoke administration screens, the digital equivalent of constructing a new kitchen every time someone ordered lunch.
Haynes, a communication-design graduate who had also spent eight years in the U.S. Air Force working with electronic warfare, noticed the common layer. What if the database itself could acquire an interface - simple enough for a non-technical user, useful enough for an engineer, and flexible enough not to dictate the rest of the project? He built the first version, then the next four. Only later did he pass the code to what he cheerfully called “more capable hands.”
“I think keeping things very simple has been a big part of this history of how we’ve built the software.”Ben Haynes
A designer meets a database
The technical origin is useful; the design origin is more revealing. Haynes describes himself as “a designer and creative by trade.” His instinct was not to hide complexity with a decorative dashboard. It was to make power legible. Directus would sit on top of a SQL database without forcing its owner into a proprietary data model. Developers would get APIs and automation. Other people would get visual ways to browse, edit and understand the same information. Everyone could use the tool without pretending everyone had the same job.
The original Directus bargain
as the layer
That respect for the underlying database became a product philosophy: arrive as a layer, not a landlord. Haynes uses “unopinionated” so often that it is practically an opinion in its own right. Customers choose PostgreSQL, MySQL, SQLite or another supported database. They keep their schema. They retain an exit. Directus supplies a collection of primitives - browse, manage, visualize, connect and automate - which Haynes compares to a carpenter’s tool belt. A hammer is narrow. What carpenters do with it is not.
The name carries the same mixture of order and improvisation. Haynes explains Directus through Latin, the notion of arranging things in straight lines. Yet it also grew from “DIR,” for directory, an early name he now regards with affectionate embarrassment. He has one orthographic request: please do not write “Direct Us.” Even founders of flexible software need boundaries.
The customer that widened the lens
Around 2011 or 2012, a young SoulCycle provided the clarifying project. The company had a substantial existing data store and a rapidly growing operation. Directus could layer onto it quickly, giving people access without a long custom build. More importantly, the data was not merely “content.” It included studio scheduling, point of sale, bike maintenance, inventory, allocation and connected devices. What Haynes had treated as a content-authoring platform was really an adaptable window onto relational data.
The realization changed the scale of the idea. A content management system is a recognizable box. A general data layer is harder to explain but less cramped. Directus went on to support digital experiences, internal tools, applications, kiosks and connected products. Its category labels kept changing because the useful thing underneath was more stable than the language around it.
Growth did not arrive with a cinematic switch-flip. Directus became open source in 2011. Haynes maintained it through agency work, mergers and acquisitions, and a spell in a corporate product role after a New York firm rolled into AOL and then Verizon. The corporate vantage point was instructive. It also confirmed that he preferred building companies to occupying them.
After leaving, he met Dutch developer Rijk van Zanten, who became his co-founder and CTO. The pair spent years modernizing the platform, including a ground-up TypeScript effort. Directus 9 brought a consequential move from PHP to Node.js. In 2020 they formed the commercial company. In 2022 Directus Cloud launched, and a $7 million Series A led by True Ventures gave the two-person project room to become an organization.
The counter on the desk
Haynes once kept a dedicated physical counter on his desk for GitHub stars. In 2017, Directus had roughly 1,400. The counter eventually migrated to his computer’s menu bar, a tiny readout with the emotional authority of a stock ticker and the commercial precision of applause. He knew the number could be called vanity. He watched anyway. Each star represented a builder choosing to remember the project.
His preferred metaphor for this growth is a lawn. Sod produces a fast, photogenic result. Seed takes longer, but its roots are varied and resilient. Directus relied heavily on word of mouth, open code and developers trying it without a sales conversation. A Saturday post on Reddit or Product Hunt could create a visible jump. The underlying line, however, was built one voluntary user at a time.
Patience should not be confused with purity. Open-source businesses collect awkward invoices. In 2023, Haynes and van Zanten changed Directus to the Business Source License 1.1. The code remained public, most organizations could still use production deployments free, and each release would convert to GPLv3 after three years. Larger organizations crossed a financial threshold that required a commercial license. It was a deliberate attempt to make heavy institutional use help pay the maintainers.
“It’s not about locking things down. It’s about opening them up, responsibly.”Ben Haynes
Haynes has always explained the business with food. The open product is cake; hosted service and other extras are icing. Too little cake and the offer becomes an unrecognizable cupcake of upsells. Too little icing and nobody funds the bakery. His metaphors are domestic because the tradeoffs are not. Security, salaries and long-term maintenance cannot survive on symbolism.
The backend gets its turn
In March 2026, Haynes announced “the end of the UI era” with enough theatrical caution to admit the title was sensational. His argument was narrower and more useful. AI tools can now generate competent forms, dashboards and interfaces quickly. That abundance makes the visible layer less scarce. Permissions, governance, resilience, scale and trustworthy access to existing data remain slow, consequential work. The front end attracts admiration. The backend earns trust.
The thesis brings Haynes back to his original irritation. More people can build now, but each new application still needs a responsible relationship with data. A gorgeous interface can arrive in an afternoon and produce a dreadful Monday if nobody considered who is allowed to read, change or delete what sits beneath it.
Monospace, opened to public preview in July 2026, is his answer to the larger version of that problem. Directus traditionally centered on one project and one database. Enterprise teams live among many projects, sources and silos. Monospace is designed as a unified layer across them, letting data remain in place while developers, business users and AI agents work through a shared governance surface. The product is new. The instinct is twenty-two years old: stop rebuilding the hidden machinery, make it understandable, and let the people closest to the problem do the work.
Haynes’s résumé has a few pleasing departures from the standard software-founder template. He wrote Paper Pilot, a 2007 book with 24 paper-airplane projects and a foldout runway. He taught advanced web development. He studied design, not computer science. The rabbit running through Directus’s identity is no accident of clip art; Haynes has spent his career making forbidding systems feel like objects people might want to approach.
There is a quiet lesson in the longevity. Directus did not endure because Haynes correctly predicted every label the industry would adopt. It endured because he picked a layer that kept mattering. Websites gave way to apps, kiosks, internal tools and AI agents. The database stayed. So did the distance between people with valuable context and the machinery holding their information.
Twenty-two years is long enough for a workaround to become infrastructure and for infrastructure to become a philosophy. Haynes still talks about democratizing data, but the mature version of democracy in his work is not universal permission. It is useful access with rules, ownership and exits. That is less romantic than disruption. It is also the sort of idea that may survive another technology cycle.