JO:LA Labs Launches AI ‘Business Operating System’ Roster
Artists have spent years assembling their businesses from software that was never really designed to operate as a business. Releases happen in one system, royalties arrive through another, and publishing, distribution, touring, marketing, fan relationships, contracts and finances can all involve different tools, accounts and databases. Running an independent music career increasingly means running a small company whose operating infrastructure is scattered across the internet.
South African music-tech company JO:LA Labs thinks AI can help pull that fragmentation back together. The company has launched Roster, which it describes as an "end-to-end music business operating system" for artists and managers. Its pitch is simple: "No spreadsheets. No juggling apps. No guessing. Just ask." Music Ally reports that its conversational AI interface covers releases, royalties, publishing, distribution, touring, marketing, CRM, contracts and finances, with independent labels and publishers also being targeted.
That's an ambitious piece of software, but the most interesting thing about Roster isn't really the AI. It's the phrase "music business operating system." That description raises a bigger question than what its AI can do: what should an operating system for an artist's business actually operate?
The Music Business Has a Software Problem
The fragmentation Roster is attacking is real. A modern artist can have enormous amounts of digital infrastructure surrounding their career while still having remarkably little infrastructure that actually belongs to them. The distributor knows about the releases, streaming services know about the listeners, social networks know about the audience, payment providers know about transactions, and rights organizations know pieces of the catalogue.
Managers and artists are left connecting those systems through spreadsheets, documents, dashboards and increasingly APIs. Roster's answer is to put an intelligent layer across much more of that business, allowing the artist or manager to interact with the operation through a conversational interface. That's considerably more interesting than simply bolting a chatbot onto another music dashboard because it recognizes that artists don't just need another tool; they need a way to operate the business surrounding their work.
Starting in Africa Makes Sense to Us
There's another part of Roster's strategy that caught our attention: it is starting in Africa. Founder Thabiso Khati is a veteran of the African music business, having worked with companies including UMG Africa and Gallo Record Company. Roster's FAQ says the product starts in Africa because its founder is African and "the market needs it most," while being designed for emerging markets globally and to compete in Western markets as well. Music Ally reports that 50 artists, managers and independent labels in South Africa and other African countries are already testing it.
That feels familiar to us. Years before Certifyd, we built a music technology product that found some of its strongest organic adoption in Africa, particularly Nigeria. We didn't begin with a grand strategy to capture the Nigerian market; creators and listeners there simply responded to what we were building, and that experience stayed with us.
The products and eras are different, but the signal is familiar. Markets that aren't as deeply locked into the incumbent music-technology stack can sometimes be unusually receptive to different ways of building it. Roster is approaching that opportunity through AI and business coordination, while our own experience eventually pushed us further toward the underlying infrastructure question.
An Operating System Is More Than a Dashboard
The operating-system metaphor is useful because an operating system isn't simply where you look at information. It's the environment where things run: applications interact with it, files live within it, permissions are managed through it and different applications can specialize because something underneath them provides a common operating layer. That is an interesting way to think about creator technology.
The music business doesn't need one company to build every application an artist will ever use. Artists will continue using specialized products for distribution, promotion, touring, accounting, analytics, lyrics, discovery and whatever comes next. The bigger question is what sits underneath all of them.
Today, the applications themselves frequently become the foundation. An artist's identity becomes an account inside a service, their audience becomes followers inside another service, their releases become records inside distributor and streaming databases, and their commercial relationships live inside payment platforms, ticketing companies and marketplaces. The artist may operate the business, but much of the digital business itself lives on infrastructure operated by somebody else.
Roster Solves One Layer of the Problem
Roster deserves credit for trying to reduce that operational mess. If an intelligent system can understand the relationships between releases, royalties, contracts, publishing, touring, marketing, finances and fan activity, it could eliminate a considerable amount of administrative work. That is particularly valuable for independent artists and smaller teams that don't have departments of people performing those functions.
There is still an architectural distinction worth making, however. Bringing a creator's fragmented business into one hosted service is not the same thing as giving the creator infrastructure of their own. Roster appears to remain a centrally operated service: users create accounts, subscribe to plans and operate their businesses through an environment provided by Roster.
That isn't inherently a criticism of the product. Centralized software can be extremely effective at solving fragmentation, and most useful business software on the internet works this way. But if we're going to use the term artist operating system, it's worth asking how far the metaphor should go.
Centralization Can Solve Fragmentation — and Create a New Dependency
Centralization offers an obvious answer to a business scattered across ten different systems: bring more of it into one. Put an intelligent interface in front of the complexity and let the software reconcile information that artists and managers previously maintained manually. From an operational perspective, that could be a substantial improvement.
The trade-off is that consolidation can create a new dependency at the same time it removes several smaller ones. The creator may have fewer applications to manage, but more of the business can now depend on one service remaining available, affordable and willing to operate under the same terms. Exporting information can reduce that risk, but portability of files and ownership of infrastructure are not quite the same thing.
If an artist's business is becoming digital enough to require an operating system, the long-term opportunity may be larger than giving the artist a better interface for accessing that business. Creators could eventually control part of the system of record itself. That changes the operating-system idea from software that organizes the creator's business into infrastructure upon which other software can operate.
What Should an Artist's Operating System Actually Operate?
Imagine an artist operating environment where the creator isn't simply seeing information aggregated from their digital business. Identity, works, release records, collaborator relationships, publishing context, permissions, catalogue information and commerce could actually originate there. Those records could then interact with specialized applications without requiring each application to become the authoritative home of the creator's business.
A lyric company could remain excellent at lyrics, a distributor at distribution, and Roster at AI-assisted business management. Social networks could continue connecting artists with audiences, while streaming services could continue playing music. The difference is that none of those companies would necessarily need to become the place where the creator fundamentally exists.
That architecture changes the relationship between creators and software. Instead of repeatedly rebuilding identity, catalogue and business relationships inside every new service, the creator becomes a common layer those services can connect to. Applications become tools around the creator rather than containers the creator has to live inside.
Certifyd Approaches the Problem From Underneath
This is where Certifyd Core approaches the operating-system question differently. Core is locally operated creator infrastructure designed so that identity, works, publishing context and commercial relationships don't have to originate exclusively inside a centralized Certifyd database. The creator can operate infrastructure where those records begin and then participate in a wider network.
The architectural distinction is relatively simple. A centralized operating platform puts the service between the artist and the connected ecosystem. Creator-operated infrastructure instead makes it possible for applications and networks to connect outward from a foundation the creator operates.
That doesn't eliminate platforms, and creator sovereignty doesn't mean refusing to use other people's software. Artists should use excellent software wherever it exists. The objective is to make sure that using an application doesn't require handing that application responsibility for being the foundation of the creator's entire digital business.
AI Makes the Infrastructure Question More Important
Products like Roster may actually make creator-controlled infrastructure more useful rather than less. AI agents become significantly more powerful when they have reliable context, and an intelligent music-business system may need to understand who the artist is, what they have released, who collaborated on the work, what agreements exist, where revenue came from, what rights are involved and which relationships matter.
Today, much of that context has to be reconstructed from external systems. Information comes from APIs, uploads, accounts, spreadsheets and documents, often with different services holding different versions of the creator's business. The creator stack has become complicated enough that we increasingly need intelligence simply to make sense of it.
There is another possible evolution alongside better aggregation. Instead of endlessly becoming more sophisticated at reconstructing the creator from everybody else's databases, more authoritative information could originate with the creator. An AI business system could then connect to an existing creator-controlled identity and catalogue rather than having to reconstruct them from scratch.
Music Technology Is Moving Down the Stack
For years, creator technology concentrated heavily on destinations: another streaming platform, another social network, another marketplace or another dashboard. More recently, companies have begun building systems around the creator rather than simply another destination for the creator's content. That shift may prove more important than any individual application.
We're already seeing pieces of it emerge in different parts of the industry. Lyric services are giving artists more direct authority over catalogue information, music-business software is becoming sophisticated enough to describe itself as an operating system, and AI agents are beginning to coordinate parts of careers that previously required multiple applications and spreadsheets.
Roster belongs to that movement, and so does Certifyd, although the infrastructure boundary is different. Roster asks how much of an artist's business can be coordinated through one intelligent environment. Certifyd asks how much of the underlying digital infrastructure can originate with the creator themselves. Those ideas don't necessarily compete and could eventually complement each other.
The Best Creator Operating System Doesn't Need to Do Everything
Certifyd doesn't need to build the world's best touring AI, accounting system, lyric database, social network or streaming service. Specialized companies can build those things, and creators should be able to choose among them. The role of creator infrastructure should be to let those applications interact with the creator's business without requiring each application to become its foundation.
That creates an interesting possibility for systems like Roster. An intelligent business layer could potentially sit over creator-controlled infrastructure, using AI to plan tours, reconcile royalties, prepare releases, analyze markets and coordinate the business. Underneath those applications could sit an identity, catalogue and commercial foundation that doesn't disappear simply because the creator changes tools.
That is much closer to what an operating system actually does. It doesn't have to perform every specialized task itself. It provides an environment in which specialized tools can work while maintaining a common foundation underneath them.
Artists Need More Than Better Software
Roster's premise acknowledges something that has become increasingly obvious: being an artist in 2026 means running a complicated digital business. Better software can make that business considerably easier to operate, and AI may eventually make much of the software itself almost invisible. Roster is a compelling example of what happens when music technology begins treating the artist's career as an interconnected operation rather than a collection of unrelated accounts.
But once the music industry starts seriously talking about operating systems for artists, the infrastructure underneath those systems becomes part of the conversation. Centralized software can coordinate an artist's business extraordinarily well; creator-controlled infrastructure can give that business an independent foundation while still allowing sophisticated software to operate around it.
The future probably needs both. The most capable artist operating system may combine intelligent software with infrastructure that doesn't require the creator to surrender the underlying business to the company providing the interface.
Because the ultimate artist operating system shouldn't just help creators run their business. It should give their business somewhere to live.