Considerations for Self-hosting

  • Updated

Deployment in Azure

There are two methods available for deploying self-hosted Decision Services:

  • Use the InRule listing on Azure Marketplace
    Azure Marketplace offers a simpler, UI-driven process that guides you through deployment. 
  • Deploy using the provided ARM template
    A deployment using the ARM template will provide you more control over settings and configuration.



For a self-hosted deployment of Decision Services, you will need to include the API key provided during the deployment configuration as the “inrule-apikey” header value on your requests to be able to authenticate to the service.

Example: “inrule-apikey”: “yourapikey”


If you want to make use of the Swagger UI for your Decision API, you will need to include the API key as a query string in the URL. The query string key should be the API key and the value will be your API key. Below you can see an example of a URL that includes the query string.

Sample URL.png

  1. Replace the <domainname> with the default domain listed on the overview page of your deployed resource.
  2. Replace the <apikey> with the API Key value you included in the configuration when deploying your self-hosted Decision Services.

Health check configuration

Health check will be automatically enabled and configured for self-hosted deployments of Decision Services. By default, the health check will be directed at the API/status/alive endpoint.
If you would like to change the health check configuration, you will need to navigate to the overview page of your deployed resource and click the link displaying the health status.

Health Check.png

This will take you to the health check configuration page where you can

  • Enable/Disable the health check
  • Change the endpoint being called
  • Set the load balancing for unhealthy instances

Health Check Configuration Page.png


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.