About

We took the bird out of the cage.

Lovault was not built to add features to an assistant. It was built because the assistant was in the wrong place — sealed in a text box, answering questions about a world it could not touch.

Why it exists

It started as a complaint.

I have more ideas than I have places to put them. Notes in four apps, voice recordings nobody will ever listen to again, terabytes of camera footage, photographs going back to when I was a baby, and half-finished thoughts scattered across a dozen conversations with a model that forgets them the moment the tab closes.

The tools were all good. None of them were in the same room. Every useful thing I wanted to do required me to be the courier — copying between a chat window, a folder, a document and a drive, and being the only part of the system that knew why any of it connected.

So I stopped adding tools and built the room. One workspace where the model works in the material instead of beside it: in the document, on the folder, against the archive, and — when the feature I need does not exist — in the source code of the workspace itself.

The idea in one line

A thought transformer.

Describe

Say what you mean

In writing, out loud, or by pointing at something that already exists in your archive. The input is a description, not a menu path you have to learn first.

Transform

It becomes material

A document, a shape, a model, a map, a report, a piece of the app. The step that used to be "now go and make it" is the step that disappears.

Keep

Nothing falls out

Every prompt, every reply, every artefact lands in a subject folder on your disk, laid out in time. The conversation is not the product; the archive is.

“If you can describe it, if you can visualise it — you can turn it into something real.”

What we will not do

Four positions, not features.

Your machine is the product. Lovault is a server that runs on your computer. We hold no account, no copy and no index of your work. There is no "export my data" button because there was never an import.
We are not your AI vendor. You bring your own provider key; requests go from your machine to whoever you chose. We are not in the middle, we take no margin on your tokens, and swapping provider — or running a model locally — is a setting.
Nothing is deleted quietly. Removing something moves it to an archive inside the project it belonged to. If a thing is genuinely destroyed, the app says so in those words before it happens.
The app is yours to change. Build mode gives the model your copy of the source. A feature you need and we have not written is a sentence away, and your install stops being identical to everyone else's.

Who is behind it

One person, so far.

Matei Șuță

Founder and, at present, the entire engineering department. Lovault began as a personal tool for a problem I actually had, and every feature in it was written because something I was trying to do that week was impossible without it.

It is developed in the open the same way it is used: the app is asked to change itself, the change is tested, and what shipped and what broke is written down afterwards. The version number in the corner of the app moves most days.

Where it stands

Alpha, honestly.

Lovault is real software that does real work every day — but it is alpha, and the word is on this site deliberately. Features land quickly, some of them break, and the parts that are planned rather than built are on the roadmap and are not described anywhere on this site as though they exist.

There is no company to speak of, no funding round and no pricing. What there is: a working application on two platforms, a changelog that goes back to the first version, and a clear idea of what the next two years look like.