Glivent answers

What is the difference between Private, Hybrid and Cloud AI at Glivent?

Direct Answer

Private, Hybrid and Cloud describe where Glivent processes an approved AI task. Private AI runs the task on the onsite Glive Pod. Hybrid AI keeps selected work local and can redact sensitive details before using a cloud model. Cloud AI uses an approved enterprise provider while the Glive System continues to run on the Pod.

Private AI processing

Private AI runs approved model work on the Glive Pod inside the business. It gives the business a clear local processing boundary and avoids sending that task to a public AI model provider. It can also make costs more predictable for suitable recurring workloads because that processing does not attract a charge for every model token.

Hybrid and Cloud AI

Hybrid AI combines local control with the capability of an approved cloud model. Sensitive fields can stay on the Pod or be redacted before the cloud step, while the returned result comes back into the controlled workflow for review.

Cloud AI uses an approved enterprise provider for the model step. The Glive System still runs on the onsite Pod, so Glive Hub, Glive Flow, permissions and workflow records remain part of the same managed system.

How Glivent chooses

Glivent tests which option does the work well enough and then considers the information involved, processing location, connected software, expected usage, provider terms and total cost. The business sees the proposed data path and approves it before the workflow goes live.

Related guides

Learn more about this topic

More from Glivent

A practical first step

Find a practical place to start.

We review how work moves across the business, identify the strongest opportunities, and recommend a practical place to start.

Request an operational review