Skip to content

Projects view

The top-level listing of all projects you own.

What you can do

  • Create a project. You give it a name; the slug is generated from that name, and you can adjust it with the Edit link next to the field before saving.
  • Open a project to see its devices, artifacts, deployments, tokens, channels, groups and signing keys.
  • Delete a project. This is blocked while any deployment is active or paused: cancel or complete those first. Devices and artifacts do not block deletion, and deleting removes them along with the project.

Projects cannot be renamed

Neither the name nor the slug can be changed after creation, in the dashboard or through the API. Pick both deliberately. Deleting and recreating is the only way to change them, and that discards the project's devices, artifacts and build counter.

Deleting through the Developer API additionally requires a personal access token; a project-scoped token cannot delete its own project.

Project ID

Every project has a UUID, shown under the project name with a copy button.

This is the identifier the API and CI use: the slug appears nowhere in any API path. Anywhere the docs refer to SIMPLEOTA_PROJECT_ID, or a URL like /api/v1/projects/{project_id}/, this is the value.

The slug is a short human label, used in the project list and in audit-log entries. It is not an API identifier.

Simple and Advanced mode

The toggle at the top right of a project switches how much of the machinery is on screen. The choice is remembered per project.

  • Simple shows devices, project API tokens, and a one-step firmware upload. Enough to ship builds to a small fleet.
  • Advanced adds firmware artifacts, deployments, release channels, device groups and firmware signing keys.

Guides that say "Advanced mode" mean this toggle: signing keys and deployment controls are not visible in Simple mode.

Shipping a release

In Advanced mode the order of operations is:

  1. Upload an artifact (with its manifest).
  2. Optionally add devices to a group, or move them to a channel.
  3. Create a deployment targeting that audience at a low percentage.
  4. Watch it. Ramp up.

In Simple mode, steps 1 and 3 are collapsed into one upload form: it uploads the artifact, then creates and starts an immediate 100% deployment to every active device on the project's default channel.

If a canary or otherwise non-immediate rollout is already active, the Simple upload refuses to run rather than quietly replacing a careful rollout with an instant one. Switch to Advanced mode to finish or cancel that deployment first.