Livinity
Livinity is an open-source homeserver OS with a built-in AI agent called Liv. It turns a spare PC into a private AI homeserver with 495+ one-click Docker apps. Users can bring their own Claude or Gemini key for privacy.
Livinity: Open-source homeserver OS with a built-in AI agent | Product Hunt
Livinity
Launching today
Open-source homeserver OS with a built-in AI agent
26 followers
Open-source homeserver OS with a built-in AI agent
26 followers
Visit website
Web hosting services
•
AI Workflow Automation
One operating system, one quiet interfacTurn a spare PC into a private AI homeserver. 495+ one-click Docker apps, plus Liv, an AI agent with MCP that installs apps and runs your containers for you. Bring your own Claude or Gemini key. Open source and TypeScript.
Overview
Reviews
Alternatives
Team
More
Free Options
Launch tags:Open Source•Developer Tools•Artificial Intelligence
Launch Team
Subscribe
Promoted
📌
Hey Product Hunt. We are Bruce and Alton, co-founders of Livinity.
We kept hitting the same wall with self-hosting: getting apps running is easy now, but the box still needs a sysadmin. So we built the homeserver OS we wanted, with an AI assistant baked in.
Livinity gives you a clean dashboard and a one-click library of 495+ Docker apps (Nextcloud, Plex, Home Assistant, n8n, and more), plus Liv, an AI assistant. Liv uses MCP, so you can just ask it to install an app, manage a container, find a file, or set up an automation, and it does the work on your system. It even remembers context across sessions. You bring your own model (Claude or Gemini), so the intelligence is frontier-grade but your data never leaves your hardware.
It's fully open source , TypeScript end to end. Self-host it from one curl | bash, or use the managed cloud at livinity.io with zero setup.
Would love your feedback, especially on the Liv experience and which apps you'd want next. Happy to answer anything. 🙏
Report
1d ago
The bring-your-own-key model (Claude or Gemini) so data never leaves the hardware is exactly the tradeoff I want from a self-hosted setup. Curious about the Liv side: when it installs an app or edits a container via MCP, is there a confirmation/dry-run step before it changes state, or does it just execute? Would love to trust it with automations but want a guardrail on destructive actions.
Report
1m ago