Hosting Multiple Web Sites in OutSystems Platform

Hosting Multiple Web Sites in OutSystems Platform


So you have Multiple websites, with distinct URLs, and you want to host all these web sites in the same OutSystems Platform. Here are three distinct ways you can accomplish this:

1. SEO (IIS only)


You can use SEO site rules to redirect urls to specific applications. For example: you can have the URL go automatically to the /CheapDeals/ application on your server. The URL shown on the browser will be


You will first need to make sure you follow the instructions on how to set up SEO in this document.


After this is done, go to Service Center, then Administration and then select SEO URLs. There are several types of rules you can configure here, but for our purpose we want to configure a Site Rule. Following the example above you’d create a new Site Rule with the following options:

2. Additional IIS Websites (IIS only)


This method requires manual configuration, but if followed as explained the platform will from then on publish the applications to the websites correctly.


  1. Create the new Website, with any root folder (you can use the same as the default web site - OutSystems Applications do not use this folder);


  1. (recommended) configure your new web site’s application pool recycling settings;

  2. “Add Application”, choose the same Physical Path as the original eSpace’s application and the same Alias as well;

  1. (important) all the producer eSpaces from which this eSpace consumes WebBlocks and Resources MUST exist in the same Web Site. For example, RichWidgets must exist in all web sites if any of the eSpaces deployed there consumes it;

Note: You cannot delete the Application from the default web site (or rather, you can but next time you publish the eSpace the platform will re-create it) .


3. Zones & Multiple Frontends(IIS, JBoss, Weblogic)


You use the Zones feature of the OutSystems Platform to selectively deploy applications only to certain frontends. With this done you can configure specific website URLs for specific frontends.


As an example, you can configure frontend 1 to have all eSpaces from application A, and frontend 2 to have all eSpaces from application B. You could then configure frontend A to answer requests for URL and frontend B for URL


More information on Zones and their configuration in this post.


Hi João,

Great post! Which method would you recommend for someone who was using only the public cloud. It would have to be version 1, correct?
Hi GP, 

We recommend method 1, yes.

Method 3 will also work but requires intervention from OutSystems (to reconfigure the load balancers). I don't know if method 2 will be supported.