SuiFleet Launch app

Product walkthrough

Product guide

New? Watch how it works first →
Read the stages below. Interactive navigation becomes available when the guide loads.
Narrated testnet demo · 2026-11-05Download video

Sign in

Overview

Open the console and connect an account. You can use the Slush web wallet with no extension, an installed Sui wallet extension, or Google sign-in where the build enables it. The first time, you create your fleet; that is the only transaction in this step.

Open Get started ↗
  1. Open the console and connect an account. You can use the Slush web wallet with no extension, an installed Sui wallet extension, or Google sign-in where the build enables it. The first time, you create your fleet; that is the only transaction in this step.
  2. A Sui wallet, or a Google account if Google sign-in is offered.
  3. Open the console and click Connect Wallet at the top right.
  4. Pick Slush, your extension wallet or Google, and approve the connection.
  5. On your first visit, choose Create default fleet in the fleet selector and approve the request. A fleet is your device workspace; choose it before continuing.
  6. Choose Get started in the sidebar: it shows your account, short address, the network (Testnet in the preview) and the next onboarding step.
  7. The console shows your connected address, your selected fleet and the next onboarding step.
Narrated testnet demo · 2026-11-05Download video

Enable device capacity

Overview

A subscription provides places for devices. It is separate from the account fees for approvals and the fleet budget for device activity. Check capacity before depositing operating funds. This preview uses a disposable test tariff and free test tokens, not real purchases.

Open Plans and billing ↗
  1. A subscription provides places for devices. It is separate from the account fees for approvals and the fleet budget for device activity. Check capacity before depositing operating funds. This preview uses a disposable test tariff and free test tokens, not real purchases.
  2. Connect and choose your fleet.
  3. Obtain free test SUI for approvals. An organization administrator must choose the plan.
  4. Open Device capacity to check how many device places are available.
  5. Open Plans and billing, select a reviewed offer and read its device limit, term, token amount and verified payment recipient.
  6. Approve prepayment from your connected wallet. Wait for verified confirmation before retrying.
  7. Apply the due prepaid payment to activate capacity. This uses the existing subscription balance, with a separate network fee.
  8. Return to Device capacity and verify the new limit.
  9. The organization’s device limit increases. No device has been registered, connected or updated by buying capacity.
Narrated testnet demo · 2026-11-05Download video

Fund the network budget

Overview

The fleet budget pays the network fees for device reports. Storage funding pays for uploaded files and logs where enabled. These balances are separate from your subscription and device capacity. Depositing funds requires your approval.

Open Network budget ↗
  1. The fleet budget pays the network fees for device reports. Storage funding pays for uploaded files and logs where enabled. These balances are separate from your subscription and device capacity. Depositing funds requires your approval.
  2. SUI in the connected account. On testnet, request it from the Sui faucet; the console shows the address to fund.
  3. Choose Network budget in the sidebar.
  4. Enter Deposit (SUI) and click Deposit, then approve. If this build offers Create budget and deposit instead, enter the Initial deposit first.
  5. Later deposits use the Deposit button. Open Device balances, spending limits and withdrawals to cap or withdraw per-device funds.
  6. Optionally create fleet storage under Storage funding to prepay Walrus storage for uploads and log archives.
  7. A Confirmed message with the transaction digest, and the new balance under Keep devices reporting.
Narrated testnet demo · 2026-11-05Download video

Register a device

Overview

Install the SuiFleet client on the device, then register the public address it supplies. The private device key stays on the device; never paste it into the console. Registration gives your account permission to manage that device.

Open Devices ↗
  1. Install the SuiFleet client on the device, then register the public address it supplies. The private device key stays on the device; never paste it into the console. Registration gives your account permission to manage that device.
  2. Available device capacity for your organization. A funded network budget does not increase your device limit; check Device capacity or Plans and billing first.
  3. The device's address, printed by suifleet --derive-address /etc/suifleet/device.key on the device.
  4. Choose Devices in the sidebar and click Register by address.
  5. Enter a Device name, paste the Device SUI address and pick the Architecture.
  6. Click Register and approve the transaction.
  7. The device appears in the list. It shows as not yet reporting until its client starts and sends a signed report.
  8. A new device row with its name, architecture and address.
Narrated testnet demo · 2026-11-05Download video

Enroll a batch

Overview

Optional for larger fleets: enroll devices in batches instead of copying each public device address. Each device receives its own enrollment credential. Start with single-device registration for your first pilot.

Open Enrollment ↗
  1. Optional for larger fleets: enroll devices in batches instead of copying each public device address. Each device receives its own enrollment credential. Start with single-device registration for your first pilot.
  2. A roster (CSV of names and serial numbers), or a single device to pair.
  3. Choose Enrollment in the sidebar. Under 1. Enrollment batch policy, set a Quota and Valid for days, then click Create policy.
  4. Under 2. Reserve names and serial numbers, paste a roster CSV (or use Pair one device), optionally pick a Default group, and click Check.
  5. Click Download credentials. This file is the only copy of the claim keys; store it with your factory image tooling, never in source control.
  6. Under 3. Register claims, click Run pending transactions and approve each transaction. Devices then enroll themselves with suifleet --enroll.
  7. Entries move from Reserved to Waiting for device, and to Enrolled when each device claims its record.
