V2 API and CLI still in public preview#

The v2 API and CLI remain in public preview. Preview endpoints are still served under /preview/v2/*. To learn more about public preview, read about our roadmap and feature states here.

The legacy API still works but is being phased out. Plan to migrate off it soon.

If you're new to v2, get started using the quick start guide.

Nodes are now Instances#

"Nodes" previously referred to both the physical hosts and the VMs running inside them. In v2, we now refer to them using distinct terms:

• Node — the physical machine purchased by an order
• Instance — the VM you launch, SSH into, and run workloads on

We've renamed our CLI, API, and wire formats to match:

• sf nodes … → sf instances …
• sf node-templates … → sf instance-templates …
• /preview/v2/nodes → /preview/v2/instances
• node_template → instance_template
• target_node_count → target_instance_count
• node_name_template → instance_name_template

In the v2 CLI, the sf nodes alias is gone - update your scripts to use sf instances. The legacy /v1/nodes API remains untouched. To migrate active legacy v1 nodes to v2 instances, run sf nodes migrate in the v2 CLI.

Capacity transfers#

Transfers move nodes between two of your capacities for a specified window.

# Using the v2 CLI
sf capacities transfers create \
  --from-capacity dev \
  --to-capacity prod \
  --start-at "tomorrow" \
  --end-at "in 7d" \
  --node-count 4 \
  --instance-sku isku_4UpxzQw7A8N

sf capacities transfers get <transfer-id>
sf capacities transfers list --capacity dev

Use capacity transfers to isolate compute time so you can resell time in one capacity without affecting the instances in the other.

A capacity with pending transfers can't be deleted until the transfers have settled.

Orderbook API#

The Orderbook API exposes a live record of every standing buy and sell order on the market.

Use it to price a specific delivery window before you place an order, discover what hardware is on offer and at what rate, or feed live supply and demand into trading bots, dashboards, and analytics.

V2 API and CLI in preview#

Our rewritten CLI and API are now in preview, built on a new mental model for managing compute that adds reselling support. Get started using the docs.

The new CLI and API are separate from the existing legacy API, which will continue to be supported as we continue to iterate.

Resell unused compute to recoup costs#

If you have more compute than you need, you can sell it back. Once your order fills, credits are added to your balance.

# Place a buy order
sf orders create --side buy --capacity my-capacity \
  --nodes 4 --start now --duration 24h \
  --max-rate '$25.00'

# Sell back unused allocation
sf orders create --side sell --capacity my-capacity \
  --nodes 4 --min-rate '$20.00'

CLI Rewrite#

We've rewritten our CLI in Rust for speed. The new CLI uses different command syntax, so some commands from the previous CLI won't work without changes.

If you forget to pass required flags on a command, it'll prompt you for what it needs.

Nodes now attach to Capacities#

Attach a node to a capacity and it runs as long as allocation is available. If there's no allocation yet, it enters an awaiting state and starts automatically when capacity becomes available.

# Create a node
sf nodes create --capacity my-capacity \
  --image ubuntu-22.04.5-cuda-12.7

Automate managing compute with deployments and procurements#

Use deployments to keep a target number of nodes running. Use procurements to buy and sell automatically within price bounds.

# Keep 4 nodes running at all times
sf deployments create --capacity my-capacity \
  --node-template my-template \
  --target-node-count 4

# Scale up
sf deployments set my-deployment --target-node-count 8

# List deployments for a capacity
sf deployments list --capacity my-capacity

# Automatically buy and sell within price bounds
sf procurements create --capacity my-capacity \
  --target 4 --window 1h \
  --max-buy-price '$25.00' \
  --min-sell-price '$20.00'

# Pause a procurement
sf procurements set my-procurement --enabled false

Node Templates#

Node templates let you define an image and startup script once, then reference the template in deployments or when creating nodes.

# Create a template
sf node-templates create --name my-template \
  --image ubuntu-22.04.5-cuda-12.7 \
  --cloud-init ./startup.sh

# List templates
sf node-templates list

Tag nodes and capacities#

Tags are key-value pairs you can use to organize and filter nodes and capacities.

# Add a tag
sf nodes set my-node --tag env=prod

# Filter by tag
sf nodes ls --tag env=prod

CLI sf images command#

Uploading and managing custom OS images is now available as a top-level CLI command.

# List available images
sf images list

# View image details and download URI
sf images get <image-id>

# Upload a custom image
sf images upload ./path/to/os.img

Live system status#

The landing page footer now describes real-time system status, including incidents and upcoming maintenance.

Clicking on the footer navigates to our status page.

Sunsetting Large Scale Inference#

We have sunsetted LSI batch inference to better support the great inference providers running on SFC.

Legacy VMs purchase flow deprecated#

sf buy, sf sell, and sf extend have been removed in CLI v0.30.0. Use the Nodes API and sf nodes commands to explicitly spin up, extend and release specific nodes instead.

Transaction history cutoff beyond June 10, 2025#

For older records, contact us.

Custom images for Nodes#

• Pre-configure Nodes with your own software and dependencies
• Supports any UEFI bootable x86_64 raw image

# Upload a custom image
sf nodes images upload ./path/to/os.img

# Create a node with the custom image
sf nodes create -n 1 --image <image-id> --zone landsend --max-price 30

Read the custom images documentation for more info.

Large Scale Inference (LSI) dashboard improvements#

Jobs and usage are now in a single tab, with a reworked job details view.

Create API keys in the dashboard#

API keys support custom expiration (e.g., 1d, 30d, 60d) and descriptions.

View, manage and create API keys via the dashboard here.

Zone availability summary#

The dashboard and CLI now show an availability summary for each zone, giving you a clearer picture of capacity at a glance.

 

Calling sf zones ls without --all in the CLI will only show zones with current and upcoming availability.

B200 and B300 GPUs now available#

We've added NVIDIA B200 and B300 GPUs to our fleet. Contact us to learn more.

Large Scale Inference (LSI) dashboard released#

The LSI batch inference dashboard is now generally available.

• Usage: Batch usage and billing data with day/week/month views
• Jobs: Paginated list with request counts and statuses
• Models: Available models and their pricing
• API keys: Create, view, and revoke API keys

Access LSI via the dashboard.

Reworked zones page#

The zones page now shows more detailed capacity availability information, with clearer hour boundaries for planning your workloads.

Dashboard creates Nodes instead of legacy VMs#

When you launch a node through the dashboard, it will now create a Node and not a legacy VM.

This means you can use the sf nodes CLI commands to explicitly manage your compute.

We're continuing to deprecate legacy VMs across the platform in the coming weeks. Please migrate your workloads to Nodes as soon as possible.

Automatically select the cheapest zone#

You can now create Nodes in the cheapest zone that meets hardware requirements.

In the API, add the any_zone parameter to your Node creation request. See the API documentation for request parameters.

The --any-zone flag has been added to the CLI to allow Nodes to be created in the cheapest zone that meets hardware requirements.

# Create Nodes with automatic zone selection
sf nodes create my-node-name --any-zone -d 1d -p 10.00

# Zone information shown in CLI output
sf nodes ls
sf nodes ls --verbose

Nodes created with --any-zone show "Any matching" in sf nodes ls until they are assigned to a specific zone. Reserved Nodes show the assigned zone immediately.