# Limits and not shipped

> Current product boundaries, locked states, and practical limitations.

Canonical: https://docs.onira.studio/overview/limits-and-not-shipped
Section: overview

This page lists important current boundaries so teams can plan work without assuming a feature exists.

## Product boundaries

Onira is not currently:

- A stock-template video editor.
- A social media scheduler.
- A talking-head avatar recorder.
- A public prompt marketplace.
- A generic image generation playground.
- A replacement for a full nonlinear editor.
- A public API product.

## Editing boundaries

Studio is designed for structured review and regeneration. The Timeline tab is read-only for most track movement. Users can review playback, select clips, inspect versions, mute tracks, style subtitles, and open context for assistant-driven changes, but the current UI does not expose arbitrary drag-to-recut editing.

Current practical boundaries:

- Generated assets are edited through regeneration, version selection, and Studio-directed plans.
- Timeline edits are scoped to supported project-level controls.
- Some asset updates require a new render before they appear in the downloadable MP4.
- Render quality is gated by plan.
- Export is locked until the project has completed generation.
- Only one render can be queued or running for a project at a time.

## Duration and plan limits

The duration picker exposes discrete options:

- 1 minute.
- 2 minutes.
- 3 minutes.
- 5 minutes.
- 10 minutes.
- 15 minutes.
- 20 minutes.
- 25 minutes.
- 30 minutes.

Each plan carries a commercial duration entitlement: Creator 10 minutes, Studio 20 minutes, and Pro or Enterprise 30 minutes by default. The engine applies a separate evidence-based qualification ceiling, conservatively 3 minutes in the default release configuration. The effective maximum is the smaller limit. A plan upgrade alone does not unlock an unqualified target.

## Credit limits

Production is blocked when available credits are below the maximum reserved estimate for the selected settings. Frozen credits are reserved by in-flight runs and are not spendable until the run finishes or releases them.

If a project fails, retry behavior depends on the failure category and whether the latest run can be resumed. Terminal failures do not promise retry. Resumable failures can retry from the failed step.

## Concurrency limits

Workspace plans limit concurrent production runs:

| Plan | Concurrent production runs |
| --- | ---: |
| Creator | 1 |
| Studio | 2 |
| Pro | 3 |
| Enterprise | 5 by default, unless customized |

When every slot is busy, the project workspace shows a cap state with a Check again action and, where applicable, an upgrade action.

## Mobile limits

The creation flow and lightweight project views are responsive. The deep project workspace and character editor are optimized for desktop-sized screens. Mobile fallback views are for inspection, render handling, and link sharing, not full Studio editing.

## Documentation boundary

These docs intentionally avoid private implementation details. They document how the product behaves, what users can control, and which operational states matter.

## Known no-go assumptions

Do not assume the current product includes:

- Public webhooks.
- A public GraphQL API contract.
- Team audit logs in self-serve plans.
- SSO in self-serve plans.
- A live browser-based editor for arbitrary frame-by-frame video editing.
- A published marketplace for user-created templates.

## Product and publication boundary

- Onira produces a reviewable MP4; it does not upload or schedule social posts.
- Creators remain responsible for facts, sources, rights, disclosure, policy review, and final publication.
- Research is research-assisted; creator verification is required before publication.
- Onira does not guarantee factual accuracy, legal clearance, monetization, reach, or production success.
- The current Timeline and Studio surfaces support defined review and regeneration workflows, not arbitrary nonlinear editing.