Self-Hosted CRMJetty Portal Architecture Explained
When you host CRMJetty Portal yourself, you run the same parts the CRMJetty cloud runs, in your own Azure subscription or on your own server. Knowing the parts helps you size the environment, plan backups and talk to the CRMJetty team about deployment.
Note: This feature is available on selected plans. See Pricing.
The parts of a portal instance
| Part | What it is | Hosted as |
|---|---|---|
| CJ Web | The portal website. Portal users sign in here, and admins reach the admin portal. | Azure App Service, or a site in IIS |
| CJ API | The portal API that the website calls. Its URL is configured in the portal website. | Azure App Service, or a site in IIS |
| CRM API | The API that connects the portal to your CRM. | Azure App Service, or a site in IIS |
| Portal database | One MS SQL database used by the CJ website. It holds the portal’s own layer: portal user accounts and credentials, session and OTP data, and configuration and layouts. On a server, SQL Server Standard or SQL Express. | Azure SQL database, or SQL Server with SQL Authentication |
| CRMJetty solution (Dynamics 365) | The solution imported into Dynamics 365 so the portal can work with it. | Your CRM |
Your CRM records are not copied into the portal database. The portal fetches them from your CRM on demand, so your CRM stays the system of record.
How the portal reaches your CRM
The portal connects to your CRM with the details you enter under Settings → Portal Settings → CRM Authentication in the admin portal (Business Central Authentication for Business Central). Until you complete this step after deployment, the portal does not work.
| Your system | How the portal connects |
|---|---|
| Dynamics 365 Online | OAuth, using an app registered in Microsoft Entra ID (formerly Azure Active Directory) |
| Dynamics 365 on-premises (IFD) | Credential |
| Salesforce | A Salesforce connected app over OAuth 2.0 |
| Business Central | An app registered in Microsoft Entra ID, with its Client ID, Client Secret and Tenant ID |
See CRM Connection Requirements for CRMJetty Portal.
The portal syncs with your CRM; timing depends on your CRM’s API limits. See How CRM Data Sync Works in CRMJetty Portal.
Sandbox and live instances
A sandbox and a live portal are two separate instances. Each has its own CJ Web, CJ API, CRM API and database.
| Setup | App services or IIS sites | Databases |
|---|---|---|
| Live only | 3 | 1 |
| Sandbox and live | 6 | 2 |
See How to Switch the Portal Between Sandbox and Live CRM.
Azure compared with your own server
| Azure | Virtual machine or server | |
|---|---|---|
| Applications run as | Azure App Service | Sites in IIS |
| Database | Azure SQL (MS SQL) database | SQL Server Standard or SQL Express |
| Server software you install | None | IIS, IIS Hostable Web Core, .NET Hosting Bundle, SQL Server |
| Scaling | Scale the App Service plan up as traffic grows | Upgrade the server |
| Operating system and security patches | Managed by Azure | Your responsibility |
| Typical monthly maintenance (estimate from CRMJetty’s hosting guide) | About 8 hours | About 12 hours |
| Encryption at rest | Yours to configure and check | Yours to configure and check |
Who sets up what
- You provide the Azure subscription or server, the domain and SSL certificate, and install the prerequisites.
- The CRMJetty team deploys the applications and the database, using temporary access to your Azure details or the published code folders and database script on your server.
- You install the CRMJetty solution in Dynamics 365, if you use it, and connect your CRM in the admin portal.
Related articles
- How to Host CRMJetty Portal on Azure or a Virtual Machine
- How to Set Up IIS for a Self-Hosted CRMJetty Portal
- CRMJetty Portal Server Requirements and Azure Sizing
- CRMJetty Portal Security and Data Protection