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

# How the platform works

> Understand Projects, Runs, Jobs, and the execution model

Intuned is a browser automation platform for developers. You write browser automations as code, deploy them to our infrastructure, and execute them on demand or on a schedule—with built-in [authentication](/main/02-features/auth-sessions), [stealth](/main/02-features/stealth-mode-captcha-solving-proxies), and scale.

## Projects

A **Project** is both your automation code and your runtime environment.

**As code**, a Project contains your browser automation APIs and shared logic—written in **Python** or **TypeScript** using Playwright.

```
Project/
├── apis/
│   ├── scrape-product.ts    # Your automation APIs
│   └── submit-form.ts
├── helpers/                  # Shared utilities
└── Intuned.json       # Project configuration
```

**At runtime**, a Project is where everything comes together: [Run](/main/02-features/runs-single-executions) records, [Jobs](/main/02-features/jobs-batched-executions), JobRuns, browser [traces and logs](/main/02-features/observability-monitoring-logs), and [AuthSessions](/main/02-features/auth-sessions) all live within the Project that owns them.

Each **API** is a function that receives a browser page and parameters, performs actions, and returns results. You have full control over the code—use any library, pattern, or approach that fits your needs.

## Building your automations

You can build the same kind of Intuned Project in two ways: as a **Hosted project** in the [online IDE](/main/02-features/online-ide), or as a **Connected project** with the [local CLI](/main/02-features/local-development-cli).

In both approaches, you write browser automation code in Python or TypeScript, organize it into APIs, test it, and deploy it to Intuned. The main difference is **where you develop** and **how your team works with the code**.

### Hosted projects (online IDE)

Hosted projects are built directly in Intuned's browser-based editor or using intuned agent.

* **How it works**: Create a Hosted project from the dashboard, open it in the online IDE, edit files in the browser, run APIs with the built-in browser view, and deploy when ready.
* **Best for**: Fast starts, solo development, quick prototyping, and teams that want platform-native workflows with minimal setup.
* **Key advantages**: Zero local setup, built-in AI assistance, Selector Agent, browser-based debugging, and access to platform AI features such as **Fix with AI**, **Fix issues**, and **self-healing projects**.
* **Tradeoff**: You work inside Intuned's editor rather than your own local IDE, and Git-based collaboration is more limited.

### Connected projects (local CLI)

Connected projects are built locally on your machine and linked to Intuned through the CLI.

* **How it works**: Create a project with the local CLI, open it in your preferred editor, manage the code in your own repo, run and test locally, then deploy to Intuned when ready.
* **Best for**: Teams using Git workflows, CI/CD pipelines, code review, custom local tooling, and shared repositories.
* **Key advantages**: Full version control, local IDE choice, easier team collaboration, and better fit for existing engineering workflows.
* **Tradeoff**: You need local setup and dependency management, and you do not get the online IDE's built-in editing workflow or platform AI features like **Fix with AI**, **Fix issues**, and **self-healing projects**.

### How to choose

* Choose **Hosted projects (online IDE)** when you want the fastest path from idea to working automation, especially if you want built-in AI and browser debugging.
* Choose **Connected projects (local CLI)** when you want to build in your own environment with Git, CI/CD, and your team's existing development process.

<Tip>
  **[Intuned Agent](/main/02-intuned-agent/overview)** can build entire Projects from a prompt, edit existing ones, fix failed Runs, and [maintain your automations automatically](/main/02-intuned-agent/self-healing-projects) after deployment.
</Tip>

## Deployment

When you deploy a Project, all its APIs become available as callable endpoints. Intuned handles the infrastructure: browser provisioning, execution queues, retries, and scaling.

## Execution model

### Runs and Attempts

When you call an API, you create a **Run**—a single logical execution of your automation.

Each Run may include one or more **Attempts**. If an Attempt fails (network issues, transient errors), Intuned can automatically retry up to your configured limit. Every Attempt is tracked with its own [logs and browser trace](/main/02-features/observability-monitoring-logs), plus timing data.

```
Run
├── Attempt 1 → Failed (timeout)
├── Attempt 2 → Failed (element not found)
└── Attempt 3 → Success ✓
```

### Two ways to execute

**[Runs](/main/02-features/runs-single-executions)** — On-demand execution via API. You trigger a Run, we handle queuing and concurrency.

**[Jobs](/main/02-features/jobs-batched-executions)** — Scheduled or batch execution. Define what to run, when to run it, and where to send results. Built for scrapers and crawlers that need to run on a recurring basis. Each execution of a Job is a **JobRun**—the Job is the template, and each JobRun is a single execution of that template.

## Authentication

For automations that require login, Intuned provides built-in [authentication support](/main/02-features/auth-sessions). You define two functions—`create` (how to log in) and `check` (how to verify a session is valid)—and Intuned handles the rest: validating sessions before Runs, reusing them when possible, and recreating them when expired.

## Key features

**[Flexible automations](/main/02-features/flexible-automation)** — Deploy any code. Deterministic, AI-driven, or hybrid—use any library or package. Unopinionated by design.

**[Built-in authentication](/main/02-features/auth-sessions)** — Write `create` and `check` functions, and Intuned handles the rest—validating, reusing, and recreating sessions automatically.

**[Online IDE](/main/02-features/online-ide)** — Zero setup. Write, test, and deploy directly from your browser.

**[Stealth and anti-detection](/main/02-features/stealth-mode-captcha-solving-proxies)** — Run automations without getting blocked. Stealth mode, automatic captcha solving, and proxy support are built in.

**[Observability](/main/02-features/observability-monitoring-logs)** — Full logs, traces, and session recordings for every Run. See what happened and why.

## What's next?

* **[Build a scraper with Intuned Agent](/main/00-getting-started/quickstarts/intuned-agent)** — Generate a scraper from a prompt and schema
* **[Build an RPA with Intuned Agent](/main/00-getting-started/quickstarts/build-an-rpa-with-intuned-agent)** — Automate browser workflows using the agent
* **[Scraper quickstart](/main/00-getting-started/quickstarts/scraper)** — Build a scraper by hand, deploy it, configure a Job, and run it end to end. Covers the platform concepts from this page in practice.
* **[RPA quickstart](/main/00-getting-started/quickstarts/rpa)** — Build an RPA automation by hand, deploy it, and trigger it via API. A hands-on walkthrough of the platform workflow.
* **[Intuned in depth](/main/01-learn/deep-dives/intuned-indepth)** — Explore the platform in depth