Transitioning from the Oz web app

The Oz web app will retire after Warp Factories reaches general availability. Existing cloud agents, integrations, schedules, API keys, and the oz CLI remain available today, so you don’t need to migrate immediately.

The Automation Platform remains the shared foundation for cloud agents. Warp Factories builds on that foundation for teams that need standing workflows with named agents, work intake, review stages, and measurement.

Choose the right entry point

• Use the Automation Platform - Configure standalone cloud agents, environments, schedules, integrations, and orchestration. Start with the Automation Platform overview or Cloud agents overview.
• Warp Factories - Use a repeatable workflow that routes work through named agents and tracks it in one place. Start with the Warp Factories overview or the factory quickstart.

What stays available

Existing workflows and configuration continue to work today:

• Cloud agents - Continue to run from existing events, schedules, integrations, APIs, and the CLI.
• Configuration - Existing environments, integrations, schedules, API keys, and secrets remain available.
• Current tools - The Oz CLI, API and SDK, and managed self-hosting continue to support their current workflows.

What comes next

This page will add verified migration actions, compatibility dates, and replacement destinations as the product transition is finalized. Until then, continue using the workflow that fits your work today.

Related pages

• Automation Platform overview - Configure the reusable primitives behind cloud-agent workflows.
• Warp Factories overview - Build and operate a standing software factory.
• Factory dashboard - Inspect work items, runs, and factory settings.