Deploy from the dashboard

  • Sign in to 1sc.dev and open Dashboard.
  • Select Deploy 5G core to open the deployment form. Choose the core implementation, radio source CIDR, data network, and radio transport.
  • Select Deploy 5G core to start the deployment.

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 stop
  • Runs this deployment end-to-end without interactive babysitting.
  • Turns on --json, so output is machine-readable.
  • Turns on --yes, so it skips the billable-action confirmation prompt.
  • Turns on waiting, so the command does not exit right after creating the deployment.
  • Turns on hosted attach verification, so after the core is ready it runs software radio validation.
  • Defaults cleanup to stop unless you change it.
Optional
true
Leave auto-detect off the command, or set a public radio source CIDR.Optional
Selects the hosted core runtime.Optional
Stops compute after verification by default.Optional

Approve the browser login if prompted. The example generates a name, deploys the core, verifies hosted attach, and stops compute afterward.

OptionRequiredDefault / optionsPurpose
--name <name>Required unless --agent is setAny deployment nameNames the deployment.
--agentOptionalFlagEnables JSON output, --yes, wait, hosted attach verification, and generated naming defaults.
--radio-source <cidr|auto>OptionalCIDR or autoRestricts N2/N3 access to the radio source. auto detects the caller's IPv4 /32.
--core <fivegc|free5gc|open5gs>Optionalfivegc, free5gc, open5gs; default fivegcSelects the hosted core implementation.
--verifyOptionalFlagWaits for readiness, then runs hosted attach verification.
--cleanup <keep|stop|destroy>Optionalkeep, stop, destroy; default keepKeeps, stops, or destroys the deployment after verification.
--timeout <duration>OptionalExample: 45m; default 30mSets the maximum wait time for readiness, attach verification, and cleanup.
--yesRequired unless --agent is setFlagConfirms the billable deployment action.
--api-url <url>OptionalURLOverrides the 1sc API URL.
--jsonOptionalFlagPrints JSON output.

Deploy from the API

POST/api/v1/deployments
terminal
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"
}'
Stored on the deployment record.Required
Required for the hosted launch path.Requiredtrue
Use auto-detect when the API caller and radio share the same public source.Optional
Selects the runtime to launch.Optional
Only the minimal SA lab profile is currently supported.Required
FieldRequiredDefault / optionsPurpose
nameRequiredAny deployment nameNames the deployment.
managedAwsRequiredtrueCreates and launches the managed AWS runtime.
radioSourceCidrOptionalEmpty string for caller IPv4 /32 auto-detect, or a public CIDRRestricts N2/N3 access to the radio source.
coreImplementationOptionalfivegc, free5gc, open5gs; default fivegcSelects the hosted core implementation.
coreProfileRequiredminimal-sa-labSelects the supported hosted lab profile.

Manage the deployment

Open Dashboard → Deployments to inspect status, endpoints, logs, attach results, and lifecycle controls.

Search commands, workflows, configuration, attach, API, and reports.