The App Directory is a public listing of apps that your users can create integrations on. Integry hosts your App Directory, but you can choose its URL. This can be a subdomain of Integry, or a custom subdomain that you can create with your own app’s name in it. The default Integry subdomain will look like this:, while a custom subdomain will appear like this:

A custom subdomain will not have Integry’s name in it, but will still point to the Integry server to show the app directory UI. For setting it up, you first have to create your custom subdomain while setting up your Directory deployment. The details for that are mentioned here. After your App Directory on the custom subdomain is created, you can use the following procedure to make that subdomain work.

Configuring SSL Enabled Subdomain

SSL (or TLS), is the most widely used way to secure the connection between your server and your browser. It ensures the connection between the server and browser is encrypted and safe, and appears as HTTPS.

In this method, you’ll see the steps to install your own SSL certificate on your server and configure a subdomain. For this, you’ll need to acquire an SSL certificate and private key. You’ll then have to set up the proxy settings for your web server.

The subdomain that you configure should also be SSL enabled. This means that the SSL certificate installed on your server should be a wildcard certificate or should at least support one subdomain.

Your App Directory is hosted on Integry’s domain (that looks like After installing your SSL certificate, you’ll need to use your server's reverse proxy feature to render the UI of Integry’s App directory link (, when your custom subdomain is hit.

Setting up a reverse proxy

Let’s suppose that you’re using Apache web server for your site. You can set up the proxy settings for Apache by adding and editing a new configuration file. Follow the steps below to set up the reverse proxy to Integry on your server.

1. Create a record in the DNS settings for your domain.

2. Add your custom subdomain as a host (e.g.

3. Add the IP for your web server in the "Points to" field.

4. Create a directory for your subdomain to serve from, for example, "/var/www/". This is so that your web server can have a directory that will listen to the requests coming to the configured sub-domain.

After this, you will need to configure the virtual host for your subdomain.

5. Create a new configuration file in your proxy web server (Apache in this example). This can be like: /etc/apache2/sites-enabled/

6. Inside this file, add content similar to the following:

< VirtualHost *:80 >

DocumentRoot /var/www/
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME}
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

< /VirtualHost >

At this point, you can also install the SSL certificate manually if it is not already installed on the server. Let’s suppose that the SSL certificate is already installed.

7. Edit the above file and add the following content for the proxy settings:

< VirtualHost *:443 > 

ServerName # this is where you specify your custom domain
DocumentRoot /var/www/
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# Set SSL options for your own domain

SSLCertificateFile /etc/letsencrypt/live/
SSLCertificateKeyFile /etc/letsencrypt/live/
Include /etc/letsencrypt/options-ssl-apache.conf

# Proxy SSL options

SSLProxyEngine on
SSLProxyVerifyDepth 10
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off

# Set up the reverse proxy to Integry

ProxyPreserveHost On
ProxyPass /mysaas
ProxyPassReverse /mysaas

< /VirtualHost >

8. After following the above steps, restart your web server for the changes to take effect. Your custom domain will now be good to go.

Did this answer your question?