Skip to content
Onira

Product map

How the current Onira app is organized from homepage to project workspace.


The authenticated app is organized around workspaces. A workspace owns projects, folders, saved characters, credits, billing, members, and settings.

The workspace slug is part of authenticated URLs. Internal navigation should use workspace-aware links so users stay inside the correct workspace.

Primary areas

AreaRoute shapeWhat it owns
Home/{workspace}Prompt composer, production defaults, template handoff, saved-character selection.
Templates/{workspace}/templatesPublished prompt templates, category filter, search, "use template" handoff.
Characters/{workspace}/charactersSaved character library and character creation entrypoint.
Character editor/{workspace}/characters/{id}Character chat, portraits, 3D model preview, role, voice, versions.
Projects/{workspace}/projectsProject list, filters, sort, folders, stars, deletes.
Project workspace/{workspace}/projects/{id}Blueprint, Timeline, Studio chat, settings, share, export.
Settings/{workspace}/settingsWorkspace profile, members, billing, account, notifications, support.

/{workspace}/projects/{id}/studio redirects to /{workspace}/projects/{id}. The project page is the canonical workspace.

The main sidebar contains:

  • Home.
  • Templates.
  • Characters.
  • Projects with All projects, New folder, visible folders, and See all folders.
  • Recent projects.
  • Upgrade action when the current plan is below Pro or Enterprise.
  • Credit balance with available and frozen credits.
  • User menu with settings, support, documentation, homepage, and log out.

The workspace switcher also exposes workspace settings, invite members, upgrade or manage plan, workspace list, pending invitations, and create workspace.

Project entry model

A project is created first, then production starts from the project workspace. Draft projects auto-start production when opened. If the backend decides the prompt needs clarification, Studio shows the assistant question instead of starting provider-heavy work.

Project generation and render are separate lifecycles:

  1. Project creation stores prompt and settings.
  2. Production runs the pipeline and creates timeline assets.
  3. Export starts one or more render attempts after the project is ready.

Settings model

Settings are split between workspace and account concerns:

Settings pagePurpose
GeneralWorkspace name, avatar, URL/slug, and delete workspace controls.
PeopleMembers, roles, invites, invite revocation, member export.
BillingPlan summary, balance, top-ups, usage, ledger, invoices, and plan changes.
AccountCurrent user's profile and account-level details.
NotificationsMarketing, low-balance, and renewal reminder preferences.
SupportSupport email, bug report email, documentation, community, and release notes.

Mobile model

The app uses dedicated mobile fallbacks for heavy workspaces:

  • Project mobile view: status, project summary, render readiness, render history, preview/download, and copy link.
  • Character mobile view: portrait, voice, appearance, portrait history, and copy link.

Detailed project editing and character iteration are designed for desktop.