Home / Why true cloud-native architecture is the foundation for AI-native BSS

TARANGA INSIGHTS · Operator modernisation

Why true cloud-native architecture is the foundation for AI-native BSS

As BSS messaging shifts from cloud-native to AI-native, the architectural distinction matters. Running in the cloud is not enough: independent change, automation and resilient operations provide the foundation for continuously evolving AI-native BSS.

By Ivan Hagen ·

An abstract sphere assembled from separate glowing blue and cyan cubes against a black background.
Illustration: Pivoslav Chipsov / Unsplash

In an interview published by RCR Wireless News on 22 January 2024, Tomás Lajous, then a Senior Partner at McKinsey & Company, discussed AI-native telecom businesses generally:

“The notion of having a cloud-native telco, I think, is part and parcel to having an AI-native telco.”

His observation concerns the wider telecom operating model, rather than BSS specifically. This article applies that architectural perspective to BSS while recognising that AI can also deliver value on existing systems.

Running in the cloud is not the same as being cloud-native

Cloud deployment is not the same as a cloud-native architecture, and that difference becomes critical when AI moves from assisting users to driving business operations.

Moving an existing, monolithic BSS to a cloud server is a lift-and-shift deployment. Without changes to its internal boundaries and operating model, it remains a cloud-hosted application.

A traditional BSS can be installed on a public-cloud virtual machine. It can be packaged into containers, or even deployed on Kubernetes. These changes may simplify infrastructure management and improve portability. But they do not automatically remove tight coupling between components, long release cycles or operational dependencies inherited from the original architecture.

A genuinely cloud-native approach is about how the software is designed, delivered and operated. The Cloud Native Computing Foundation emphasizes loosely coupled systems that are resilient, manageable and observable, combined with automation that enables frequent, predictable change.

The distinction is important because a container is a packaging mechanism, not proof of architectural independence. A collection of microservices can still behave like a monolith if every change requires shared testing, synchronized deployment or a common release window.

Cloud-native is not a location. It is an architectural and operational capability

The practical test: can the platform change independently?

Operators evaluating a BSS platform should look beyond technology diagrams and ask how the system behaves when a real business requirement changes. Imagine introducing a new subscription benefit, revising a pricing rule or extending an order flow. Can the relevant capability be modified, tested and released without coordinating an upgrade across the entire platform?

If the answer is consistently no, the system may be cloud-hosted or cloud-adapted, but the operational benefits of cloud-native design remain limited. This is not to say every capability must always be a separate microservice. Service boundaries should reflect useful business and technical independence, not an arbitrary number of components.

Cloud-native is also about more than code structure. Continuous integration and delivery, automated testing, infrastructure automation, observability, resilience and security practices determine whether a platform can evolve safely and at speed.

Why AI-native raises the bar

The move toward AI-native BSS introduces a new level of architectural pressure. Connecting an AI chatbot to an established BSS can provide value. But adding AI functionality around a difficult-to-change core is not the same as designing a platform whose capabilities can continuously evolve with new AI-driven workflows.

AI-native operations require an effective way to introduce new reasoning and orchestration capabilities, connect them to dependable business transactions, monitor their behavior, enforce security and policy controls, and improve them as experience accumulates. AI components may need to scale and change at a very different pace from billing, charging or order-management transactions.

An architecture that requires coordinated platform releases for every new business capability can become a bottleneck. The AI layer may innovate quickly while the underlying commercial systems continue to move at slow speed.

Is cloud-native a prerequisite for AI-native?

There is an important nuance. AI capabilities can be connected to legacy BSS platforms, and operators can begin using AI without first replacing their entire technology estate. A legacy application does not have to become cloud-native overnight for an AI agent to deliver useful outcomes.

However, if the ambition is a BSS in which AI is a fundamental, continuously evolving part of business operations, genuinely cloud-native characteristics become a practical foundation. Independent evolution, resilient operations, automation and well-defined interfaces make it substantially easier to introduce and govern AI-driven capabilities at scale.

In that sense, cloud-native is a prerequisite for the AI-native architecture we should aim to build—not because AI cannot run on legacy systems, but because the full operating model demands adaptability that lift-and-shift alone does not provide.

Five questions worth asking your BSS vendor

  • Can one business capability be changed and released without a coordinated upgrade of the entire platform?
  • How much of testing, deployment, rollback and infrastructure management is automated?
  • Can different services scale independently based on workload and demand?
  • How are resilience, observability and security handled across the platform?
  • Can you demonstrate these characteristics in a working environment, rather than only on an architecture slide?

Cloud-native is the foundation, not the destination

Cloud-native architecture does not by itself make BSS AI-native. It does not give AI agents business understanding, decision authority or trustworthy execution. Those requirements need additional architectural capabilities, which deserve their own discussion.

But a platform that cannot be changed, tested or operated independently will struggle to support the pace of AI-led innovation. Before accepting the next AI-native claim, operators should ask a more basic question: is the BSS genuinely cloud-native in the first place?

At Taranga, we see true cloud-native design as a foundation for the next generation of BSS—not simply a deployment option. In our next article, we will explore the additional capabilities needed to move from cloud-native infrastructure to AI-native business operations.

Sources

Related articles

Operator modernisation

When Personal AI Agents Become the Customer: Why Telecom Product Catalogues Must Evolve

Telecom operators have for years focused heavily on enabling a customer friendly digital customer journey. Now a lot of operators are expecting AI agents to be a vital part of the customer engagement with the operator. The next wave of BSS transformations is about enabling commercial interactions where the customer is represented by AI agents.

Read article →
Explore the related solution →

YOUR NEXT MOVE

Let’s start with your business.

Tell us what you want to change, launch or bring to your customers.

Request a meeting or demo

Opens your email application.