Splunk Cloud Platform operates in two architectural generations: the legacy Classic Experience and the modern Victoria Experience. Understanding which experience your stack runs determines where apps install, how index-time configurations propagate, and whether an Inputs Data Manager (IDM) exists.
In the Victoria Experience, Splunk eliminates the separate IDM node and executes modular and scripted inputs directly on the Search Head or Search Head Cluster (SHC) tier. When you install an app via Self-Service App Install (SSAI) or the Admin Config Service (ACS) API on Victoria, Splunk automatically distributes it across all search heads (including premium stacks) and pushes index-time configurations such as props.conf, transforms.conf, and indexes.conf to the indexer tier.
In the Classic Experience, modular and scripted inputs run on a dedicated managed IDM tier rather than on the search heads, and app deployments or index-time configuration updates frequently require Splunk Support tickets or separate tier coordination. Additionally, Victoria restricts downloading previously uploaded apps back out of the Splunk Web UI.
# Victoria Experience app installation
POST https://admin.splunk.com/{stack}/adminconfig/v2/apps/victoria
# Classic Experience app installation
POST https://admin.splunk.com/{stack}/adminconfig/v2/apps