Independent project log · Switzerland
I’m Eliott. I’m building Jarvis, experimenting with local AI, and learning how to run the systems behind it myself.
This page is a record of the work, not a polished product launch. Some pieces already run; others are still on the bench.
On the workbench
They connect to the same question: what can I build, understand, and operate myself instead of treating technology as a black box?
A personal assistant with voice and chat interfaces. I’m working through the ordinary but important details: how it listens, how a response is shown, and how the controls behave when nothing is happening.
Ready and listening voice states, a chat view, and settings for local AI and spoken replies.
Jarvis includes a local AI setup. The current settings screen shows a Llama 3.1 8B model and a local Piper voice. I’m interested in what can run on my own hardware, and where it still needs work.
The model is marked ready in Jarvis settings. That does not mean every assistant workflow is finished.
A machine I can use to learn containers, virtual machines, storage, and networking by running real services. It would also give Jarvis a place to grow beyond a single development setup.
Dedicated hardware and a documented deployment. I’m not presenting a finished server rack.
Jarvis has a place for Home Assistant in its settings. Connecting it responsibly—checking device state and requiring approval before control—is a future integration, not a live claim.
Home Assistant is shown as “Not connected” in the supplied settings capture.
The interface, not a mockup
The voice screen has distinct states. When it is idle, Jarvis tells me how to begin. When listening starts, the central label changes and the stop control becomes available. The chat view offers a quieter way to type a request.
The screenshots here are from my current build. They show the interface; they are not a benchmark or a claim that every integration is complete.
What I’m still shaping: reliable voice flow, useful responses, and a setup that can run locally.
Loading the listening-state screenshot…The listening-state screenshot could not load. Open it directly using this link.
Loading the chat screenshot…The chat screenshot could not load. Open it directly using this link.Notebook / 2026
Public project pages can make prototypes look finished. I’d rather keep a clear line between the interface I can show today and the infrastructure I still want to build.
This is a new project page. I don’t have meaningful traffic numbers or a publishing track record to present.
Hardware / collaboration
I’m looking for a desktop, mini PC, laptop, NAS, or small server suitable for a home lab in Switzerland. New is not essential: refurbished, previous-generation, demo hardware, or a long-term loan could all be useful.
I can share a concrete use plan and honest feedback. I’m not offering guaranteed reach or pretending this new site has an audience it does not have.
contact@eliotteliott.xyz
