PHP SDK 3.11

Work that keeps going. Even when PHP stops.

Move an existing Laravel workflow application to Durable Workflow 2.0 without giving up its container, configuration, commands, logs, or tests. Choose embedded state or a separately operated service.

Choose a Laravel path Start with plain PHP

first-workflow

composer require durable-workflow/sdk:^3.11
env -u DURABLE_WORKFLOW_CLIENT_TOKEN \
  php worker.php &
env -u DURABLE_WORKFLOW_WORKER_TOKEN \
  php client.php

After configuring the runtime and saving the example files.

Start where your PHP already lives

The durable model is shared. The bootstrap, container, and operating experience stay idiomatic to your stack.

01 · LARAVEL

Move from v1 without losing Laravel

Choose v2 embedded or service mode now, then change ownership later through one supported transition matrix.

Laravel guide → 02 · PLAIN PHP

Client + remote worker

Use the framework-neutral SDK in a script, service, or existing application.

Plain PHP guide → 03 · SYMFONY

Container-managed worker

Configure the first-party SDK as services and run a Console command under your supervisor.

Symfony guide →

Choose who runs the runtime

Your workflow code and task queue stay the same. The runtime URL, credentials, and operating boundary change.

Your infrastructure · no account

Self-hosted Server

Run the published Server image with your database, auth policy, and operational controls.

Run Server →

Managed · limited access

Durable Workflow Cloud

Request a managed namespace, then use its full runtime URL with separate client and worker credentials.

Request early access →