Platform

Choose hosted or on-premises iService deployment

iService runs as a managed service or on your own infrastructure. IT and security teams choose hosted or on-premises deployment for their security, data residency, and local access requirements. Cloud, private, and on-premises deployments use one codebase and one upgrade path.

Two mirrored deployment environments of equal size, one resting on a cloud form and one on a customer building

Hosted and on-premises deployment

IT and security teams set hosting, data location, and access requirements for iService.

iService runs as a hosted service or on your own infrastructure. You choose the deployment path for your hosting, data location, and control requirements. Both paths run the same iService product for teams with different infrastructure policies.

A customer-controlled boundary enclosing the service, with one keyed gateway out to an external AI provider

On-premises iService setup

On-premises iService runs on your equipment with a website domain, DNS mapping, and local access instructions.

For on-premises deployment, you run iService on your equipment, add your website domain, and map DNS to the iService web server. You provide local access instructions for users. Cloud, private, and on-premises installations use the same codebase and upgrade path. Your hosting choice retains the same iService product.

One shared set of capabilities delivered identically to a hosted and an on-premise environment

Local access for on-premises iService

An IT team configures local access to an on-premises iService installation.

An IT team selects on-premises deployment and runs iService on its equipment. The team adds a website domain, maps DNS to the iService web server, and provides local access instructions. Users access the same iService product, codebase, and upgrade path used for cloud and private deployment.

One product and upgrade path

Cloud, private, and on-premises teams run the same iService product and upgrade path.

iService runs the same product as a managed service and inside your environment. Cloud, private, and on-premises deployments share one codebase and one upgrade path. Hosted customers move to an on-premises installation when their hosting requirements change.

Deployment path for security and data residency

Security and data residency requirements determine the iService hosting path.

iService supports hosted and on-premises deployment. You select the path that meets your security and data residency requirements. Hosted customers move to an on-premises installation when infrastructure requirements change.

Discuss iService deployment options

Discuss the hosted or on-premises path that meets your security, data residency, and local access requirements.

Discuss deployment