pricing

1ctl pricing lets you understand what resources cost before you commit to them. Satusky pricing is configured per-cluster and broken down into three dimensions: CPU-hours, memory GB-hours, and storage GB. Rates vary by region, machine type, and SLA tier.

Alias: 1ctl price

Pricing configurations are set by platform operators and are read-only for regular users. The calculate command is the practical one for day-to-day use: give it a machine, a start time, and an end time, and it returns the cost for that window.

Commands

`1ctl pricing list`

1ctl pricing list

Lists all pricing configurations available on the platform. Each configuration covers a region, machine class, and SLA tier combination.

$ 1ctl pricing list
ID          REGION      TYPE      SLA        CPU/HR    MEM GB/HR   STORAGE GB/MO
pconf_001   my-kul-1    standard  standard   $0.024    $0.004      $0.10
pconf_002   my-kul-1    premium   standard   $0.048    $0.008      $0.10
pconf_003   my-kul-1    standard  pro        $0.030    $0.005      $0.10
pconf_004   my-bki-1    standard  standard   $0.022    $0.004      $0.10

`1ctl pricing get`

1ctl pricing get --config-id <id>

Returns the full detail for a single pricing configuration.

Flags

Flag	Description
`--config-id <id>`	required — Pricing configuration ID from `1ctl pricing list`.

1ctl pricing get --config-id pconf_001

Example output:

ID:              pconf_001
Region:          my-kul-1
Machine type:    standard
SLA tier:        standard

Rates:
  CPU:           $0.024 per CPU-hour
  Memory:        $0.004 per GB-hour
  Storage:       $0.10 per GB per month

Guaranteed uptime (SLA):  99.5%

`1ctl pricing lookup`

1ctl pricing lookup --region <region> --type <type> --sla <tier>

Finds the pricing configuration that matches a specific region, machine type, and SLA tier. Use this when you know what you want to deploy and need the price before committing.

Flags

Flag	Description
`--region <region>`	required — Region identifier, e.g. `my-kul-1`.
`--type <type>`	required — Machine type, e.g. `standard` or `premium`.
`--sla <tier>`	required — SLA tier, e.g. `standard` or `pro`.

# What does a standard machine cost in KL?
1ctl pricing lookup --region my-kul-1 --type standard --sla standard

# Premium tier with pro SLA
1ctl pricing lookup --region my-kul-1 --type premium --sla pro

`1ctl pricing calculate`

1ctl pricing calculate \
  --machine-ref-id <id> \
  --machine-id <uuid> \
  --start <time> \
  --end <time>

Calculates the cost for a specific machine over a time period. Both --start and --end accept ISO 8601 timestamps.

This command is useful for estimating your bill before the billing cycle closes, auditing the cost of a specific machine, or modelling the cost impact of a resource change.

Flags

Flag	Description
`--machine-ref-id <id>`	required — Machine reference ID (the machine class/type identifier).
`--machine-id <uuid>`	required — UUID of the specific machine instance.
`--start <time>`	required — Start of the calculation window. ISO 8601 format: `2026-01-01T00:00:00Z`.
`--end <time>`	required — End of the calculation window. ISO 8601 format: `2026-02-01T00:00:00Z`.

# Calculate cost for January 2026
1ctl pricing calculate \
  --machine-ref-id mref_123 \
  --machine-id abc-def-uuid \
  --start 2026-01-01T00:00:00Z \
  --end 2026-02-01T00:00:00Z

Example output:

Machine:     abc-def-uuid (mref_123)
Period:      2026-01-01T00:00:00Z → 2026-02-01T00:00:00Z
Duration:    744 hours

Resource usage:
  CPU:       2.0 cores × 744h            = $35.71
  Memory:    4.0 GiB × 744h              = $11.90
  Storage:   20 GiB                      = $2.00

Total:       $49.61

How pricing works

Satusky bills by the hour for compute and by the month for storage. The formula for a billing period is:

cost = (cpu_cores × cpu_hours × cpu_rate)
     + (memory_gib × memory_hours × memory_rate)
     + (storage_gib × storage_rate_per_month × months)

Machines are billed from the moment they are provisioned until they are destroyed — not just when they are running workloads. If you provision a machine and leave it idle, you still accrue CPU and memory hours at the configured rate.

Credits in your organization balance are consumed first. When the balance reaches zero, new machine provisioning is blocked. Add credits via the dashboard. Older/internal docs mention 1ctl admin credits add; that is platform-operator context and was not present in the current user-facing CLI help verified for v0.8.3.