---
title: "Shiplight Cloud"
description: "Shiplight Cloud at app.shiplight.ai — upload test results, track flakiness and trends, run CI on Shiplight-hosted runners, and manage tokens, teams, and billing."
---

# Shiplight Cloud

<div class="view-markdown-wrapper">
<ViewMarkdown />
</div>

Shiplight Cloud at [app.shiplight.ai](https://app.shiplight.ai) is the hosted side of Shiplight. Your tests still live in your repository and run through the same CLI — the cloud is where their results accumulate, where CI runs execute, and where your team, tokens, and billing are managed.

You don't need it to run tests. Everything in [Local Testing](/local/run-locally) works standalone. The cloud becomes useful when you want history rather than a single run: which tests are flaky, whether last month was better than this one, and whether a failure is a real regression.

## What it does

**[Test Results](/cloud_v2/test-results)** — every run, preserved with its steps, screenshots, video, and Playwright trace. Filter by repository, branch, PR, or author, and follow a single test's history across runs.

**[Analytics](/cloud_v2/analytics)** — pass rate, duration, and flakiness trends, plus failure attribution that separates genuine regressions from stale tests and infrastructure noise. Scheduled digests can post the summary to Slack.

**[CI Runners](/cloud_v2/ci-runners)** — ephemeral, Shiplight-hosted GitHub Actions runners with browsers and credentials preinstalled. An alternative to `ubuntu-latest`, requiring one line of change in your workflow.

**[API Tokens](/cloud_v2/api-tokens)** — scoped credentials for uploading results, reading them from your coding agent, and calling LLMs through the Shiplight proxy instead of holding your own provider keys.

**[Integrations](/cloud_v2/ci-runners#setup)** — connecting your GitHub organization and repositories. Required before [CI Runners](/cloud_v2/ci-runners) will pick up any job, and what fills in the commit, branch, PR, and author details on your runs.

**[Organization](/cloud_v2/organization)** — members, roles, and organization settings.

**[Billing & Usage](/cloud_v2/billing)** — plans, allowances, and a usage view broken down by tokens, compute, and storage.

## Getting started

1. **Sign in** at [app.shiplight.ai](https://app.shiplight.ai). If your team already has an organization, ask an owner to invite you.
2. **Create an API token** at [Settings → API Tokens](https://app.shiplight.ai/api-tokens).
3. **Upload your first run** by setting `SHIPLIGHT_API_TOKEN` and `SHIPLIGHT_REPORT_TO_CLOUD=1`, then running `npx shiplight report` after your tests. See [Test Results](/cloud_v2/test-results#getting-results-into-the-cloud).
4. **Wire it into CI** with the [CI/CD guides](/local/ci), and optionally move onto [Shiplight runners](/cloud_v2/ci-runners).

Your coding agent can read results back with the **`/shiplight cloud`** skill — runs, failing and flaky tests, and artifacts — so it can triage a CI failure without you leaving the editor.

::: info Looking for the older cloud product?
Documentation for Shiplight Cloud v1 at `app.shiplight.ai` has moved to [Shiplight Cloud v1](/cloud_legacy/quickstart). It describes a different product from the one on this page.
:::