Oracle has expanded its collaboration with NVIDIA to help customers streamline the development and deployment of production-ready AI, develop and run next-generation reasoning models and AI agents, and access the computing resources needed to further accelerate AI innovation.
Multi-tenancy was once a term that described a very particular software architecture: Where an application lives on a server for other computers — tenants — to use it.
Over the years, the definition expanded and now describes much more than that. Sometimes we use it for software architecture, sometimes not. Sometimes we use it to explain how we serve or deploy applications, and even how users access them.
At its simplest, the software industry uses multi-tenancy to explain where software or its architecture splits into manageable chunks. These chunks could save money, simplify processes, or make things safer or easier for customers.
Rather than try to unravel the whole term, it's easier to explain the scenarios typically described as multi-tenancy.
Split by customer
Splitting tenancy by customer is a common architecture for Software as Service (SaaS) applications. A SaaS application is software delivered via a subscription model and usually accessed by a web browser. SaaS software providers manage the application's infrastructure so users don't have to.
Multi-tenancy in SaaS sees each customer get the same product but with resources separate from other customers.
For example, your customers would get isolated:
■ Space on your hosting platform
■ Identity management and security functions
■ Databases
Here, your tenants could be your customers or infrastructure.
Split by location or region
This is where organizations, like big enterprises, serve customers worldwide.
Worldwide or regional support usually means accounting for regional differences. That includes region-specific:
■ Content
■ Languages
■ Outage windows
■ Legal requirements
Here, your tenants could be your regional infrastructure.
Split by business model
Your business model could dictate where your application becomes multi-tenancy. The best example is delivering software to many brick-and-mortar locations, like retail chains, hospitals, hotels, and more.
In this scenario, you could be:
■ Working for an international organization delivering software to its worldwide branches
■ An independent organization delivering software to physical locations for many organizations
Here, your tenants could be each store or a group of stores.
Split by hosting solution
Due to strict processes or legal requirements, you may need to deliver your software to your customers' own hosting solutions. This could be common if you support government agencies or businesses in other sensitive industries.
For example, you may need to deliver your software to your customer's own:
■ Cloud services
■ On-premises servers or desktop computers
■ Data centers
■ Hybrid setups
Here, your tenants could be a deployment target or a group of deployment targets.
And everything in between
At this stage, you may be thinking, "our multi-tenancy application fits a couple of these descriptions," and you'd be absolutely right.
These scenarios can crossover, for sure. And some apps may use more than one multi-tenancy variation at different stages.
That's because software development is only growing more complex and with it, the term evolves too. The lines we draw between these scenarios are blurry and will only get blurrier.
Industry News
Datadog launched its Internal Developer Portal (IDP) built on live observability data.
Azul and Chainguard announced a strategic partnership that will unite Azul’s commercial support and curated OpenJDK distributions with Chainguard’s Linux distro, software factory and container images.
SmartBear launched Reflect Mobile featuring HaloAI, expanding its no-code, GenAI-powered test automation platform to include native mobile apps.
ArmorCode announced the launch of AI Code Insights.
Codiac announced the release of Codiac 2.5, a major update to its unified automation platform for container orchestration and Kubernetes management.
Harness Internal Developer Portal (IDP) is releasing major upgrades and new features built to address challenges developers face daily, ultimately giving them more time back for innovation.
Azul announced an enhancement to Azul Intelligence Cloud, a breakthrough capability in Azul Vulnerability Detection that brings precision to detection of Java application security vulnerabilities.
ZEST Security announced its strategic integration with Upwind, giving DevOps and Security teams real-time, runtime powered cloud visibility combined with intelligent, Agentic AI-driven remediation.
Google announced an upgraded preview of Gemini 2.5 Pro, its most intelligent model yet.
iTmethods and Coder have partnered to bring enterprises a new way to deploy secure, high-performance and AI-ready Cloud Development Environments (CDEs).
Gearset announced the expansion of its new Observability functionality to include Flow and Apex error monitoring.
Check Point® Software Technologies Ltd. announced that U.S. News & World Report has named the company among its 2025-2026 list of Best Companies to Work For.
Postman announced new capabilities that make it dramatically easier to design, test, deploy, and monitor AI agents and the APIs they rely on.
Opsera announced the expansion of its partnership with Databricks.