Public direction / no fixed dates

Test the operating system before opening the doors.

We are using a guided beta to observe real productions first. Release order will follow recurring workflow problems, not a fixed list of marketing dates.

Now / guided beta

Run real productions with selected teams.

Test onboarding, project setup, permissions, file reuse, notifications, client review, approval, and delivery with production teams and freelancers. Fix blockers that appear during actual work. Publish English product documentation alongside the pilots.

IN PROGRESS
Next / beta readiness

Prepare for open registration.

Use pilot findings to harden the first-run path, clarify plan limits, improve support and recovery states, and make core workflows understandable without a guided call. Open registration only when teams can complete a production without avoidable intervention.

VALIDATING
Later / expansion

Add depth where production evidence supports it.

Broaden language support, integrations, automation, and reporting after the core lifecycle is stable. Items may move as beta feedback reveals more important work.

DIRECTION
Shape the roadmap

Beta feedback should come from production, not a feature poll.

Apply with a project →