Core concepts

This page describes the core concepts that underpin Foundry DevOps and Foundry Marketplace. We recommend that you read this page before proceeding since Foundry DevOps and Marketplace use specialized terminology (such as "product").

Product

In Foundry DevOps, "products" are collections of Foundry resources that a product builder has made available to install. Builders can create new products in Foundry DevOps.

Example product types include:

• Ontology: An instance of the Foundry Ontology, whether a comprehensive standard industry ontology or an ontology fragment.
• Use Case: A use case can be as simple as a single Workshop application or could involve a combination of multiple Workshop applications, functions, and Carbon workspaces.
• Pipeline: Pipelines can range from a single data transformation all the way to a group of many transforms and data connections in sequence.
• Modeling: A containerized executable model encapsulating any functional logic, including machine learning, forecasting, optimization, physical models, and business rules.

Each product has outputs, or content, that are produced when the product is installed. Products may require that installers map inputs in order to produce output content.

Products are the atomic unit that users can browse and install via the Marketplace storefront.

Product version

Product builders create and publish new versions of products every time they want to adjust existing product content or add new product content. When installing, we typically recommend choosing the latest product version. When new product versions become available, installers can upgrade manually or opt to receive new versions automatically.

Store

Stores are collections of products; these products typically have a shared purpose. Product builders can publish new products to stores. Stores that appear on your Foundry instance may be local (for instance, produced by a builder within your organization who works on your Foundry instance) or remote (for example, the Foundry Store that is available to all Foundry users and maintained by Palantir).

Installation

An installation is created when an installer fulfills the required inputs (if any) for a product. Each product can be installed multiple times. Multiple installations are typically created when:

• A product is required for different user groups. For example, you might install a ticket management product across a variety of support teams, using their ticketing data as input.
• You need to create an installation for different development environments. For example, you might install a ticket management product into a pre-production space and ontology, and again into a production space and ontology, each with their own input data and environment-specific settings like release channels and upgrade windows.