# Free Tier for the cicd-sensor Integration Released

Takumi's [cicd-sensor integration](/docs/r/202608-takumi-runner-cicd-sensor-integration) now has a free tier.

No credit card required — just create a Takumi organization and Takumi accepts trace logs for up to 3,000 minutes of CI/CD job run time per month. Every feature that makes use of the trace logs is available too, including [Trace Search](/docs/t/runner/features/trace-search) and [Threat Detection](/docs/t/runner/features/threat-detection), so you can **check and detect the impact of supply-chain incidents free of charge**.

![Available features by subscription status](/docs/_md-assets/9f416e1a13-subscription-matrix.svg)

## Overview

Until now, using the cicd-sensor integration required a Takumi subscription and Runner enabled. Starting today, with the free tier, all it takes is creating a Takumi organization.

:::warning
The pricing of Takumi Runner (running CI/CD jobs on our dedicated runners) is unchanged.
:::

## What You Can Use {#features}

All the trace log investigation features are available.

**Trace log visualization**

You can review the [visualized trace data](/docs/t/runner/features/trace-visualization) in the Takumi console.

![Network tab](/docs/_md-assets/d2e0811031-job-network.png)

**Trace log search**

From the Takumi console, you can [search the contents of the collected trace logs](/docs/t/runner/features/trace-search). You can check whether the CI/CD jobs that ran during a supply-chain incident were affected.

![Search results](/docs/_md-assets/516479dc7c-trace-search-results.png)

**Threat detection**

[Threat detection](/docs/r/202608-takumi-runner-threat-detection) proactively investigates the impact of a supply-chain incident based on the trace logs and notifies you if you are affected. Since it removes the need to investigate yourself, it addresses gaps in expertise and the risk of missing an incident.

![Responding to a supply-chain incident: before vs. with threat detection](/docs/_md-assets/ba18ee84bc-threat-detection-before-after.svg)

## When You Exceed the Free Tier

The free tier accepts trace logs for up to 3,000 minutes of total job run time per organization per month. Once the 3,000-minute limit is reached, trace logs are no longer accepted after that point, but your CI/CD jobs still run as usual.

To manage trace logs in Takumi beyond 3,000 minutes, you need a Takumi subscription and Runner enabled.

For the pricing details of the cicd-sensor integration and Takumi Runner, see [Pricing & Billing](/docs/t/runner/billing).

## Getting Started

The steps to start using the free tier are as follows.

### Creating an Organization

Go to [https://cloud.shisho.dev/hello/takumi](https://cloud.shisho.dev/hello/takumi).

![Organization registration screen](/docs/_md-assets/e5b7f29d10-create-organization.png)

1.  Turn on **Create a new organization** and enter the ID of the organization to register
2.  Press **Create a new organization**

Once the organization is created, next set up the cicd-sensor integration.

### Setting Up the cicd-sensor Integration

Here we walk through the setup for CI/CD jobs on GitHub-hosted runners. If you use another environment, see the [user guide](/docs/t/runner/features/cicdsensor-integration).

**Credentials**

First, create a bot that handles the credentials. In the Takumi console, open **Settings** > **Bots** > **Add bot** and select **Takumi Runner Trace Sender** to open the bot creation screen.

![Add bot](/docs/_md-assets/c301d5a440-cicdsensor-create-bot.png)

![Select Takumi Runner Trace Sender role](/docs/_md-assets/f0f782789d-cicdsensor-select-role.png)

On the bot creation screen, set up a **trust condition**. Enter the **name**, **organization**, and **repository**.

![Create trust condition](/docs/_md-assets/946c4873a6-cicdsensor-trust-condition.png)

Press save to finish creating the bot. Next, create a GitHub workflow.

**Creating a GitHub job**

Here we create a job that runs `echo Hello`.

```yaml
jobs:
  build:
    runs-on: ubuntu-latest
    environment: cicd-sensor
    permissions:
      contents: read
      id-token: write
    steps:
      - id: auth
        uses: flatt-security/shisho-cloud-action@v1
        with:
          bot-id: <Bot ID>
          export-token: true
          expires-in-minutes: 360
      - uses: cicd-sensor/cicd-sensor-action@a803a7bc1890f85d3f2feb7c29b74b5c730da6c2 # v0.0.37
        with:
          manager-url: https://manager.cicdsensor.cloud.shisho.dev
          manager-token: ${{ steps.auth.outputs.token }}
      - run: echo Hello
```

The `uses: flatt-security/shisho-cloud-action@v1` step obtains the credentials. The `uses: cicd-sensor/cicd-sensor-action` step runs cicd-sensor.

The connection to Takumi is configured with `manager-url: https://manager.cicdsensor.cloud.shisho.dev`.

### Checking the Trace Logs

Run the job above and the run becomes visible in the Takumi console. Open **Runner** on the left side of the screen, and completed jobs appear under **Recent Jobs**.

![Takumi Runner overview screen](/docs/_md-assets/98345f86d7-overview.png)

Click a job to see its trace logs. From here, you can use the [various features](#features) for working with trace logs introduced above.

For more details on the cicd-sensor integration, see the [user guide](/docs/t/runner/features/cicdsensor-integration).