What is SC Compute?
SC Compute is a virtual machine service that gives you access to remotely available servers over the internet. Think of it as renting a server in the cloud that you can use for whatever you need. Each compute instance comes with:- Customizable specifications - Choose CPU, RAM, and storage that fit your needs
- compute monitoring - Track performance metrics in real-time
- UI management - Control your instances (shutdown, reboot) directly from the dashboard
- Team collaboration - Share compute resources with your team members
Use Cases
SC Compute instances can be used for virtually anything you would do with your own server. Common use cases include:- Hosting websites and web applications - Deploy your frontend and backend applications
- Running web APIs - Serve REST APIs, GraphQL endpoints, or microservices
- Database hosting - Run MySQL, PostgreSQL, MongoDB, or other databases
- Development and testing environments - Spin up instances for testing and experimentation
- Batch processing and data analysis - Run compute-intensive workloads
- Custom services - Deploy any application or service that runs on Linux
Resource Lifecycle
Problem: What states can my resources be in, and what do they mean for access and billing? Different resource types may have different lifecycles. This section focuses primarily on compute instances as the most common example.Lifecycle States
Here’s the typical flow through lifecycle states:| State | Description | Web Dashboard | Resource Access (SSH/Console) | Billable? | Can Transition To |
|---|---|---|---|---|---|
| Creating | Initial provisioning when first created | Visible | Not accessible | No* | Running |
| Running | Normal operational state | Visible | Fully accessible | Yes | Stopped, Destroying |
| Stopped | Instance stopped but resources reserved | Visible | Not accessible | Yes | Starting, Destroying |
| Starting/Rebooting | Transitioning from Stopped or rebooting | Visible | Not accessible | Yes | Running |
| Destroying | Brief destruction process (seconds) | Visible | Not accessible | No* | Destroyed |
| Destroyed | Final state - all data permanently deleted | Not visible | Not accessible | No | None (irreversible) |
*Creating and Destroying states are not billable due to their very brief duration (typically seconds to less than a minute).
The Stopped state still incurs charges because resources remain reserved. To stop billing, you must Destroy the resource.

