IC 3.0 Shared Cloud Hosting
Shared Cloud is a multi-tenant Azure-hosted environment managed by Intranet Connections. Unlike Private Cloud, infrastructure resources are shared across customers while data remains logically isolated and secure. This approach allows customers to benefit from lower costs and simplified infrastructure management.
Fast. Scalable. Fully managed.
IC3.0 delivers a modern intranet on secure shared infrastructure so you get the latest features without the operational overhead. We handle the hosting, updates, and security, freeing your IT team to focus on what matters most.
Ready to move to the cloud?
Complete the form HERE
Want the full details?
Download the complete overview HERE
Built for organizations that want more with less
-
Lower total cost of ownership, with average savings of 30% (up to 40% for smaller teams*)
-
Vendor-managed security, maintenance, and monitoring
-
Rapid deployment with automatic upgrades and patches
-
Secure, scalable infrastructure that grows as you do
-
Reduced dependency on internal IT resources
*Compared to private cloud.
Everything included, no extra effort
-
Unlimited product support
-
Continuous access to new IC releases
-
Fully managed hosting and monitoring
-
Ongoing security hardening and performance optimization
Want to learn more? Check out our webinar recording here.
---
IC 2.0 Private Cloud vs. IC 3.0 Shared Cloud – FAQ
1. What are the primary infrastructure differences between IC 2.0 Private Cloud and IC 3.0 Shared Cloud?
Both are Windows-based IIS web applications hosted on Azure VMs, but have different underlying application technologies. 3.0 Shared Cloud supports multi-tenant hosting comprised of both a frontend application and backend API application supporting it. 2.0 main application service was Lucee/CFML with underlying Tomcat/Apache service. 3.0 is .NET/Blazor based and more native to Microsoft technologies. Both use SQL Server as a main database. 3.0 adds PostgreSQL as vectorized database to support the AI Search feature in 3.0.
2. In IC 3.0 Shared Cloud, is each customer’s environment/data isolated from other customers? How is that isolation maintained?
SQL Server databases are logically separated and securely accessed by unique logins for each customer. File data is managed by segregated disk folders that can only be accessed by their tenant. Applications in IIS are separate and uniquely bound to the unique customer URL, typically a subdomain of intranetconnections.com.
3. If an outage occurs in IC 3.0 Shared Cloud, would it impact all Shared Cloud customers or could it affect only an individual customer?
We recognize this may depend on the cause and type of outage. It would be helpful to explain the different scenarios—for example, an issue specific to one customer versus a broader infrastructure/service issue.
Yes, if it was a core infrastructure or underlying service experiencing an issue, like SQL Server stopped running or Azure had some disruption. If for example a specific web application or database stopped, that would affect the specific customer.
4. How does IC respond to and recover from an outage in IC 3.0 Shared Cloud compared with IC 2.0 Private Cloud?
For IC2 our backup/recovery was VM-level and using backup vaults (alternate Azure region) that could restore the whole infrastructure. For IC3 Shared Cloud, that same mechanism exists, but we can also backup/restore individual customer data/files/application vs the entire environment. How we would respond would depend on the outage situation or recovery need.
5. Does moving from IC 2.0 Private Cloud to IC 3.0 Shared Cloud introduce different infrastructure, availability, or security risks? If so, how are those risks mitigated?
Yes, as noted above, this requires additional controls and procedures to mitigate that such as data segregation, applications isolation/management, unique logins/passwords/keys, and additional backup/recovery methods.
6. How are backups, disaster recovery, monitoring, and infrastructure maintenance handled in IC 3.0 Shared Cloud compared with IC 2.0 Private Cloud?
This question appears to overlap question 4 with regards to backups and recovery. Monitoring and infrastructure maintenance is similar using RMM to maintain server patching, remotely monitor and alert, endpoint security. One difference is capacity monitoring and resource scaling is handled for all tenants vs a singular customer.
7. Who is responsible for infrastructure management and security in each hosting model?
IC is responsible and supported by a managed IT partner for Azure management in both cases. IC is responsible for security and governed by SOC II.
8. What information can we provide to the customer’s Risk/Compliance team to support their review of IC 3.0 Shared Cloud?
The main attestation is our official SOC II Type 2 report, which is very comprehensive and covers policies, controls, they system description, and tested and issued through external auditor.