Narrated testnet demo · 2026-11-05Download video

Publish a version

Overview

A version is a named component with one artifact per platform and a recipe describing how to install and run it. The browser encrypts both before uploading them to Walrus and records their digests on chain.

Open Components ↗
  1. A version is a named component with one artifact per platform and a recipe describing how to install and run it. The browser encrypts both before uploading them to Walrus and records their digests on chain.
  2. The artifact file for each platform.
  3. An access policy (Access policies page) naming who may decrypt it, for confidential delivery.
  4. Choose Components in the sidebar. The first time, click Set up publishing to create your publisher catalog.
  5. Click Publish version, enter the Component name and Semantic version, and continue.
  6. For each platform choose the Operating system and Architecture, attach the Artifact and, if needed, an Install command.
  7. Under Delivery keep Confidential and choose the Access policy for proprietary software. The scripted testnet demo chooses Public (unencrypted) and confirms that its example artifact contains nothing confidential.
  8. Click Review version, then Upload and publish version, and approve the transaction.
  9. Version published, with the confirmed transaction digest. The version appears in the component library.
Narrated testnet demo · 2026-11-05Download video

Deploy to a group

Overview

Groups let one deployment reach many devices, and membership is checked by each device at apply time. A deployment records the version, the targets and the wallet that authorized it.

Open Deploy component ↗
  1. Groups let one deployment reach many devices, and membership is checked by each device at apply time. A deployment records the version, the targets and the wallet that authorized it.
  2. A published version.
  3. Registered or enrolled devices.
  4. On Devices, open the Device groups tab, click Create group and give it a Group name.
  5. Click Manage on the group and Add the devices that should receive the release.
  6. In the component library click Deploy this version, or choose Deploy component in the sidebar.
  7. Under Select targets & review tick the group (or individual devices) and click Deploy to 1 target. A catalog version deploys once; to make it a group's desired version, use the ad-hoc Deploy component flow.
  8. Approve the transaction, then open View deployments to follow each device's signed result.
  9. Deployment created. Each device in the group reports success or failure under Deployments.
Narrated testnet demo · 2026-11-05Download video

Run a staged rollout

Overview

A staged rollout releases to cohorts in order. Devices are admitted a few at a time; each cohort must report signed, healthy results for its bake period before the next one starts, and the rollout stops itself if failures pass your threshold.

Open Rollouts ↗
  1. A staged rollout releases to cohorts in order. Devices are admitted a few at a time; each cohort must report signed, healthy results for its bake period before the next one starts, and the rollout stops itself if failures pass your threshold.
  2. A published library version for the target device platform.
  3. Named devices or groups to divide into batches. Configure device reporting and verify current health before admitting devices.
  4. Choose Rollouts and open Create a gradual rollout.
  5. Choose Published library version and platform. Add named devices or groups to each cohort (batch); each device can appear in only one batch.
  6. Choose the pace, observation period, minimum reports and failure threshold. Select Review rollout, check the exact plan, then Confirm creation in wallet. Creation starts no devices.
  7. Select the saved rollout. Once device reporting is configured and current health is available, choose waiting devices and Check device health and continue. Return to approve subsequent batches.
  8. Use Pause to stop new starts, Resume to allow further checks, or Abort permanently. Give an audit reason; updates already allowed to start may finish.
  9. Creation leaves devices waiting. The demonstration creates and pauses a plan without admitting devices; it does not claim healthy rollout completion. Actual progress requires admitted devices, verified update results and current health reports.
Narrated testnet demo · 2026-11-05Download video

Private-release access

Overview

Optional for private software: choose which devices may decrypt a release. Create the device group first, then configure access before publishing private software. This controls access to files; it does not itself deploy them.

Open Access policies ↗
  1. Optional for private software: choose which devices may decrypt a release. Create the device group first, then configure access before publishing private software. This controls access to files; it does not itself deploy them.
  2. A group you administer.
  3. Open Access policies and create a named policy.
  4. Choose Group as the recipient type, select the demo group and click Grant decryption.
  5. Approve the transaction. The group appears under granted recipients.
  6. The group may request keys according to current membership; already decrypted bytes cannot be recalled.
Narrated testnet demo · 2026-11-05Download video

Choose fleet settings

Overview

Choose how often devices check for updates and report health. Budget estimates are planning tools.

Open Fleet settings ↗
  1. Choose how often devices check for updates and report health. Budget estimates are planning tools.
  2. A selected fleet and its network budget.
  3. Open Fleet settings and choose a device reporting interval.
  4. Review the estimate, then click Save settings and approve.
  5. Open Network budget to review the balance separately. Saving settings does not fund the budget.
  6. Settings are saved on chain; devices apply them at their next check.
Demo layout may differ · Never share recovery phrases