Set up your organization for ProcessOS Harness
Before you install anything, set your organization up to succeed with ProcessOS Harness. This page covers the organizational preparation. For the technical setup, see install ProcessOS Harness and configure a project.
ProcessOS Harness is a new way of running projects, not a new feature in a familiar tool. The interaction model is unfamiliar, and the early access release assumes a trained builder. The two steps below are the intended path for early access, not optional extras.
Run your first project with a partner or a Camunda FDE
Run your first ProcessOS project together with an enabled partner or a Camunda Forward Deployed Engineer (FDE), rather than on your own.
The first journey is where an unfamiliar interaction model costs the most. Someone who has already completed an engagement can tell a recoverable result from a dead end, which saves you iterations. Once your team has one project behind it, later projects are far less dependent on outside support.
Contact your Camunda account team to arrange this.
Complete the Camunda Academy overview course
Complete the ProcessOS Harness overview course in Camunda Academy before you start a project.
Academy is where you build the capability to work with ProcessOS Harness, including the mindset shift that working with non-deterministic AI output requires. This documentation is written for a builder who has already done that, and it's here to keep you unblocked rather than to teach the approach from scratch.
Treat the overview course as a prerequisite for your first project.
Plan the effort
ProcessOS Harness runs many agent iterations, so a journey has a real token cost. Plan for roughly $300 to $600 in tokens and six to eight hours for one journey from discovery through implementation. Treat this as a planning input rather than a fixed price. Run configuration and process complexity heavily impact token usage.
Involve your SMEs early. ProcessOS Harness changes their role from main contributor to reviewer, which reduces their total effort, but they still need to be available at the review gates in each phase. A project stalls when a review cycle has no reviewer.