For terms specific to one area, see the Governance glossary, the Audit Trail Data Glossary, and Default Domino Environment Variables.
AI Gateway (legacy)
A proxy between Domino and external LLM providers, such as OpenAI or AWS Bedrock. It routes requests through central credentials and logs every request. In Domino 6.3, AI Gateway is off by default and works only in deployments that enable it. Domino Cloud doesn’t include it. LLM Gateway 2.0 replaces it. See AI Gateway (legacy).API endpoint
Another name for a Domino endpoint. See Model deployment.App
An interactive web application that runs code from your Project. Each App runs in its own container, and Domino handles its routing, authentication, and resources. See Apps.App & Agent Hub
Where people in your organization find and use published Apps and agents. See the Domino overview.App instance
One run of an App version, from start to stop. An App has at most one running instance at a time. Domino records logs and resource use for each instance. See App versioning and reproducibility.App Preview
A private run of a Draft App, started from a Workspace, that only the App author can open. It doesn’t change the published App, but it isn’t sandboxed: it runs as the author, with real access to Domino APIs and shared data. See Develop and test an App.App version
An immutable snapshot of everything that defines an App: pinned source commits, Compute Environment and revision, Data Plane, mounted storage, and identity propagation. Publishing a Draft or changing any of these creates a version. Starting the App doesn’t. See App versioning and reproducibility.Approval
A sign-off on evidence that a governance stage requires before it’s complete. Approvals can also control moves between stages. See Governance.Audit Trail
Domino’s record of user activity across the deployment, for compliance, security investigations, and audit reporting. You can view it in the UI or query it through APIs. See Audit Trail.Bundle
A group of work items, such as models, files, and Apps, that you govern together. Policies apply to bundles, so anything you govern must be in one. Each bundle belongs to a Project. See Work with bundles.Checkpoint
A commit in a Workspace’s history that you can return to. Domino creates one each time you sync code or artifact changes. Recreating a Workspace from a checkpoint starts a new branch. See Create a Workspace from a checkpoint.Compute cluster
A Spark, Ray, Dask, or MPI cluster that Domino provisions on demand and attaches to a Workspace or Job. It runs on a Domino Cluster Environment. See On-demand distributed computing.Compute Environment
A versioned, shareable Docker image that defines the software every Workspace, Job, App, and model runs with. Domino starts a separate container from it for each execution. See Compute Environments.Control Plane
The Domino services and user interface that schedule and manage work across every Data Plane. See Data Plane.Data Plane
A Kubernetes namespace where Domino runs your workloads. The local Data Plane is in the same cluster as the Domino Control Plane; remote Data Planes are in other clusters, regions, or clouds. See Data Plane.Data Source
A saved connection to an external data system, such as a database, data warehouse, or data lake, that you can reuse in any Project. See Domino Data Sources.Dataset
Versioned, high-performance file storage in Domino for curating data and sharing it across Projects. See Datasets.Domino endpoint
A model deployed from a Project as an HTTP API. Clients send inputs and get predictions back, either in the response or, for long-running work, asynchronously by polling. See Model deployment.Domino File System (DFS)
Domino-managed file storage for Projects that don’t use a Git provider. Domino versions DFS files automatically and records a new Project version on every sync. See DFS Projects.Domino Nexus
The Domino capability to run workloads on multiple clusters, in any cloud, region, or on-premises location, by attaching remote Data Planes to one Domino Control Plane. See Data Plane.Domino skill
A packaged set of instructions that teaches a coding assistant a Domino task, such as submitting a Job, registering a model, or deploying an App. The Domino Standard Environment includes the skills from the publicdomino-claude-plugin repository, and coding assistants load them when they start in a Workspace. Skills are optimized for Claude Code. Anyone can contribute one through a pull request. See Domino skills reference.
Domino Standard Environment (DSE)
A Compute Environment included in every Domino installation, with preconfigured data science tools and libraries. You can use it for any Workspace, Job, App, or Domino endpoint. Domino updates it with each major release. See Domino Standard Environments.Draft App
A private, unpublished App linked to one Workspace, for development and testing. Domino creates it the first time you use App Preview in that Workspace and deletes it with the Workspace. Draft Apps don’t appear in App lists or search. See Develop and test an App.Evidence
The information a governance policy requires, usually answers to questions, collected as inputs, metric checks, or scripted checks. Each policy defines the evidence for each stage. See Governance.Experiment Manager
Domino’s experiment tracking, built on MLflow Tracking. It logs parameters, metrics, and artifacts, and stores them in the Project for reproducibility. See Track and monitor experiments.Extension
An entry point in the Domino UI that opens a Domino App. Extensions can appear in the Project sidebar, on Dataset or Model details pages, in the three-dot menu for Dataset files, or as a page in the Admin panel. One App can power several Extensions. See Create and manage Extensions.External data volume (EDV)
A network-attached storage volume that Domino mounts into every execution in the Projects you attach it to. See External data volumes.Finding
An issue raised while reviewing governance evidence. A finding belongs to one bundle and usually points to a specific piece of required evidence. See Governance.FinOps
Cost management for AI work, part of the Governance Center. See FinOps.Flow
A multi-step pipeline with full lineage and reproducibility. Each step, or task, runs as a Domino Job, and the tasks form a directed acyclic graph (DAG). See Flows.Gate
A governance control that blocks an action, such as deploying a published App, an agent, or a model endpoint, until required approvals are complete. See Governance.Git-based Project
A Project whose code lives in a repository at your Git provider. You branch, commit, push, and pull from your Workspace, and keep your provider’s review and collaboration features. Use a Git-based Project whenever you have a Git provider. See Git-based Projects.Governance Center
Domino’s governance capabilities: policies that enforce lifecycle standards, FinOps for costs, and the Audit Trail of platform activity. See the Domino overview and Governance.Hardware Tier
A named amount of CPU, memory, and GPU, on a specific node type, that you choose when you start an execution. See Hardware Tiers.HPC Job
A batch job that Slurm schedules on autoscaled worker nodes from inside Domino. Submit one from a Workspace with the Slurm CLI, or from the HPC tab on the Project’s Jobs page if an administrator enabled UI submission. See Run HPC workloads with Slurm.Job
A non-interactive, reproducible run of your code for batch and headless work. For interactive work, use a Workspace. See Jobs.Launcher
A web form that lets less technical users run a predefined task. Each form control, such as a text box or menu, supplies a parameter to the run. See Launchers.LLM Gateway 2.0
A gateway that centralizes access to external LLM providers, with usage tracking across users, Projects, and models, per-team and per-model budgets, guardrails that inspect prompts and responses, and broad model and vendor coverage. It replaces AI Gateway. Domino distributes LLM Gateway 2.0 as a binary that you deploy as a Domino App; contact your Domino field representative for access. See LLM Gateway 2.0.Model Monitoring
Tracking of deployed models for drift in input features and predictions, with alerts when a metric crosses a threshold you set. See Model Monitoring.Model Registry
Domino’s MLflow-based catalog of models, at Project and deployment scope. It records versions, metadata, lineage, and deployments, and controls access with Role-Based Access Control (RBAC). See Manage models with model registry.Namespace
A category in Domino’s tag structure, such asbusiness-domain or data-sensitivity. Each Namespace holds the Tags allowed as its values. See Tags.