Use Rivya public pages to browse AI models, preview workflows, start quick tasks, compare examples, and decide when to sign in.

Use this guide when you are deciding whether a Rivya task can start from a public page or should move into Studio.

Public pages are useful for browsing models, previewing workflows, reading examples, and choosing the next surface before committing to a deeper signed-in workflow.

What Public Quick Start Is For

Use public pages when you want to:

browse workflows
compare models
understand a category
test a lightweight entry point
read examples or guides
decide whether the task needs Studio

Public pages are useful for orientation. Authenticated Studio is better for saved, credit-backed, repeatable work.

Public Layer Order

For most tasks, use the public layer to narrow the next step before signing in:

Start from the category page when you only know the format: Chat, Image, Video, Audio, Tools, or AI Models.
Open AI Models when the main question is capability, input mode, examples, or credit shape.
Open a blog guide when the main question is comparison or workflow choice.
Move into Studio when the task needs uploads, saved history, credits, or follow-up work.

This order keeps public discovery useful without pretending it is the full workspace.

When To Move Into Studio

Move into Studio when you need:

generation with account context
file uploads
saved history
notifications
credit-backed execution
multi-step work
continuation from previous results

If the task matters enough to revisit, Studio is usually the better place.

Public Pages And Model Pages

Public pages help you compare options. Use Chat, Image, Video, and Audio when the output type is already clear; use Tools when the task is calculator- or solver-shaped.

Model pages help you check current capabilities, supported modes, examples, and entry points. Treat them as inventory pages before you spend credits.

Discovery Is Not Production

A public page can help you decide where to begin.

It should not be treated as the full production workflow when you need saved context, references, billing state, and result management.

Public Start Checklist

When you are deciding where to go next, check:

Identify whether the need is discovery, execution, account management, billing, or support.
Point model questions to model pages and model docs, not generic help text.
Point task execution to the relevant public start page or Studio surface.
Keep current product scope separate from future roadmap language.
Prefer one clear next link over a long list of possible paths.

The goal is to help the reader choose the next page without learning internal architecture.

Common Wrong Turns

Avoid using public pages as if they were saved project spaces.

Common wrong turns include starting upload-dependent work from a public article, comparing models without checking supported modes, treating examples as guaranteed outputs, and delaying sign-in after the task already needs history or credits.

If you want to continue from a result later, move into Studio before the workflow becomes important.

When To Recheck The Next Step

Recheck the next step when discovery, execution, billing, and support questions are mixed into one task.

In those cases, separate the intent first, then send them to the page that can actually resolve that intent.

Rivya Public Quick Start Guide