Blog
OutSystems Developer Cloud or OutSystems 11: the difference for a new project
· 4 min read
You have decided that a process run on Excel and email will finally become a proper application, and you ask a builder who works with OutSystems for a quote. Then a term comes up that you did not know yet: OutSystems Developer Cloud, alongside the OutSystems 11 you come across in blogs and case studies. Two names for the same platform, you might think. It is not. They are two separate products from the same supplier, with a different foundation underneath. For anyone planning a project now, the difference is not a technical detail: it determines where your application runs and how your build team works.
Two platforms, not an upgrade of one another
OutSystems 11, or O11 for short, is the platform that has been around for longer and runs on Microsoft technology: applications run on IIS application servers with Windows Server, and the data lives in Microsoft SQL Server, Azure SQL Database or Oracle. You can have O11 hosted by OutSystems itself, or manage it yourself in your own data centre or on a public cloud such as AWS or Azure. That is how it is described in OutSystems' own infrastructure documentation, including the option to set up production environments as a server farm with multiple front-end servers for availability.
OutSystems Developer Cloud, ODC, is a newer platform built from the ground up on cloud-native technology. According to the documentation on the cloud-native architecture of ODC, ODC runs on Kubernetes, with Amazon Aurora as a PostgreSQL-compatible database and separate storage for configuration, files and container images. Each platform service runs in its own container, and the platform scales automatically based on processor and memory usage. So ODC is not O11 with a fresh coat of paint: it is a different platform, fully managed on AWS infrastructure, without the self-hosting option that O11 does offer.
What works differently once you start building
The difference is not only under the bonnet, but also in how a developer works day to day. In O11 you build in modules that you publish, and their dependencies are deployed together in a deployment plan. The concept of a module does not exist in ODC: according to the documentation for O11 developers moving to ODC, the equivalent term there is an asset, such as a web app, mobile app, agentic app, workflow or library, and each asset has its own lifecycle. In ODC you deploy an app individually to the next stage of your pipeline; a library must first be explicitly released with a version and release notes before another app may use it. That is a deliberately different way of working from O11's combined deployment plan.
The source code itself is also organised differently. O11 has a separate code repository per environment, which means code is recompiled at each step in the pipeline. ODC works with a single central code repository: when you publish in ODC Studio, the code goes as a container image to a central registry, and that image flows through the pipeline unchanged. For a developer coming from O11 that takes some getting used to, but it saves repeated compilation steps with every deploy.
When each platform fits
In its own blog post on choosing between O11 and ODC, OutSystems states that there is no mandatory move from O11 to ODC: both platforms will continue to exist side by side, and organisations already running on O11 do not have to choose one or the other. That is a relevant signal for an SME that already has an O11 application today: it does not need to be migrated to stay relevant.
For a new project the choice is more concrete. O11 is attractive if you need to integrate with existing on-premises systems, if regulation or an existing IT landscape requires your own hosting, or if your organisation already has experience and management in place around SQL Server or Oracle. ODC is attractive if your project is cloud-first, needs to scale automatically with peaks in usage, and you have no need to manage the underlying infrastructure yourself. Because ODC runs entirely on AWS through a managed Kubernetes environment, the discussion about servers, patches and database maintenance largely disappears, at the price of less control over exactly where and how the application runs.
A third consideration is the type of application. ODC is explicitly designed with agentic apps and direct integration with large language models as part of the platform, something that requires more custom work on O11. If, on the other hand, you are going to build a classic business application that mainly needs to connect to an existing on-site ERP or CRM system, that is often better done with O11.
What does this mean for your business?
If you are starting a new project now, factor the platform choice into your preliminary research instead of leaving it to whatever a builder happens to be used to.
- Map out which existing systems the new application needs to connect to, and whether that includes on-premises databases or older interfaces. That often points towards O11.
- Ask explicitly whether hosting should be with you, in your own data centre, or fully managed by the supplier. Only O11 offers the first two options.
- Decide whether AI functionality, such as an agent that carries out actions itself, is a core part of the application. If so, ODC is the platform where that is most deeply built in.
- Do not just ask your builder which platform they recommend, but also why, and which part of that choice fits your situation and which part reflects their own preference.
At HubTwo we build with OutSystems and decide per project which platform suits the situation, not the other way round. Unsure which platform fits your plan? Get in touch with us, and we will think along up front rather than only after the first sprint.