Create a hosted core
Deploy a managed 5G core from the dashboard, CLI, or API.
Deploy from the dashboard
- Sign in to 1sc.dev and open Dashboard.
- Under Deploy 5G Core, fill out your preferences.
- Click Deploy 5G Core.
The deployment page opens automatically and shows launch progress, endpoints, logs, and attach evidence.
Deploy from the CLI
terminal
npx @1sc-hq/1sc deploy \
--agent \
--core fivegc \
--cleanup stopApprove the browser login if prompted. The example generates a name, deploys the core, verifies hosted attach, and stops compute afterward.
| Option | Required | Default / options | Purpose |
|---|---|---|---|
| --name <name> | Required unless --agent is set | Any deployment name | Names the deployment. |
| --agent | Optional | Flag | Enables JSON output, --yes, wait, hosted attach verification, and generated naming defaults. |
| --radio-source <cidr|auto> | Optional | CIDR or auto | Restricts N2/N3 access to the radio source. auto detects the caller's IPv4 /32. |
| --core <fivegc|free5gc|open5gs> | Optional | fivegc, free5gc, open5gs; default fivegc | Selects the hosted core implementation. |
| --verify | Optional | Flag | Waits for readiness, then runs hosted attach verification. |
| --cleanup <keep|stop|destroy> | Optional | keep, stop, destroy; default keep | Keeps, stops, or destroys the deployment after verification. |
| --timeout <duration> | Optional | Example: 45m; default 30m | Sets the maximum wait time for readiness, attach verification, and cleanup. |
| --yes | Required unless --agent is set | Flag | Confirms the billable deployment action. |
| --api-url <url> | Optional | URL | Overrides the 1sc API URL. |
| --json | Optional | Flag | Prints JSON output. |
Deploy from the API
- Create an Operator API token, store it in ONE_SC_API_TOKEN, then create the deployment.
POST
/api/v1/deploymentsterminal
curl --fail-with-body https://www.1sc.dev/api/v1/deployments \
--request POST \
--header "Authorization: Bearer $ONE_SC_API_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"name": "radio-lab",
"managedAws": true,
"radioSourceCidr": "",
"coreImplementation": "fivegc",
"coreProfile": "minimal-sa-lab"
}'| Field | Required | Default / options | Purpose |
|---|---|---|---|
| name | Required | Any deployment name | Names the deployment. |
| managedAws | Required | true | Creates and launches the managed AWS runtime. |
| radioSourceCidr | Optional | Empty string for caller IPv4 /32 auto-detect, or a public CIDR | Restricts N2/N3 access to the radio source. |
| coreImplementation | Optional | fivegc, free5gc, open5gs; default fivegc | Selects the hosted core implementation. |
| coreProfile | Required | minimal-sa-lab | Selects the supported hosted lab profile. |
Manage the deployment
Open Dashboard → Deployments to inspect status, endpoints, logs, attach results, and lifecycle controls.