Get startedConnect infrastructure once. Score verifies it and publishes its exact capabilities to every compatible product surface.
Source reviewed 2026-09-23. Availability depends on your installation, permissions, and compatible runtimes. A supported path is not a guarantee of model quality or production readiness.
Start here
What you need to know first
Check the inputs below before starting. If you are new, begin with the first-project guide. A dataset holds media and labels; a model produces results; a deployment makes a selected model version callable. Creating one does not create the others.
Bring these inputs
- Provider endpoint and least-privilege credential
- A declared compute, inference, storage, or device capability
Expected output and limits
- A workspace-scoped connection
- Verified capabilities shared across every compatible feature
Core workflow
- 01
Choose a provider type
Customer-owned provider connections require Pro. Open your name at the top of the sidebar → Connections, then connect compute, inference, storage, or an edge runtime for the intended workload.
- 02
Add credentials
For provider-backed training, create an API key with the provider, then store the minimum required secret and confirm workspace scope. Provider usage is billed to that account.
- 03
Test the connection
Verify authentication, then publish the connection's supported product capabilities.
- 04
Use it across Score Studio
Select the same connection for compatible generation, training, segmentation, deployment, storage, and workflow actions.
What this surface supports
- Compute providers
- Inference providers
- Storage connections
- Edge devices
Expert section
Contracts, signals, and failure modes
Use this section when you are defining acceptance criteria, automating the surface, or reviewing whether its output is safe to promote downstream.
Expert release checklist
- Inputs and dependencies are pinned to immutable versions.
- Acceptance metrics include critical classes and operating slices.
- Failure, retry, cost, and rollback behavior are understood.
- The resulting artifact has an owner and a downstream review path.