> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ironbee.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Verification Platforms

> Verify through the browser, backend, Node.js, and Android and tune each platform.

The action verifies through IronBee DevTools modes: the browser, backend, Node.js, and Android platforms, the same cycles the [CLI uses](/cli/concepts/how-it-works#verification-cycles). Each enabled platform registers its MCP server so the agent can exercise the change through that surface.

***

## The four platforms

| Platform | Input                      | Default | Verifies through…                                                                    |
| -------- | -------------------------- | ------- | ------------------------------------------------------------------------------------ |
| Browser  | `ironbee_browser_devtools` | `true`  | A real Chromium browser navigation, screenshots, console, accessibility              |
| Backend  | `ironbee_backend_devtools` | `false` | Real protocol calls HTTP, gRPC, GraphQL, WebSocket                                   |
| Node.js  | `ironbee_node_devtools`    | `false` | The Node.js V8 inspector probes and runtime snapshots                                |
| Android  | `ironbee_android_devtools` | `false` | A real emulator over ADB app launch, taps, swipes, screenshots, UI snapshots, Logcat |

Only the browser runs by default. Opt into backend, Node.js, or Android verification by setting the corresponding input to `true`.

```yaml theme={null}
- uses: ironbee-ai/ironbee-action@v1
  with:
    ironbee_api_key: ${{ secrets.IRONBEE_API_KEY }}
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
    ironbee_browser_devtools: 'true'
    ironbee_backend_devtools: 'true'
    ironbee_node_devtools: 'false'
    ironbee_android_devtools: 'false'
```

<Info>
  Each enabled platform is registered as an MCP server during `ironbee install`, and its log is written under `.ironbee/artifacts/` so it ships with the [evidence artifact](/github-action/advanced/evidence#evidence-artifacts).
</Info>

***

## Browser on CI runners

GitHub-hosted Linux runners reject user-namespace sandboxing, which would otherwise kill Chromium on first navigation. The action handles this for you by launching Chromium with `--no-sandbox` (`BROWSER_CHROMIUM_SANDBOX=false`), no configuration needed.

***

## Tuning a platform

Each platform's MCP server can be customized beyond the enable toggles, set extra environment variables or replace the server entirely via `ironbee_extra_config`. See [Custom configuration](/github-action/advanced/custom-configuration).

***

## What's next?

<CardGroup cols={2}>
  <Card title="Verifying your application" icon="play" href="/github-action/guides/verifying-your-app">
    Install, build, start, and reach your app.
  </Card>

  <Card title="How it works" icon="lightbulb" href="/github-action/concepts/how-it-works">
    The verification loop behind these platforms.
  </Card>
</CardGroup>