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

# Deployment Overview

> Deploy workflows locally, on Vercel, or anywhere using pluggable World adapters.

Workflows are designed to be highly portable. The same workflow code can run locally during development, on Vercel with zero configuration, or on any infrastructure using **Worlds** — pluggable adapters that handle storage, queuing, and communication.

## Local Development

During local development, workflows automatically use the **Local World** — no configuration required. The Local World stores workflow data in a `.workflow-data/` directory and processes steps synchronously, making it perfect for development and testing.

```bash theme={null}
# Just run your dev server - workflows work out of the box
npm run dev
```

You can inspect local workflow data using the CLI:

```bash theme={null}
npx workflow inspect runs
```

<Callout>
  Learn more about the [Local World](/deployment/storage) configuration and internals.
</Callout>

## Deploying to Vercel

The easiest way to deploy workflows to production is on Vercel. When you deploy to Vercel, workflows automatically use the **Vercel World** — again, with zero configuration.

The Vercel World provides:

* **Durable storage** - Workflow state persists across function invocations
* **Managed queuing** - Steps are processed reliably with automatic retries
* **Automatic scaling** - Workflows scale with your application
* **Built-in observability** - View workflow runs in the Vercel dashboard

Simply deploy your application:

```bash theme={null}
vercel deploy
```

<FluidComputeCallout />

<Callout>
  Learn more about the [Vercel World](/worlds/vercel) and its capabilities.
</Callout>

## Self-Hosting & Other Providers

For self-hosting or deploying to other cloud providers, you can use community-maintained Worlds or build your own.

<Cards>
  <Card title="Explore Worlds" href="/worlds">
    Browse official and community World implementations with compatibility status and performance benchmarks.
  </Card>

  <Card title="Build Your Own" href="/deployment/storage">
    Learn how to implement a custom World for your infrastructure.
  </Card>
</Cards>

### Using a Third-Party World

To use a different World implementation, set the `WORKFLOW_TARGET_WORLD` environment variable:

```bash theme={null}
export WORKFLOW_TARGET_WORLD=@workflow-worlds/postgres
# Plus any world-specific configuration
export DATABASE_URL=postgres://...
```

Each World may have its own configuration requirements — refer to the specific World's documentation for details.

## Observability

The [Observability tools](/observability/opentelemetry) work with any World backend. By default they connect to your local environment, but can be configured to inspect remote deployments:

```bash theme={null}
# Inspect local workflows
npx workflow inspect runs

# Inspect remote workflows
npx workflow inspect runs --backend @workflow-worlds/postgres
```

Learn more about [Observability](/observability/opentelemetry) tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.