For most new cloud-hosted business applications, OutSystems Developer Cloud (ODC) is the forward-looking choice: it is cloud-native, organises software as apps and libraries, and is where OutSystems is investing. OutSystems 11 (O11) can still fit when you need self-managed infrastructure or rely on features ODC handles differently, such as Traditional Web screens, BPT processes or SOAP integrations.
Key takeaways
- ODC is OutSystems’ cloud-native platform, built on a Kubernetes-based architecture and managed by OutSystems.
- O11 supports self-managed infrastructure, Traditional Web, BPT processes and SOAP, which ODC handles differently or not at all.
- As of October 2026, OutSystems has not published an end-of-support date for O11.
- If you start on O11 today, design with a later move to ODC in mind.
What is the difference between O11 and ODC?
| Area | OutSystems 11 | OutSystems Developer Cloud (ODC) |
|---|---|---|
| Architecture | Modules grouped in applications | Apps and libraries, cloud-native and Kubernetes-based |
| Hosting | OutSystems cloud or self-managed servers | Managed by OutSystems in the cloud |
| Development tool | Service Studio | ODC Studio and the ODC Portal |
| Web UI | Reactive Web and Traditional Web | Reactive |
| Processes | BPT processes | ODC Workflows |
| Custom code | C# extensions | .NET external libraries |
When should a new project start on ODC?
- You want OutSystems to run and scale the infrastructure for you.
- The app is new, with no Traditional Web screens or BPT processes to carry over.
- Your integrations use REST APIs.
- You want to avoid a platform migration later.
When does OutSystems 11 still make sense?
- You must host on your own infrastructure.
- The new app extends an existing O11 estate and shares its modules.
- You depend on Traditional Web, BPT or SOAP and cannot redesign them yet.
If you choose O11, keep new screens Reactive, prefer REST to SOAP, and avoid new BPT logic where you can, so a later move to ODC is smaller. OutSystems provides a Conversion Assessment Tool and, since 2026, an App Conversion Kit (Beta) for that move.
Do you need different developers for O11 and ODC?
The core skills carry over, but ODC adds new concepts: apps and libraries, ODC Studio and the ODC Portal, external libraries and Workflows. Ask for developers with production experience on the platform you choose, and an ODC certification such as Associate Developer (ODC) for ODC work.
How AWT helps
Anav Webtech (AWT) provides certified OutSystems developers and tech leads for both OutSystems 11 and ODC, and runs O11 to ODC migrations. See OutSystems staff augmentation to add developers to your project.
Frequently asked questions
Is OutSystems 11 being discontinued?
As of October 2026, OutSystems has not published an end-of-support date for OutSystems 11. O11 customers can keep using it, and OutSystems provides tools to move to ODC when they are ready.
Should a new OutSystems project use ODC?
For most new cloud-hosted business applications, yes. ODC is cloud-native and managed by OutSystems. O11 can still fit when you need self-managed hosting or depend on Traditional Web, BPT or SOAP.
Does ODC support Traditional Web apps?
No. ODC uses Reactive apps. Traditional Web screens must be rebuilt as Reactive when an app moves from O11 to ODC.
Can AWT developers work on both O11 and ODC?
Yes. AWT provides certified OutSystems developers and tech leads for both OutSystems 11 and OutSystems Developer Cloud, and runs O11 to ODC migrations.
