Deployment

Flexible deployment. Full control where it matters.

CXFabric can run in the model that fits the customer: shared cloud for speed, dedicated VPC for isolation, or self-hosted and on-prem deployment for maximum control over security, data, and infrastructure.

Shared cloud Managed VPC Self-hosted cloud On-premises
FastShared cloud tenantmanaged
PrivateDedicated VPC environmentisolated
OwnedCustomer cloud or on-premcontrolled
OpsLogs, credentials, workers, flowsobservable

Deployment options

Choose the boundary. See who operates what.

Compare the speed, isolation, connectivity, and operating ownership of each deployment model. The CXFabric workflow model remains consistent while the infrastructure boundary changes.

Shared cloud

Move from evaluation to a working tenant quickly.

A CXFabric-managed environment for suitable pilots, smaller deployments, and teams that prefer infrastructure operations to remain with CXFabric.

Infrastructure
CXFabric managed
Isolation
Tenant boundary
Connectivity
Public and approved endpoints
Best fit
Fast start and lower operational lift
CXFabric cloudManaged runtime
APIsSystemsLogs

Operating ownership

Move the boundary. Keep responsibilities explicit.

Deployment choice is also an operating decision. Infrastructure, network access, scaling, credentials, logging, upgrades, and support need named owners before production begins.

Deployment outcomes

Different boundaries. The same production discipline.

Whichever model fits, the deployment should remain observable, adaptable, and operationally clear.

Observable

Understand executions and runtime health.

Keep flow history, errors, connector activity, timing, and support context available to the operating team.

Adaptable

Match connectivity and scale to the environment.

Adjust runtime layout, workers, network paths, and support patterns as the implementation grows.

Predictable

Agree on responsibility before launch.

Make infrastructure, operations, upgrades, credentials, evidence, and recovery part of the deployment plan.

Deployment planning

Bring the environment.We will map the operating model.

Start with the systems, data, network boundaries, and ownership requirements that matter to the implementation.