Platform overview / Deployment options

Deployment options

Compare the two SPICE™ deployment models, then review the architecture, integration and responsibilities behind them.

Talk to a platform specialist

Deployment models

Run SPICE™ where your infrastructure already is.

Two deployment models, one platform. Choose the one that fits your IT and security requirements.

SPICE™ cloudYour ERPSpicY™ AITrading partners

Model 1

SaaS

SPICE™ runs, secures and updates the platform for you.
How most customers run SPICE™.

Your cloudYour ERPSpicY™ AITrading partners

Model 2

BYOCBring your own cloud

The full SPICE™ platform, deployed in your own Azure or AWS account, including Azure Government.
Your security boundary, data residency and controls.
Deployed by SPICE™ in your Azure or AWS account. Who handles infrastructure, access, monitoring, updates and support is agreed in the architecture review.
Built for defense and regulated industries, open to any enterprise that wants to run in its own cloud.

SaaSBYOC

Where it runsThe SPICE™ cloudYour Azure or AWS account, including Azure Government

Who manages the infrastructureSPICE™Agreed in the architecture review

Security boundaryThe SPICE™ cloud, secured and updated by SPICE™Your boundary, data residency and controls

Typical fitA managed, cloud-first environmentDefense, regulated industries and any enterprise that runs its own cloud

Defense & regulated industries

Modern microservices inside your cloud boundary

SPICE™ BYOC is the same cloud-native, microservices-based platform architecture used for SPICE™ SaaS, designed for this delivery model.

Customer cloud boundary Application compute and customer data can remain within your Azure or AWS boundary.
Dedicated environment Each BYOC deployment is a dedicated, single-tenant environment isolated from other SPICE™ customers.
Microservices architecture Services can be operated and scaled independently to support resilience and controlled change.
Enterprise integration API-first services connect ERP, WMS, TMS and B2B systems through governed interfaces. See security and integrations.
Regulated environments Support data-residency and infrastructure-control requirements, including Azure Government where required.
One platform model The same SPICE™ processes, trading partner model and product capabilities across SaaS and BYOC.

Choose BYOC when the cloud boundary is part of the requirement

Use BYOC when regulatory, security or data-sovereignty requirements mandate that application resources and data remain within your organization’s cloud boundary.
In both models, native middleware maps, validates and routes X12, EDIFACT, IDoc, XML, JSON, CSV and flat-file transactions.
Define access, monitoring, update and support responsibilities during the architecture review.

Whichever model you choose, the SPICE™ team designs, implements and supports your program, and SPICE Connect™ can take on trading partner onboarding and day-to-day operations. See managed services and the glossary entry BYOC vs SaaS.

The SPICE™ platform

One platform between your ERP and every trading partner

Suppliers, customers, carriers and 3PLs connect through one governed platform, with your ERP as the system of record. Select any part to explore it.

Your ERPWMS · TMS · OMS stay the system of record

SuppliersProcure-to-pay SPICE Web OMS™Supplier collaboration without EDI

SPICE™Supply Chain Collaboration Platform

SPICE DDS™Documents in, transactions out SPICE Catalog™Product data in, validated SPICE iKompli™Trading partner certification

SPICE Insight™Visibility across every transaction SPICE Connect™The managed team around it

Customers, dealers & retailersOrder-to-cash SPICE Trade™B2B ordering for non-EDI customers

Carriers & 3PLsLogistics

FAQ

Frequently asked questions

What is cloud EDI?

Cloud EDI is EDI software delivered as a service, so you exchange transactions with trading partners without installing and running EDI infrastructure yourself. SPICE™ offers cloud EDI as part of a broader collaboration platform that also covers non-EDI trading partners, orchestration, and visibility with exception management across procure-to-pay, order-to-cash and logistics.

Can SPICE™ run in our own cloud?

Yes. With BYOC (bring your own cloud), SPICE™ deploys a dedicated, single-tenant instance of the complete platform inside your Azure subscription or AWS account, including Azure Government where required. Application compute and your data can remain within your boundary. Who handles infrastructure, access, monitoring, updates and support is agreed in the architecture review. The products and processes are the same as in SaaS.

Which deployment model should we choose?

Most customers choose SaaS for a managed, cloud-first environment. Choose BYOC when regulation, security policy or data-sovereignty rules require your applications and data to stay inside your cloud boundary, or when you want the platform in your own cloud. An architecture review agrees who is responsible for access, monitoring, updates and support.

Do features differ between SaaS and BYOC?

No. The same SPICE™ processes, trading partner model and product capabilities are available in each model. What differs is where the platform runs. Any requirement specific to your environment, such as integration endpoints or update scheduling, is confirmed during the architecture review.

Talk to a platform specialist

Review the right deployment model

Bring your security, data-residency and cloud requirements.

Prefer to call or email? Contact SPICE™