Look around a real workspace.
One button opens a live LumaVista account with finished research projects already in it — the reports, the sources behind every claim, the library they were built from, and the knowledge graph they produced. Not screenshots, and not a scripted tour. The actual product, with real output in it.
Read-only. No account, no card, nothing to install.
What you'll be looking at
A workspace, not a report generator. The demo account holds a flagship research project together with everything it produced, and the surfaces around it that make this a place to work rather than a one-shot tool.
Finished reports
Long-form and structured, with every claim traceable to the source it came from. Open a citation and you land on the material it was drawn from.
The sources behind them
The pages and documents a run actually read are kept with the report instead of thrown away. That is the difference between a report you can audit and one you can only hope is right.
The knowledge graph
Entities, topics and relations extracted from the results as they arrive, accumulating across projects. It is why a second investigation into a subject starts further along than the first.
The rest of the workspace
Library, notes, tasks, workflows — including the surfaces that happen to be empty in the demo account. An honest empty state tells you more about a product than a staged one.
What's real, and what isn't
This page exists to show you the product, not to flatter it. So, precisely:
Real
-
A real account
You are signed in to an actual LumaVista account, through the actual app. There is no marketing replica of the interface anywhere in this.
-
Real generated output
Every report in the demo was produced by the same research engine that would run your own questions. Nothing in it was written by hand to make it read better.
-
The shipping build
The demo is the product, so it cannot drift away from it. When we ship a change, the demo changes with it — there is nothing separate to keep up to date.
Not in the demo
-
It is read-only
You can open, read and browse everything in the account. You cannot change it, and you cannot run your own research in it — the account is shared with every other visitor, so nothing you did there would stay yours.
-
There is no chat
Asking questions across your own library is one of the best things the product does, and it is deliberately not part of the demo: it spends credits per visitor on a shared, public account. You get it in a workspace of your own, not here.
-
No settings, billing or connectors
Those surfaces belong to one person's own account. On a shared demo identity they would be meaningless, so they are closed rather than faked.
You dispatch a run and come back to it later.
This is the one expectation worth setting in advance. A deep research run takes minutes, sometimes tens of minutes. That is not a delay we are apologising for — it is what genuinely reading dozens of sources costs, and it is the reason the result is worth reading.
- 01
Ask
You write the question, choose how deep to go, and dispatch it. That part takes a moment.
- 02
Go and do something else
The run continues without you. You can watch the graph work if you find that interesting, or close the tab entirely — it makes no difference to the result.
- 03
Come back to a finished report
Structured, cited and ready to read. The demo shows you that end state, because the end state is the point. We are not going to make you sit through a staged progress bar.
It is not a chatbot that replies in two seconds. That is the trade, stated plainly: it takes longer because it actually goes and does the work.
The demo is not encrypted. Your own workspace is.
The demo account runs unencrypted, on public sample content, because it is shared with everyone who opens this page. Nothing in it is private and nothing in it belongs to anybody.
A workspace of your own works the other way round. Your documents are encrypted per user under keys generated on your device, and we hold no copy of them and no escrow. If the app offers to unlock a session while you are inside the demo, it is showing you that mechanism in a labelled demo state — it is not protecting demo data, because there is nothing in there to protect.
Questions people ask first
Do I need an account?
Is any of it my data?
Can I try it on my own question?
How long does the session last?
Have a look.
A few minutes inside a real workspace will tell you more than the rest of this website can.