Check Rivya's live scope across public pages, models, sign-in requirements, Studio execution, audio coverage, and coming-soon boundaries.

Use this page to understand what Rivya supports today.

It separates three things users often mix together: what you can browse publicly, what you can start from a public page, and what runs as a saved workflow after sign-in.

That distinction matters before you choose a model, buy credits, upload files, or explain Rivya to a teammate. If you already understand the product scope and only need help choosing a path, the decision guides in the blog are usually faster.

The Shortest Accurate Summary

The current product, at a glance, looks like this:

the public model catalog currently spans 92 live model pages across chat, image, video, and audio
public discovery pages, prompt pages, showcase pages, model pages, tool pages, docs, blog, and pricing are all live
public start pages now combine product context, examples, and quick-start entry points on the same path
saved, billable execution lives behind sign-in in Studio and related account areas
the only live tools today are AI Calculator and AI Solver
the audio surface now spans voice, dialogue, sound effects, cleanup, and a smaller live music branch

That is the practical shape of Rivya today.

A Layer-By-Layer View

1. Public discovery

Before sign-in, users can browse:

/chat, /image, /video, /audio
/chat/showcase, /image/showcase, /video/showcase, /audio/showcase
/chat/prompt, /image/prompt, /video/prompt, /audio/prompt
/ai-models and /ai-models/[slug]
/tools and /tools/[slug]
/pricing, /blog, and /docs

This layer is for:

comparing models and tools
understanding which path fits the task
browsing prompts, examples, and product context

2. Public start pages and quick starts

Users can also open these paths before sign-in:

/chat, /image, /video, /audio
/ai-models/[slug]
/tools/[slug]

This layer is for:

starting from the right public start page without leaving the path
reducing blank-page friction
carrying task intent into sign-in and Studio

This layer is not for:

fully anonymous saved execution
upload-heavy execution with no account
treating public paths as a substitute for the signed-in workspace

3. Signed-in execution and account context

This is where the product actually runs as a saved workflow:

billable chat execution
image, video, and audio generation
reference-file uploads
saved continuity and history
wallet-backed task execution
notifications, billing, credits, and settings

In path terms, that includes pages such as:

/dashboard
/studio/*
/history/*
/notifications
/settings/*
/payment

What Is Really Live In Tools

This boundary matters because the tools catalog is wider than the live tool set.

Today, the only real live tools are:

AI Calculator
AI Solver

You may still see other categories in the tools catalog, but those categories show where Rivya may expand next. They are not the same as tools you can run today.

What The Audio Surface Really Means

Another boundary worth keeping explicit:

the current audio surface already covers voice, dialogue, sound effects, cleanup, upload-led audio tasks, and a smaller live music branch built around Suno Music, Suno Sounds, and Suno Lyrics.

Today the clearest shipped center of gravity is:

single-speaker voice
multilingual speech
multi-speaker dialogue
sound effects
audio cleanup and isolation
song drafts, sound sketches, and lyric-first music ideation

That is the current live scope. It is broader than a simple voice tool and already includes early music workflows, but it is not yet best described as a deep music-only product.

How To Read “Coming Soon”

In Rivya, “coming soon” should be read as:

a category you may already see in the catalog
a direction Rivya may support later
not something you can rely on for a task today

It should not be read as:

a workflow users can already run
a place to send new users before it ships
a page that needs the same step-by-step instructions as live features

If A Page Seems Out Of Date

Rivya's model catalog can change faster than older explanatory pages.

So when an older blog post and the live catalog disagree:

trust the current model or tool page first
use this page for the overall product boundary
use narrower guides to choose a starting point, not to count every available model

The Practical Rule

If the question is:

Can I browse or evaluate this today?

The answer may be yes on the public pages.

If the question is:

Can I execute this today as part of a real saved workflow?

That usually means checking whether it is truly live and whether sign-in is required.

Scope Check Before You Start

This checklist helps classify a request as part of the live product, a public discovery path, or a category that is not live yet:

Match the task to one layer: public browsing, public quick start, or signed-in Studio execution.
Treat coming-soon tool categories as future direction signs, not executable product promises.
For audio, separate voice, dialogue, sound effects, cleanup, and the smaller music branch before choosing a path.
If a blog guide and the live catalog disagree, trust the catalog and this scope page first.

Recheck When Scope Changes

Recheck this page when a model, tool, upload path, pricing-sensitive flow, or public quick-start behavior changes. Scope pages lose trust quickly if they describe a future plan as if it already shipped.

Rivya Live Features and Product Scope