Research
It fills itself
Autonomous deep research runs the gathering, and every claim it writes carries the source it came from. The workspace does not start empty and wait for you.
Cited research
European-sovereign · keys made on your device
Your AI workspace.
Research, your library, notes, chat and workflows in one connected place, encrypted under keys made on your device.
Scattered, and nothing remembers
You already have the knowledge.
It is just scattered across a dozen places that cannot talk to each other.
- Twelve tabs the research you did last month, and can no longer find
- A drive contracts and reports the assistant has never seen
- A notes app the thinking, disconnected from the evidence
- A chat window that forgets all of it by Monday
So every task starts from zero. Not because the work is hard, but because nothing you have built is connected to anything else.
One connected workspace
Six surfaces, one connected system.
Library · Notes · Recordings
What you bring stays yours
Documents, notes and recordings become usable by the AI while staying encrypted under an account key made on your device. We keep no copy of that key and no escrow. 1
Encrypted at rest
Chat
Talk to all of it
Chat grounded across the whole library and the web at once, with scope selection so you decide exactly what any answer is allowed to draw on.
Scope under your control
Workflows
It runs your playbook
Workflows turn the routine into something the system performs, with every inbound byte filtered before it touches your knowledge and every outbound action guarded.
Filtered in, guarded out
Nothing crosses unchecked
Connecting everything you know to an AI is only a good idea if the connection has a boundary.
Inbound
Filtered
Every external byte, whether a crawled page, a fetched document or a connector payload, passes a filter before it is allowed near your knowledge.
Outbound
Guarded
Every action the system takes on your behalf passes a guard on the way out. Nothing leaves on the strength of a model deciding it should.
Your account key is made on your device. It has to read your work to do the work. Once you sign out, your account is closed to us.
An always-on space is different, if you switch one on: for that one space our servers keep a wrapped key, so they can run your automations while you are away, and each opening is written to the space's access log. Processed in Europe, on infrastructure we run.2
So the work arrives already done
Research that arrives already done
Ask a real question and the system runs the gathering itself, reading, cross-checking and writing up a cited report into your library. You start from a briefed position instead of an empty page.
A library that answers
Your documents, notes and recordings become searchable evidence the assistant can actually cite, not context you paste in again every session.
Scope you choose
Point a question at the whole library, one project, or the open web. The answer tells you which it drew on.
Routine that runs itself
The steps you repeat become workflows the system performs, on a schedule or on a trigger, inside the same boundary.
And because every answer shows its work, you get sharper using it. Most AI makes you dependent. This one makes you better.
Paid for in euros, not in data
You pay for the workspace.
Not with your knowledge.
A subscription, in euros, for storage and included usage. That is the whole arrangement. There is no second business model reading what you put in.
-
Minimum
€9 /mo
-
Standard
€29 /mo
-
Plus
€79 /mo
-
Max
€200 /mo
Annual billing and Enterprise on the pricing page.
Bring your work somewhere it connects.
Sources
Sources for the statements marked above (2).
-
The account key is generated on the user's own device; LumaVista AI keeps no copy of it and holds no escrow of its own, so it cannot open the content of a locked, encrypted account; the exception is an always-on space the user chooses to switch on, for which LumaVista's servers keep a wrapped key so they can open that one space to run the user's automations, and every opening is written to that space's access log. An organisation may optionally enable escrow on a shared team workspace so that its own owners can recover that workspace's key; the escrow private key is generated in the browser and stored only in copies wrapped to those owners' devices, and it does not cover a member's personal account. Workflow data created before LumaVista's October 2026 custody change moves under the user's own key the next time they sign in; until then LumaVista's servers can still open it.
LumaVista AI — device-held encryption keys, generated on your device; no provider-held escrow, optional org-owner-held escrow on shared workspaces -
An always-on space is optional, has a single owner, and is off unless the user switches it on with a recorded acknowledgement. While it is on, LumaVista's servers keep a wrapped key for that one space and can open it, through a separate key service and only for purposes registered for that space, to run the user's automations while the user is signed out. Each opening is written to the space's access log, which the owner can read and which is kept for 12 months. Switching the space off prevents any new opening at once and destroys the service's key for it; the content stays in the user's account. Other workflow data created before LumaVista's October 2026 custody change can still be opened by the servers until its owner next signs in.
LumaVista AI — Security: always-on spaces (server-held wrapped key for one opt-in space, opened through a separate key service for registered purposes, every opening logged)