Assets / Tools

Utility tools should connect back into the platform, not sit alone.

The tools page now reflects real platform utilities and metered suite actions instead of a hollow external directory.

Utility Lane

Tools should read like connected system utilities. Make the next route obvious and keep the page away from dead-end directory behavior.

Utility lane

Shared billing context

Utility actions should expose the same pricing and tier rules as the main lanes around them.

Linked role

System fit

Utility lane

Route continuity

The tools page is now tied to real workspace routes instead of a dead-end list of promises.

Linked role

System fit

Utility lane

Less surface drift

Utility functions now point back to Studio, Suite, and Production surfaces that already exist.

Linked role

System fit

Utility lanes

3

Connected surfaces

3

Support uses

3

Next routes

5

Current Utilities

These are the real utility-oriented lanes already connected to the platform.

Video Edit AIVideo Edit AI with integrated billing and provider guardrails.20 credits · Pro+ · Gemini
Camera Angle ControlRegenerate perspective and framing with camera intent.30 credits · Pro+ · Kling
Add Sound EffectInject contextual sound effects into generated video.10 credits · Pro+ · Gemini

Platform Fit

A tool only matters when it remains part of the system.

Each asset category should feel like a production-adjacent utility surface with one strong use posture instead of a generic content directory.

Shared billing context

Utility actions should expose the same pricing and tier rules as the main lanes around them.

Route continuity

The tools page is now tied to real workspace routes instead of a dead-end list of promises.

Less surface drift

Utility functions now point back to Studio, Suite, and Production surfaces that already exist.

Use Cases

Where utility lanes do real work.

Use case 01Production

Finishing support

Use utilities to tighten media that is already mostly working instead of rerunning the whole job.

Use case 02Studio

Cross-medium fixes

Keep audio, image, and video support functions visible in one broader operating system.

Use case 03Operations

Publish readiness

Use utility lanes to remove the last blockers before queue and delivery.

Use utilities where the rest of the production system can still see them.

Open Studio when support functions need to remain attached to creation, review, and publish.

Open Studio