Your data
Yours to control.
Others collect your work, move it to their servers and ask you to trust them. Trust only goes so far once your data is no longer yours to control, so Jorv never asks for it. It runs on your machine, your cloud account or a closed network, with your own AI keys. We don't hold your data, because we never see it. The only thing we keep is your licence.
Where it runs.
Now
Your own hardware
A laptop, a server or an office network. One download; the free tier lives here.
Now
Your cloud account
Our stack in your own AWS or Azure account, under your keys. Nothing of ours in the path.
Now
A closed network
Fully offline, with no path to the internet, with local models and an offline licence.
One boundary
Knowledge comes in. Nothing leaves until you approve it.
What you already have flows in: notes, tasks, docs, emails, wiki, code, design, deals, reports. The web, your sources and any AI model feed knowledge in through a one‑way gate.
What leaves
- What you approveReports, decks and documents, apps and sites, client deliverables. Nothing goes out until a person says so.
- What you ask the AISent straight to the provider you chose, under your own key. With a local model, it goes nowhere.
- Your licence detailsYour sign-in email and your licence, so we can issue and renew it. Nothing of your work.
What never does
- Your work and your recordMissions, items, documents, decisions and files stay where you installed Jorv.
- Your AI keysEncrypted on your machine. Only the engine uses them.
- How you use JorvNo telemetry and no analytics by default. A crash report is sent only if you choose to send it.
Your own AI keys
Any model. Your account. Your bill.
Bring a key from any AI provider you like, or run a model on your own hardware. You pay the provider directly, at their price. Jorv adds no markup.
- Choose a model for each role, with a fallback if one is unavailable.
- Every call, token and dollar on the record, with a spending cap on a deployment, a team or a mission.
- A local model keeps every request on your own machine.
What that means for your security team.
Access follows the work
You see a project because you are on its team, approve because you review it, publish because you own it. Leave the team and the light goes out at once.
A record written once
Who read what, who drafted, who approved, which model, which sources: kept, never quietly changed. The record Article 12 of the EU AI Act describes, as a matter of course.
Exit is total
Database, files, code and the master key move whole. An exportable report proves where it runs, who holds each key and what has left.
Under the hood
One engine, written in Rust.
Everything Jorv knows and does lives in one program, written in Rust: the language chosen where software must be fast, safe with memory and dependable for years. It is why Jorv installs as a single download, runs on a laptop or a closed network, uses little of your machine, and behaves the same on every surface.
The only thing we keep is your licence.
What we hold is your Microsoft or Google sign‑in email and your licence details: your organisation's name, the tier and the seat count. Nothing of your work, ever.