Development priorities
- Expanding our capabilities as a public cloud. We build core primitives for buying, managing, and orchestrating compute, then layer higher-level functionality on top.
- Increasing liquidity. If you have unused compute, you should be able to resell it and recoup some of your compute costs.
Feature states
Features move through the following states as they mature. A feature starts in development: we are building it, and it is not yet available. It then enters private preview. Selected customers get access, so we can validate the design with real usage before opening it more broadly. Email support@sfcompute.com to request early access. In public preview, the feature is available to everyone but may have rough edges. See Public preview support for what that means in practice. Generally available features are production-ready and fully supported under a stable API version prefix (the versioned URL path; see Using the API). Our uptime SLA covers them. When we retire a feature, it reaches planned end of life first. It still works, but you should migrate to the recommended alternative. At end of life, it is no longer available or supported.Public preview support
Preview features are available to everyone. Their API paths, response shapes, CLI flags, and error codes may change while the design settles. We support preview features on a best-effort basis, and our uptime SLA does not cover them.Public preview features
- Instance templates - define reusable instance configurations
- Deployments - automate instance creation and management
- Orderbook - view market depth and pricing
- Tags - organize resources with key-value pairs
- Reselling - resell unused allocation on the orderbook
Generally available features
- Pools - manage your compute allocation
- Orders - buy and sell compute time
- Instances - launch and operate GPU instances
- SKUs - pick the hardware your orders run on
- Images - build, upload, and manage custom images
- Workspaces - group resources to isolate teams or environments
- Resource paths - reference resources by name across the API and CLI