Overview
Open Source

Your day.LIA keeps up.You decide.

Your open-source personal AI assistant, ready to self-host.

See LIA in action
The code and setup guide
Built in FranceOne server, separate accountsApprove sensitive actions

Sign-up by email: you confirm your address, then the administrator activates your account (automatically on a demo instance).

Scroll to explore

Stop choosing between the power of an assistant that acts on its own, the comfort of a real workspace and control over your digital life.

Personal AI assistants take several approaches. Agents such as OpenClaw and Hermes Agent are powerful at running commands and automating tasks. Their chats, consoles and shared profiles offer plenty of freedom, with technical setup to take in hand.

Consumer assistants such as Meta Muse offer a smooth, accessible experience. You can follow their actions and take over, while your data stays on the publisher’s servers and the publisher manages the hosting.

60+

functional building blocks

LIA brings these two worlds together and creates her own category: a personal, family and sovereign AI platform from end to end, installed on the server of your choice.

A complete environment of 60+ building blocks under the free AGPL license, combining an AI that can act for you, everyday tools that use no AI at all when you work them yourself, and professional-grade safeguards.

Beyond agents: a personal, family and sovereign AI platform

The power of an assistant that acts on its own and the comfort of a real workspace, plus control over your data and a place for the whole family.

The power of an AI agent, without the compromises

LIA works in two ways: following a checked plan step by step (Pipeline mode), or searching by herself, attempt after attempt, when the request is open-ended (ReAct mode). Like OpenClaw and Hermes, she can also take real action: drive a web browser, run exact calculations in an isolated space, plug into third-party tools (MCP servers and their apps) and learn new know-how through skills and plugins, including the ones she writes for you and you install in one click.

The “Manual + AI” hybrid: AI only when you call on it

Why pay an AI and wait for its answer to archive an email or move a meeting? LIA gathers your everyday tools in one interface: Gmail, Outlook, iCloud, calendars, tasks, contacts, Google Drive, OneDrive and even your Philips Hue lights. When you do it yourself, your actions go straight to your providers: no AI involved, no cost, no answer to wait for. And one click on a yellow star brings LIA in.

A platform for the whole family, with a face and a 3D world

An assistant shouldn’t be a lonely program on a developer’s computer. LIA welcomes your family and close ones on the same server: everyone gets their own account, data and spending limits, with sharing you choose and connections between your accounts. She comes alive with animated avatars and a 3D world you explore together.

Beyond text: live voice, phone and media

LIA talks with you live, in a real spoken conversation where you can cut in at any time (two real-time modes: Live and Live direct). She can call you, or call someone for you once you approve, keep an archive of your text messages, host a personal radio made for you and create images.

Governance, GDPR and professional-grade monitoring

Self-hostable with Docker and free under the AGPL license, LIA ships what experimental open source projects often lack: management of several accounts, spending caps per person, the cost of every exchange shown to the cent, your approval before sensitive actions, the GDPR tools (full export of your data, right to be forgotten) and Grafana dashboards to follow activity in real time.

Head to head: why choose LIA?

Six criteria, three duels: pick who LIA takes on.

LIA versus

LIA

The sovereign butler

“Does the dirty work, keeps your data at home and won’t empty your wallet.”

Frugal: AI costs nothing when you do it yourself

OpenClaw

The caffeinated hacker

“Lives in your terminal, speaks fluent Bash, never sleeps.”

Appetite: AI gets to work when you give it a task

  1. Acting on its own

    Yes

    Two ways of working, real tools

    As muscular as a developer’s agent, yet kept in check when it matters.

    • A checked plan step by step, or a search of her own
    • A driven browser and exact calculations in an isolated space
    • Third-party tools (MCP), skills and plugins, including the ones she writes
    Yes

    Runs commands on your machine

    Powerful, but watch out for over-enthusiastic commands.

    • System commands and a driven browser
    • Scheduled tasks, skills and plugins
  2. Everyday use, and what it costs

    Yes

    Your tools by hand, LIA as backup

    You don’t pay an AI to archive three emails.

    • Mail, calendar, tasks, files and Hue lights, with no AI
    • Your actions go straight to your providers
    • A yellow star to ask LIA for help
    Partly

    Chat and a web console

    Chatting with a bot just to move a meeting gets old fast.

    • WhatsApp, Telegram, Discord or its web console
    • AI carries out the tasks you request in chat
  3. Family, close ones and 3D

    Yes

    The whole household on one server

    The assistant where the whole household belongs.

    • One account per person, activated by the administrator
    • Sharing and connections between accounts
    • Animated avatars and a shared 3D world
    Partly

    Several people, set up by hand

    Flat-sharing, yes. The lease, you write it yourself.

    • Individual sign-in, profiles and roles
    • Shared trust between participants, no 3D world
  4. Voice, phone and media

    Yes

    She talks to you live and makes your calls

    She talks with you, makes your calls and hosts your radio.

    • Two real-time voice modes
    • Calls once you approve, an archive of your texts
    • Personal radio, images and meeting summaries
    Yes

    Live voice, phone as an option

    It picks up the phone too… once the plugin is installed.

    • Continuous voice conversation in its apps
    • Calls through a plugin, generated images and music
  5. Memory and control

    Yes

    A memory you can see and correct

    Nothing important leaves without your green light. And you see everything.

    • Memories you can browse and edit
    • Follow-up of your close ones and pending promises
    • Your approval before what matters, export and erasure
    Partly

    File-based memory, guardrails to set

    Great freedom, great responsibility.

    • Memories written in readable text files
    • Command approvals depending on the mode you pick
  6. Administration and costs

    Yes

    Everything is set and measured

    An IT manager’s dream: everything is measured.

    • Accounts and spending caps per person
    • The cost of every exchange shown to the cent
    • Self-diagnosis and Grafana dashboards included
    Partly

    A web console, measurements to wire up

    Everything is measurable… if you build the dashboard.

    • Estimated cost of every answer
    • Exportable metrics, Grafana to install yourself

Sources

What this table says about other assistants comes from their official documentation and announcements, read on November 16, 2026.

These projects move fast. Report an error

One day, many ways to help

Pick up the thread. Prepare what comes next.

Finding the right file, keeping a commitment, preparing your next conversation with someone: LIA works with what you have chosen to open up to her.

An assistant that gets to know you

Her memory, the Relations page and your knowledge spaces let her pick up the thread without you having to tell the whole story again.

Proposals you can inspect

You review her sources and drafts, and you approve anything sensitive. The registers keep a record of what she read, what she tried and what came of it.

An app you can make your own

Designed in France and open source under the AGPL license. Use an existing instance from your browser, or install your own with Docker. Hosting and external services may cost money.

What you share today can help tomorrow.

LIA can use your preferences, your exchanges and your commitments for your next request, within the limits of the enabled features and the sources you have authorized.

Your reference points
Your preferences, memories, rules and knowledge, which you can view and correct.
Your relationships
Each person, with your exchanges and open commitments, to prepare your next contact.
Your next steps
Your appointments, projects and follow-ups, drawn from the sources you allow.
Your choices
Your answer style, your interests, your sources and the times when LIA may reach out to you.

For example, before you meet Claire again…

The Relations page finds your last exchange with Claire and the commitment still open. In the conversation, LIA helps you prepare the meeting from the sources she can access, and gets to the point because you prefer concise answers.

When you ask
A summary based on your file and on what LIA found.
When LIA suggests
A useful signal, drawn from your sources, in the time windows you have allowed.
When you delegate
An action prepared for you, which you review and approve when it needs your consent.

You can view and correct her memory, limit her sources or switch off her initiatives. Keep a critical eye, too: her conclusions still need checking.

CHAPTER 01

Do it yourself, or ask.

Your mail, calendars, tasks, contacts, files and lights each have their screen. You work by hand, with no AI, and hand over to LIA when that is simpler.

Your tools: the mail, its folders and an open message, without going through the chat.

Your tools: the mail, its folders and an open message, without going through the chat.

  • Six tools, one way of working.Gmail, Outlook or iCloud, Google Drive or OneDrive, Philips Hue: each tool acts on the account you connected, on the same screens from one provider to the next.
  • By hand, no AI comes into it.Your gestures go straight to your provider, with no token to pay. Nothing is added to LIA’s registers, her memory or your journal.
  • And LIA takes over when you want.Yellow stars ask LIA to sum up, write, translate or fill a form: a proposal to read, the cost shown, nothing written at your provider. “Ask LIA” opens the chat on it, and nearly all of it can be asked in conversation, with a card to confirm as soon as it reaches someone else.
What makes this possible

Each tool talks directly to the service you connected, through an interface that does not depend on the provider: what a service cannot do is not offered, and what failed is said. Nearly all you do here, the assistant can do too. Deleting for good stays yours.

Explore the engineering : One screen per tool, shared by Google, Microsoft and Apple · Gmail, Outlook, iCloud · Google Tasks, Microsoft To Do · Google Drive, OneDrive · Philips Hue · search across every tool (Ctrl+K) · PDF and Word read in the page · by hand, no model call · yellow stars: one click, one proposal.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

I sort a mail and answer an invitation, without going through the chat.

What you can get

The gesture goes straight to your provider, with no AI call, and nothing enters LIA’s registers.

Possibilities you can combine

Tools: your services, by your own hand

Open Tools when you would rather do it yourself. Your mail sorts on Gmail, Outlook and iCloud, with a moment to take a message back. Your calendars answer invitations and repeat events on the three providers, your tasks gather under Today, Overdue and Coming up, your contacts keep their photo, groups and vCard. Your files live on Google Drive or OneDrive, and a PDF, a Word file or a spreadsheet reads in the page. Ctrl+K searches them all and says what it could not reach. By hand no AI is called, and what you do stays yours, out of LIA’s registers. Yellow stars ask LIA to sum up, write, translate or fill a form: one click, a proposal to read, the cost shown. Nearly all of it can be asked in conversation too, with a card as soon as it reaches someone else.

1 of 9

CHAPTER 02

Before, during and after your conversations.

Prepare the meeting, talk out loud, then find what was decided and what is left to do.

Detailed meeting report · inspect participants, summary, decisions and assigned actions.

Detailed meeting report · inspect participants, summary, decisions and assigned actions.

  • Before: the context and useful questions.LIA gathers the documents, the latest exchanges and the meeting decisions. You walk in knowing what needs clearing up.
  • During: speak and interrupt naturally.Talk to her in Live with your Gemini, OpenAI or ElevenLabs key. The voices on offer, and what the voice can hand over to LIA, vary by provider.
  • After: minutes to correct and share.Record the meeting, review the decisions and action items, then share the PDF. Once the minutes are indexed, you can find them again in conversation.
What makes this possible

For a precise request, Pipeline mode prepares a plan; to explore, ReAct mode adjusts its searches along the way. Either way, the sources used, the proposals and the confirmations stay attached to the work.

Explore the engineering : 38 agents working in parallel · live voice sessions on your own Gemini, OpenAI or ElevenLabs key · five voice engines, including Fish Audio · phone calls placed by LIA through your ElevenLabs connector · browser control · Philips Hue · images and diagrams on demand.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Prepare my day from my calendar, my tasks and the relevant emails.

What you can get

The specialists bring together the sources they can access, and independent steps can move forward at the same time.

One request, several coordinated actions

38 specialised agents

Emails, calendar, contacts, files, tasks, weather, web search, places, routes and reminders: LIA can get the specialists a single request needs working together. Independent steps can move ahead in parallel, while those waiting on a result keep their order. You stay in the conversation to prepare your day or pull together the pieces of a project. The available capabilities depend on your access and on the instance, and the time it takes depends on the work, the models and the services used.

1 of 17

CHAPTER 03

Your day has context. LIA brings it back.

From the briefing to your personal radio, your appointments, your commitments and the topics you follow come together in one day.

Relations · review conversations, useful facts and open commitments before getting back in touch.

Relations · review conversations, useful facts and open commitments before getting back in touch.

  • Memory you can correct.Preferences, people, projects, rules: see what LIA remembers, correct it, pin what matters or delete it.
  • Read your day or listen to it.Read the essentials on the dashboard, or listen to a radio built from your day and the news sources you have authorized.
  • Prepare for your next conversation with the full picture.In Relations, your own small CRM, each card brings together exchanges, remembered facts, calls and open commitments. You prepare your next conversation with what matters for that person, not with a plain contact list.
What makes this possible

Memory helps LIA understand your request, and the connected sources tell her what is happening now. The briefing and the radio each have their own settings for choosing their sources.

Explore the engineering : dual-vector semantic memory · introspective journals · daily briefing · private SMS archive · Psyche Engine (14 moods, 22 emotions, an experience grounded in evidence).

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Remember that I prefer appointments after 10 am.

What you can get

A lasting preference that you can view, correct or delete, and that LIA can recall when a request concerns it.

Your context stays within reach

Contextual memory

LIA keeps your preferences, your relationships and your standing instructions, recalls what concerns your question and can look up a subject that came up along the way. A new instruction is pinned straight away, safe from automatic corrections and clean-up. You can edit it, unpin it or delete it, and bring an export of your memories back in. A fact that changes keeps a dated record of its previous version, and resetting the chat keeps what she has learned for the long term.

1 of 11

CHAPTER 04

Pick up the project at the right moment.

An awaited reply, a deadline, a useful signal: routines and proactivity connect what comes in to what you are working on.

My commitment

Fictional example

An already configured routine watches Marc’s new emails about the Atlas committee.

LIA brings the useful context together

Your commitmentsOriginal commitment · 3 pm
Your emailsMarc moves the committee to 2 pm
Your routineConfigured watch · new emails

The change and a reply to review

Watch turned on at your request, at the instance’s pace; the signal doesn’t decide for you.

Illustrative scenario: fictional people, data and outcomes.

  • A condition, then the right next step.Choose the condition to watch and the work to start. LIA checks the condition at the pace set by the instance, and starts the next step only if it is met.
  • The alert comes with context.Your available sources, your projects and your interests help LIA make you a useful suggestion. You can adjust this help or turn it off.
  • Visible follow-up between requests.Reminders, habits, scheduled actions and tickets keep their state in the app: you see what is waiting and what got done.
What makes this possible

A conditional routine checks the rule you set before starting the planned work. Proactivity can also link something new to your context, to put what deserves a decision in front of you at the right time.

Explore the engineering : configurable proactive intelligence · opt-in proactive discussions · interests · natural-language reminders · scheduled routines · health tracking.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

On this ticket, I hand LIA the job of preparing the file.

What you can get

LIA works in the chosen mode, comments on her findings and asks on the ticket for the confirmations she needs.

Work followed through to its result

Hand a ticket to LIA

Hand her the ticket: she takes it, does the work in Pipeline, ReAct or automatic mode (your choice, set on the ticket), comments on what she found and gives you back the result to approve. When she runs into something she can’t do alone, she neither gives up nor decides for you: she asks on the ticket, showing what she is about to do, and one comment is enough to answer: yes, no, or what needs to change. She follows up on what is late or left waiting, pointing to what is really waiting.

1 of 12

CHAPTER 05

Delegate the action. Keep the decision.

Before a sensitive send or call, you see what LIA proposes. Afterwards, you find the result and the recorded spend.

A phone call

Fictional example

Call Les Jardins restaurant to ask for a table for two on Thursday at 8 pm, outside if possible.

LIA brings the useful context together

Your calendarFree after 7 pm
Your preferencesTwo · terrace
Your approvalBefore the call

A specific proposal before the call

Try confirming: this demo makes no call.

📞
Les Jardins (Demo)
Callee: Les Jardins (Demo)
Phone: (202) 555-0100
Objective: Ask for a table for two on Thursday at 8 pm, outside if available. Do not accept another time without checking with me.

Draft to review

The call starts only after you confirm, if telephony is configured.

Illustrative scenario: fictional people, data and outcomes.

  • A real proposal to review.Recipient, content, purpose of the call: you confirm the exact action, and you can touch up the draft before approving.
  • A proposal is not a result.The actions register and the consultations register show what LIA did and what she read. A failure or a limit stays visible there.
  • Readable costs and budgets.The calculated tokens and cost appear with the answers. Ceilings can be set for each account and for the instance.
  • Choose your hosting and models.Host the app yourself and export your data. The external models and services you choose receive the context needed for the requests that go through them.
What makes this possible

You confirm the concrete action: the recipient, the message or the purpose of the call. The registers keep every attempt and its outcome, failures included, so you can find out what happened.

Explore the engineering : Approvals at tool level, editable drafts, action and consultation records, budgets and encryption.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Prepare this email to Claire and show me the draft before sending it.

What you can get

You check the recipient and the content, then you confirm, edit or decline.

A decision that stays yours

You stay in control

LIA shows the native actions she prepares for your approval: you can inspect the draft, change it or refuse. A task with several drafts presents them one at a time. For MCP, your account, server and tool choices determine the questions; their effect is visible in Settings. The report beneath the answer names what actually ran.

1 of 4

Security & Privacy

Data protection is part of LIA’s architecture. The browser does not receive connector credentials: a dedicated backend keeps the tokens in server-side sessions. The context an answer needs may be sent to the chosen model provider, after personal data has been filtered and minimized. Passkeys, the second factor and a step-up confirmation protect your account, and skill code runs in an isolated, throwaway container. Content from a third party stays data to analyze, never an instruction. From design to operation, every version is built on pinned, verified building blocks, then monitored in production.

  • Data control

    Your account data is scoped to your session, and you can export it. You see the connected devices and can revoke them, and the daily backups have a tested restore. Model and service providers may receive the minimum context that the features you turn on need.

  • Secure architecture

    A dedicated backend (BFF pattern), with HTTP-only cookies and Redis sessions: connectors’ OAuth tokens are never exposed to the browser. Passkeys and a TOTP second factor, with re-authentication for certain sensitive account operations, such as managing the second factor or exporting. A strict CSP, coverage of the OWASP Top 10, and third-party code run in a throwaway container, with no socket and offline except toward allowed hosts. A page LIA writes runs in a frame with no origin, under a policy that names no host. A Google sign-in proves an address, never a right: it can neither activate nor unblock an account. Every page LIA reads is fetched at the verified address, redirect after redirect, so none can lead her into an internal network. A client that probes unknown addresses or racks up refused sign-ins is banned for a while by all the server’s workers at once.

  • Encryption

    Connector credentials are encrypted with Fernet and passwords are hashed with bcrypt. A reset link is valid only for one account and one password, each account receives only a few reset emails a day, and the operator can add Cloudflare’s anti-bot check to sign-up, sign-in and reset. Some features give the browser temporary session access or a restricted Google Maps key; the provider’s restrictions and quotas are still needed.

  • Privacy and GDPR

    Pseudonymization, data minimization and the filtering of personal content in technical logs help protect privacy; debug mode can keep more. The export includes readable Markdown, JSON and the files, without the secret credentials. A contact’s photo is redrawn before it leaves, without its GPS tag. The registers show actions, consultations and initiatives: they are transparency tools, not a general certification under the GDPR or the AI Act.

  • A verified software supply chain

    Every building block of the server is pinned by its digest, and every version publishes the exact inventory of what it contains (CycloneDX SBOM). A weekly watch reads each dependency’s security advisories, and an update waits out a cooling-off period and never moves backwards. Before it is published, every version is installed on clean machines, and the code goes through the secret detector before every push.

  • Monitored operation

    In production, metrics, traces and logs keep only facts, never a name or a search. They feed dashboards and alerts, each linked to its resolution procedure. LIA reads these signals herself and diagnoses an incident from a bounded evidence pack, shown to the administrator. The monitoring tools stay on maintained versions.

Regulatory references and open standards
  • RGPD / GDPR
  • EU AI Act
  • MCP 2026-07-28
  • Agent Plugins 1.0
  • agentskills.io
  • OWASP Top 10
  • WebAuthn / FIDO2
  • OAuth 2.1 + PKCE
  • iCalendar (RFC 5545)
  • CalDAV / CardDAV
  • vCard
  • List-Unsubscribe (RFC 8058)
  • OpenTelemetry
  • Prometheus / OpenMetrics
  • CycloneDX SBOM
  • ISO/IEC 25010
  • Keep a Changelog
  • SemVer 2.0
  • Conventional Commits
  • WCAG 2.2 AA

Open standards rather than a home-grown protocol: what LIA speaks, another tool can speak too, and what she promises can be checked against a text written by someone else.

Read our privacy policy →

CHAPTER 06

From your sources to a useful deliverable.

Query your knowledge, compare it with the web, and get a comparison, a document or a mini-app that fits what you need.

Organize knowledge with documents and synchronized sources

Organize knowledge with documents and synchronized sources

  • Your knowledge joins the work.Documents, Drive or OneDrive folders and emails synced into your spaces: LIA finds the useful passages and their sources, without you having to copy anything over.
  • A response takes the right form.A table, a file, a diagram, or a game or a calculator that runs in the chat: information becomes something you can read, use or share.
  • Add the capabilities you need.Skills, plugins, MCP servers and read-only specialists widen what LIA can do. The code and the interface contracts are documented.
What makes this possible

Knowledge spaces find a passage by its meaning as well as by its words. Specialists can explore several leads in read-only mode, then LIA combines their findings into the deliverable. Skills and plugins then extend what she can do.

Explore the engineering : sandboxed skills with interactive widgets · pages LIA writes and runs in a sealed frame · knowledge spaces (15+ formats, hybrid search) · MCP protocol · open source.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Explore several leads on this topic and compare their sources.

What you can get

Read-only specialists each work within their own budget, and LIA can bring their findings together.

One request, several coordinated actions

Sub-agents

For in-depth research, an analysis that cross-checks several sources or an expert summary, LIA hands the work to temporary specialists who move forward in parallel, each from their own angle, then she coordinates and summarizes their results. Each sub-agent works in a bounded loop, with an explicit list of allowed tools and its own budget, so a delegation never spirals out of control. Every delegation is written into your registers, like any action of LIA’s.

1 of 9

CHAPTER 07

With family, friends and colleagues.

One server, one assistant per person. Connect the people around you, coordinate your availability and share messages, images or useful tools, with everyone keeping their own space.

Dinner with Sarah

Fictional example

Find a time tomorrow evening to have dinner with Sarah at Les Jardins. Prepare the invitation for me to review.

LIA brings the useful context together

Connected LIASarah · accepted connection, same instance
Approved accessAuthorized availability only
Your calendarYour calendar · free tomorrow at 7:30 pm

Your invitation is ready to review

Accepted connection on the same instance; no general access to Sarah’s data.

Illustrative scenario: fictional people, data and outcomes.

  • Coordinate with fewer back-and-forth messages.A dinner with friends, a family get-together or a catch-up with colleagues: LIA matches up the shared time slots and the information each person has authorized. To pass on a message, you approve the text, then the other person’s assistant delivers it and reports the outcome back to you.
  • Useful know-how to pass on.Share an image, a skill, an MCP server or a plugin with an accepted connection. A capability received is a disabled copy, without your connections or your personal credentials, and the person receiving it chooses whether to configure and activate it.
  • Individual context. A shared instance.Each account keeps its own connectors, memory and preferences. You choose what you share for reading, you see who accesses it and you can withdraw those rights. The administrator keeps control of the server’s accounts, capabilities and budgets.
What makes this possible

Relaying a message, opening read access and sharing a capability are three different acts. For each connection, you define what the other assistant may look at: your time slots, the titles of your events or the titles of your tasks. You approve every relay and every capability share. Withdrawing access stops future reads, but a copy already received stays independent.

Explore the engineering : Rights and blocks checked every time, a log of consultations, relay after approval, a preview of what will be shared, identical to what you confirm, received copies installed disabled, and visible provenance.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Tell Sam I’m picking up the kids tonight.

What you can get

The message is queued directly for your accepted connection’s assistant on the same instance, without a confirmation card.

The conversation continues between assistants

Your circle, assistant to assistant

Find people on your instance by deliberately searching for their exact name or email address, then accept your connections. Ask LIA to pass on a message: it leaves without a confirmation card, their assistant delivers it, and the outcome comes back to your thread. A reply can be prepared right under the message. For a known connection, a first name is enough; if several people share it, LIA asks you which one.

1 of 7

When LIA World is available, its directory also shows you your accepted connections and their general presence. Discover LIA World

CHAPTER 08

Step into LIA’s world.

A house to explore, a garden to take a break in, people to meet. LIA comes along with you, and the features you know are a few steps from your home, which stays private.

LIA World · a shared house and garden, your avatar and companion.

LIA World · a shared house and garden, your avatar and companion.

  • LIA beside you.Call her over, let her follow and open your personal conversation without leaving the world. Your knowledge awaits in the library, your meetings in their room and your creations in the multimedia studio.
  • A world in step with your day.Day and night follow your local time, and rain, snow or sunny spells reflect the recent weather LIA already knows, when she has it. From the garden to the cafeteria, each place has its own soundscape, at the volume you choose.
  • Together, with room for privacy.Meet the people who are there, write privately or join the public discussion. Have a message translated if you like, and personalize your character and your home’s colors. Your documents, your memory and your conversation with LIA stay private.
What makes this possible

The library opens your knowledge, the engineering lab your skills and extensions, the divination room your routines and the multimedia studio your creations. The Functions directory gives access to the other activities of your account. Every entrance keeps its rights and confirmations.

Explore the engineering : Canvas 2D in your browser, shared presence checked by the server, panels specific to your account, and private messages. Moving around calls no model, and translations go through the usual quotas and cost register.

Explore the capabilities

Choose a topic to see what it brings you.

Example request

I enter LIA World and head to the library.

What you can get

A shared place in isometric view, with your avatar and LIA; the library opens your private knowledge tools.

Shared places, personal tools

LIA World

Explore a house and its garden in isometric view, with your avatar and LIA beside you. The minimap, the keyboard and the touch controls help you get from one place to another. Each room opens LIA’s usual features in private, and walking in sends no message and starts no action. Availability depends on your instance’s settings.

1 of 13

The places, and what you find there

Push a door open, walk up to an object or go through the Functions directory. The shared areas welcome everyone, but the tools you open stay personal.

Social atrium
Meet by the fountain and benches; the connections board opens your links with other people.
Meeting room
From the meeting table, you find your meetings, their recordings and their minutes, just as in the app.
Multimedia studio
The drawing table prepares an image request; your images, documents, screenshots and kept answers live in their galleries.
Phone booth
Prepare a call, find its history and the mail shortcuts; sending keeps the usual confirmations.
Memory archives
The archives open LIA’s memories: inspect, correct or delete what your assistant retains.
American diner
The reading desk leads to news; the jukebox opens your personal Radio. Booths offer somewhere to pause.
Engineering lab
Skills, MCP servers, plugins and task shortcuts are in this place’s directory.
Gym
Habits and health measurements have their own panels, and the equipment gives access to the activities set up there.
Divination room
The crystal opens routines and the telescope weather; the directory also offers calendar and scheduling shortcuts.
Library
The shelves open your knowledge spaces and documents, with the same sources and access as the application.
Restroom
Private access to your SMS through the authored object and this place’s function directory.
Garden
Your interests, a walk among trees and the pond; seats let you pause near LIA or other people.
Terrace
An outdoor place to meet or rest, with seats and an atmosphere that follows the time of day.
Theatre
A pavilion for privately rehearsing a difficult conversation, then reviewing the dialogue and Theatre feedback.
My studio
Your private space: colour palette, avatar mirror, Relations, Workboard, reminders and commitments. Its contents remain yours.

The features on offer depend on the services and capabilities enabled for your account. Shortcuts open your usual tools, with their permissions, costs and confirmations.

And everything else, obviously.

Your emails, calendar, contacts, tasks and files feed one personal context. Connect Google, Apple or Microsoft, depending on the services available: LIA can match this information with your preferences, your commitments and your knowledge to help you, in one place.

  • Emails
  • Calendar
  • Contacts
  • Tasks
  • Files, Drive & OneDrive
  • Weather
  • Places & routes
  • Web search
  • Photos & documents analysed
  • Voice — in your language
  • 6 UI languages
  • PWA · Telegram · push
  • Themes & dark mode

Explore the capabilities

Choose a topic to see what it brings you.

Example request

Find a place near my home and a route to get there.

What you can get

Search, places and routes depend on the configured services, your access and the information available.

Answers connected to your sources

Search, places & routes

Bring your context and public information together: search across several sources with Brave, Perplexity and Wikipedia, or with the instance’s own web search when you have no key, reading of accessible, supported public pages, nearby places, and routes by car, on foot, by bike or by public transport. With your consent, a saved location can help local answers while you are on the move, and how old it is stays visible. Search, places, routes and weather depend on the services configured on the instance, your access and the data provided. When an answer lists places, a Position card numbers them on a single map, and choosing one shows the details already gathered along with a billed route from where you are.

1 of 10

LIA has nothing to hide.

Inspect costs, registers and code. Choose your infrastructure and the providers you entrust with your requests.

Every message: 🟠 1 240 IN 🟢 210 OUT · 0,003 €

A fictional example of the counter: the cost is calculated from the configured models and rates, and varies from one request to the next.

Costs become visible

Tokens, cache and cost are calculated in the conversation, with budgets per user and for the instance. External services are still billed by their own providers.

A public audit, including its limits

The method, the findings and the points to improve are published, and each finding is tracked in a public register until its proof is recorded. You can examine that evidence, but the report is not a certification.

Read the audit report →

Open software under AGPL

Read the code, install the app on your own infrastructure and explore the documented choices. Connected services and models remain separate choices.

View the code →

Design decisions explained

The architecture, the technical decisions, the guides and the field report are all available, so you can understand how LIA is built and run.

Read the story →

The software is open source; hosting and your chosen services may incur costs.

Try it, knowing everything

A day with LIA.

Keep scrolling: the day moves with you.

Before the meeting, you ask where things stand with the client: the latest exchanges, the quote and the meeting decisions are gathered, with the questions still open.

“Suggest two slots and keep my Wednesday free.” LIA puts your remembered preference together with your calendar, then prepares an email you can correct.

Your routine spots the supplier’s reply and starts the planned follow-up: compare the new proposal with the file and summarize the differences for you.

The ticket handed to LIA holds her research, her result and what she needs from you. You pick up the thread without starting over.

A simple interface. Serious operations.

For your family, your team or your friends: a web app where everyone has their own account, with the tools to understand how it works and to step in.

What the operator can see

Grafana: instance and container resources

Grafana: instance and container resources

LIA’s Grafana screenshots: instance resources, token usage, costs and cache. More than 30 complete dashboards.

One server for several people

Each person has their own account, connectors, memory and preferences. You manage users and capabilities from the interface.

Your models and limits

Choose the models role by role, use Ollama locally and set the budgets for the instance and for each account. Optional services are configured to suit your needs.

Grafana dashboards shipped with LIA

Costs and tokens, latency, errors, Pipeline and ReAct modes, confirmations, connectors and infrastructure: the dashboards show you how the instance is running.

Signals to act in time

Prometheus, Grafana, Loki, Tempo and Alertmanager bring together metrics, logs, traces and alert rules. You choose the recipients and the services of this stack to suit your deployment.

A foundation for your internal company assistant.

Preparing meetings, finding business knowledge, keeping track of commitments: these uses can help your colleagues too. The multi-user web app, the connectors, MCP, the APIs and the observability stack form a foundation to customize and integrate into your environment.

Adapt the sources, permissions and usage rules to your organization. Identity, business integrations and hosting still have to be defined for your deployment, and the open code and the documentation help you scope that work.

Flow is built with care.

Finding the right context, organising the work, checking the result: every design choice should make your life easier.

  1. Connect the context

    Relevant passages from your documents come together with your exchanges and remembered facts.

    Less to explain again.

  2. Organise the work

    LIA divides the research and connects the steps that depend on one another.

    An intention becomes a result.

  3. Check what comes back

    She can refine a search, try another source and flag what remains unfound.

    Conclusions you can examine.

  4. Make actions clear

    Proposals, approvals and results each keep their place.

    You know where the work stands.

Explore the engineering choices

LIA links semantic routing with the tools and sources relevant to your request. For a task to carry out, Pipeline mode prepares a plan and checks it; ReAct mode moves forward through searches and adjustments. Choose the mode yourself, or let Automatic decide for each request. The whole path is measured end to end, from token to euro, with email alerts on the vital signs. Behind the interface, there is Bayesian plan learning, dual-vector semantic memory, hybrid BM25 and embeddings search over your documents, and a LangGraph state machine whose every step is saved in PostgreSQL. All of it can be self-hosted, down to a Raspberry Pi. LIA gives the model the information its tools retrieved, with instructions to tell facts, sources and gaps apart. When ReAct mode declares that it is missing something, it gets a limited recovery pass. The registers let you examine what was consulted and what was done. An answer can still be incomplete or wrong: you can check its sources and correct its conclusions. What runs is isolated from what runs it: a skill’s code runs in a container created for a single call, with no socket, no network beyond the allowed hosts, and read-only. If that sandbox cannot be built, nothing runs. The chat can read preferences and prepare operations on LIA’s resources, within the catalogue actually on offer. Each operation declares its parameters, its results, the interface sections concerned, the rights it requires and its confirmation rule. The values offered reuse the form’s choices and labels: the model doesn’t invent an option that doesn’t exist.

Registers of acts, consultations and initiatives

Three registers answer three different questions and are never mixed: what the assistant did, with the outcome and your confirmation; what it consulted to answer you; and what it undertook on its own. A consultation records the capability used, “your calendar”, never what was searched for. An action is written down before it happens and closed only on an explicit result: nothing is presented as done just because no error came back. The assistant also uses them to answer you: asked “what did you do this week?”, it counts instead of remembering. The three registers belong to you, can be read in the app, export whole with the exact total at the top, and disappear with your account.

One vocabulary across your data

A contact, an email, an event, a file, a place: each one has the same name everywhere, with a shared vocabulary of thirty-one terms rather than one vocabulary per integration. That is what lets a question cross sources: the person in an email is the same as the one in your calendar and your notes. The links between these items have a declared type and meaning, so the assistant reasons about relationships instead of guessing from names that look alike. And the vocabulary a new capability brings is checked at start-up, never discovered in use.

Native Shells & Wake Relay

One app per store, which connects to any self-hosted server: the WebView loads your server’s address with the same httpOnly-cookie session as the web. On Android, the app talks to your own Firebase project at runtime. On iOS, it is woken by a stateless relay whose identifier is itself the device’s sealed token: nothing is stored, nothing can be read along the way. Sharing and notifications open existing web pages instead of duplicating the interface.

Forgetting really means forgetting

Everything the assistant keeps declares what it is: a conversation, a cache, something learned, something in progress. Every operation reads that declaration instead of guessing from a name. So clearing a conversation clears a conversation: what LIA learned about you stays, and anything whose nature is uncertain is kept and counted rather than deleted on a mere guess. The rule holds the other way too: only “Forget everything” and deleting the account remove what was learned.

Structured minutes

Thirty formats for meeting minutes ship with LIA, from a decision log to a one-page summary, and you can add your own. The right format is chosen from the most explicit signal available: what you asked for, then the meeting’s settings, then your preferences. Failing those, a model reads an excerpt, and it abstains rather than guessing when it is not sure enough. What decided the choice is noted on the meeting. A long transcript is rewritten section by section, so a two-hour meeting is never cut short to fit into a single answer.

Two ways to carry out a request

You choose the mode in the chat header, or let LIA choose it for each request. For a structured request, Pipeline mode prepares a plan, checks that it holds together, then runs the independent steps in parallel: it is fast, controlled and predictable. For an open question, ReAct mode explores, reads the results and adapts what comes next. To stay reliable, it checks that the results really answer the question, can switch source when it hits an obstacle, and says what it did not find, with what it tried. In both modes, confirmations depend on the planned actions. In ReAct, your exchange rhythm can favor the cache if you exchange often (the next turn reuses the beginning of the previous one, for an hour at most while you wait for the answer, with the providers that allow it), or tool selection if you exchange only now and then. The turn ends on the result and its limits, without announcing work that won’t be done.

Seven model providers, your choice

OpenAI, Anthropic, Google, DeepSeek, Qwen, Perplexity and any local model with Ollama. Each role (routing, planning, answering, vision, indexing) is configured separately, so a cheap model handles the mechanical steps and a powerful one writes the answer. What each model can really do is read from a catalogue kept up to date, rather than assumed, and the depth of reasoning requested is translated into each provider’s own language.

Plans that improve with use

LIA remembers which plan shapes worked for which kind of request and reuses them, with a Bayesian score that goes up with each success and decays over time: an old habit never outweighs a recent failure. The effect is practical rather than magical: fewer model calls, faster answers and steadier behavior on what you ask for often. Nothing is shared between accounts: this learning is yours, and it disappears with your data.

Hybrid search

In your knowledge spaces, relevance is decided on meaning rather than on words, with a single multilingual similarity threshold, recalibrated across the six languages. Exact matching keeps a useful role, putting a word-for-word occurrence first when two results are almost tied, but as a limited bonus, never as the judge: giving both signals equal weight would throw out one good answer in three whenever the question is not in the documents’ language. Scripts written without spaces are split into pairs of characters; otherwise a whole Chinese sentence would count as a single word.

Real-time streaming

The answer in progress streams the routing, the planning, the tools and the text as it runs. If the connection drops, generation carries on on the server, and what it produced is replayed to you as soon as you reconnect. Alongside that, every change saved in a conversation sends a signal with no content: the browser re-reads the authenticated history and adds the new rows, without replacing pages already loaded or moving where you are reading. On reconnection, missed signals are caught up. One answer runs per account at a time, held by a database row that no timeout releases, and a message written meanwhile waits its turn on the server.

Honest enrichments

A provider sometimes publishes a category without a number: the French air-quality index says “Moyen” with no value, while Google’s universal index runs the opposite way to the US scale (there, 100 means excellent). So the weather card and a place’s details share a single display, which follows two rules: the category shown is always the one the source publishes, never one deduced from a number, and a number is never shown with the label of another scale. Better an absent signal than a false one.

Exact where it must be

Calculations, dates and currencies are never left to a model’s intuition. A calculation is parsed, then evaluated in exact decimal, never executed as code, and LIA says when the result had to be rounded. A duration is counted between two absolute instants: a night with a clock change lasts 23 or 25 hours, as in real life. A time you say reaches your calendar with its zone, and each message carries the moment it was written: « tomorrow », said on a Tuesday, is still Wednesday on the Friday. A conversion uses the European Central Bank’s reference rate and gives its date. Every limit a tool enforces is written into the description the model reads: whatever is refused had been announced.

A decision with boundaries

An administrator can turn on each use of JEV separately, with optional, bounded diagnostics. The model helps choose, but permissions, compatibility rules and confirmations stay in the code. When in doubt, LIA falls back to deterministic protections, and paid attempts are counted, as are their fallbacks.

Modern stack

FastAPI, Next.js, React, TailwindCSS, PostgreSQL, Redis. Strict TypeScript on the frontend, asynchronous Python on the backend. An installable PWA: six translated manifests, sharing from the system into the chat, an offline page and smart file caching, with API responses never cached. Settings can be searched from the keyboard, in all six languages, ignoring capitals, accents and typographic apostrophes. The design system is a contract checked by tests: every color pair is checked across five themes, in light and dark, with one tone per status and one shape per level of action.

Skills with frames & images

A skill is a small program LIA can write for you, then run in a sandbox. It answers with text, an image or a mini-interface built into the conversation, isolated from the page and matched to your theme and language, and it can run its own commands in a throwaway copy of its folder to hand you files. Whether you upload it, the chat proposes it or you pick it from a public library, every skill follows the same path: strict validation, capped sizes, and an installation that either succeeds completely or leaves nothing behind. A skill written elsewhere is kept away from your connectors.

Human-in-the-Loop

Confirmations sit at the tool level, depending on the planned action. An ambiguity can be cleared up with a question, a draft touched up before approval, and several operations grouped for a single approval when their scope allows. What is proposed and what was done stay distinct, and both leave a trace.

LIA on the phone

LIA can call and be called: your speech is transcribed, the answer is put together, then the text becomes a voice again, in the same conversation as the chat. She has access to the same capabilities, your calendar, your contacts, your reminders, and an action that would need a confirmation is asked about out loud rather than carried out in silence. A call leaves the same trace in your registers as a written exchange: what is done by voice is no less accounted for than what is typed.

Two ways to reach the result

A direct path for structured requests, an adaptive exploration for open questions. You choose the mode in the chat.

Pipeline

Speed and control

The default mode organizes the work before carrying it out. A clear path, with coordinated steps.

  1. Plan

    Your request becomes a plan of steps and dependencies.

  2. Check the plan

    LIA checks the consistency of the planned steps and tools.

  3. Execute in the right order

    Independent steps run in parallel. The others wait for the results they need.

Useful, for example, for

Finding an invoice, drafting a reply and creating a reminder.

ReAct

Exploration and adaptation

When the next step depends on what is discovered, LIA chooses its next move from the results it receives.

  1. Explore

    LIA chooses an initial search or action based on your request.

  2. Observe

    It reads what comes back before deciding what to do next.

  3. Adapt the next step

    It adjusts its search and can revisit a missing point, within a bounded budget.

Useful, for example, for

Comparing solutions, cross-checking sources and resolving a discrepancy.

In both modes, reasons to trust the work

  • You decide before the action

    Actions that require your confirmation ask for it before they run.

  • The work stays traceable

    Consultations and actions have their own separate records.

  • The result matters

    The answer draws on what was obtained and states what still needs clarification.

  • 38+AI agents
  • 345Integrated tools
  • 7LLM providers
  • 99+Voice languages
  • 89,400+Automated tests
  • 392Architecture decisions
  • 298Versions shipped

Recently shipped

The product moves, and says so

Every release is told in plain words: what changes for you, not what changes in the code. Here are the latest ones, and the whole history is one click away.

  1. v5.1.0 — 🧭 The right mode, wherever you talk

    November 16, 2026

    • 🧭 Automatic mode — Choose Automatic in the chat header: LIA picks Pipeline or ReAct for each request, favouring the loop when the work needs exploration or an action. When LIA chooses an engine, its badge appears below the answer as soon as it finishes and stays in the history, including when Telegram is active. Tickets, routines and Telegram offer the same choice; the menu says when the instance cannot choose automatically.
    • 📎 Telegram reads more — Send photos, documents, albums or your location, and reply to a message to give LIA its context. Answers keep their headings, lists, tables and quotes; generated images and documents arrive as files. The chat's file limits still apply.
    • ⏯️ Telegram keeps your place — /stop stops an answer; a text sent while LIA works waits for its turn. If the answer fails or is stopped, you can send or withdraw the waiting text. With spoken replies enabled, a voice note also gets a voice reply. Routine results reach Telegram too.
    • 📲 Notifications through ntfy — Subscribe the ntfy app on your phone or computer to your instance's server, or another allowed server. A QR code and a test message help you connect. By default, only a notice leaves LIA; Full text is your choice for each subscription.
    • ⏰ A reminder can wait — When it rings, postpone that occurrence from its message or notification, or confirm that you want to stop the series. The offered times follow your timezone, and pressing twice from two devices does not create two postponed reminders.
    • 🖋️ Your words, your choice — Writing style is learned only when you ask, from Settings or a confirmed chat request. You can learn it again or forget it; it no longer renews itself. E-mails LIA writes use that style, while words you dictate explicitly stay as you gave them.
    • 💬 Results return to their discussion — Calls, meetings started or imported from a discussion, and routines run manually from its chat return there, or to Main if that discussion was reset or deleted. A notification for another discussion names it and offers to open it.
    • ✉️ Read the e-mail as it was sent — Open its original layout from the chat card, as in Tools, without a model call. Remote images wait for your click. When LIA summarises the mail or turns it into an event, it reads the words that layout actually shows.
    • 💓 Health figures follow your day — Overlapping iPhone and Apple Watch step samples are counted once per time slice, including history already received. Charts, averages and requested periods follow your account's timezone; a day without samples is not shown as zero.
    • 📅 Read across your lists — Availability, the home page and other calendar summaries read every calendar you own. Internal readers follow provider pages for calendars, task lists and mail history; a single tool request that reaches its limit says so.
    • 🧠 A longer conversation keeps its bearings — Compaction preserves recent words you wrote and important identifiers. If a model refuses a conversation that no longer fits, LIA compacts it and tries once more only when the turn has not already carried out an action.
    • 🧩 Restore through the chat — Attach a memory export and ask LIA to import it, or ask to restore a skill's previous version. LIA shows what will change and waits for confirmation, rechecking that the record has not changed meanwhile.
    • 📇 Calls and texts on a contact's card — Recent calls and incoming SMS appear even for a contact with only a phone number. After a call, LIA distinguishes voicemail, no answer and a failed line, and says whether a voicemail message was left when the provider recorded it.
    • 🔌 Stripe in Known MCPs — Add Stripe from the ready-made server gallery. OAuth discovery also reads the metadata published under a server's path, allowing connections that previously failed at sign-in.
    • 📱 Small-screen fixes — Dialogs and long file or discussion names stay within the screen. The home page's unread-mail label describes the count actually shown, and an answer's mode badge wraps as a whole on narrow phones.
    • 🌐 A clearer introduction — The public home page explains LIA's services, personal context and ways to act, with a more focused presentation and a sourced comparison that separates what is built in from what needs an extension.
    • ⚙️ For administrators — The installer offers an optional ntfy server, off by default; its iPhone wake relay is a separate choice. Automatic mode has its own JEV configuration and states its fallback. Reading compressed documents is bounded by their expanded size; knowledge spaces explain when that limit is exceeded. Administrator diagnostics retain the processing details through the end of the answer.
  2. v5.0.0 — 💬 A discussion for every subject

    November 14, 2026

    • 💬 Several discussions — The pill in the middle of the chat header opens your discussions: Main, always there, and the side discussions you create for a subject, each with its own history, draft and cost. Rename, export, reset or delete them; reminders and routines keep arriving in Main, and Search all discussions finds your words everywhere.
    • ⏳ Write while LIA answers — The field stays open: Send next keeps your message waiting, and it leaves by itself once the answer is done. Until then you can edit it, withdraw it or Send now. In ReAct mode, Add to the answer in progress lets LIA read it at its next step.
    • 📡 Routines that react — A routine can start When another system calls it (a home automation box, a code forge, a form), through its own address and a secret shown once, or when A web page changes: LIA reads the public page itself and runs the routine when new lines appear, a price for instance.
    • 🧩 Ready-made routines — The Template list fills the form: Morning briefing, Inbox triage, Weekly review, Overdue task. Only notify me when there is something new keeps the answer in the chat without disturbing you for nothing, and a routine now tells you when it failed, was skipped or missed its time.
    • ✉️ Mail that knows it was answered — Chat cards, the home and Tools › Mail mark a message Answered, Reply drafted, not sent or Reply received, read from your mailbox. LIA stops offering to answer what you already answered, and notifications leave it out.
    • 🖋️ E-mails in your voice — The first time LIA writes an e-mail for you, it learns how you write (greeting, sign-off, signature, tone) from your latest sent e-mails, never what you wrote about. See it, switch it off or choose Forget in Settings › Writing style.
    • 📊 Richer documents — Spreadsheets with real formulas, totals, drop-down lists and charts; presentations with key figures, quotes, pictograms and editable charts; reports with a cover page and cited sources. Settings › Documents decides illustrations (each one is an image generation, counted in your costs) and the animations of a presentation.
    • 🌐 Web search without a key — Where your instance runs its own search, LIA finds web links for you even with no search key: in the chat, in your interests and in the Tools. Your own Brave key keeps priority.
    • 🧰 Known MCP servers — Known MCPs opens a gallery of servers ready to add (Notion, GitHub, Linear, Todoist, Canva…): pick one, the form opens already filled, and one you already have is marked Installed. You can also ask in the chat: « Add the Notion MCP server ».
    • 🗂️ Categories on the workboard — The Categories button sorts your tickets into lanes, plus To categorize; deleting a category deletes no ticket. The Workboard is now in the menu, with The board at a glance at its top.
    • ✅ All your tasks, all your files — The Tools open on All tasks, and LIA reads every list, naming the list of each task. In the chat you can now attach Word, Excel, PowerPoint, OpenDocument, EPUB, CSV, Markdown and other documents, no longer images and PDFs only.
    • 🧠 Skills and memories — Each skill says how often you use it; those left unused are proposed with Switch them off or Keep them, and a replaced skill keeps one previous version to restore. Import brings an export of your memories back in.
    • 🌦️ A livelier companion — It acknowledges your message, presents the answer, looks at what matters on the screen, moves its mouth on the voice you actually hear and plays the weather where you are. The theme button also reaches Automatic, and an interactive page can draw a map.
    • 🔧 Fixed — An event moved in Tools › Calendar no longer lands an hour late. A task asked in a given list no longer goes to the default one, a mail you opened is no longer announced as unread, a failed web source is said instead of « nothing found », a list opened in a dialog no longer freezes the page, and the theme button no longer flickers between two open tabs.
    • ⚙️ For administrators — The installer proposes the instance’s own web search (SearXNG) and now asks for an Anthropic and a DeepSeek key. A switch governs Routines started by a call, each account has a Writing style switch, and a capability you switch off disappears from every menu.
  3. v4.6.0 — 🧭 Everywhere, your way

    November 10, 2026

    • ✍️ Text menus everywhere — Select words anywhere in LIA, the chat included: Read, Question, Explain, Summarize, Simplify, Translate, Internet, or make a task, an event, a reminder, a ticket or a memory of them through the form you know, saved by your own click. While you write, a selection is corrected, formatted, shortened, made more formal or warmer.
    • 💡 Proposals from your use — What you ask for on many days, whatever the hour, becomes a proposal in Alerts › Proposals: a routine ready before you ask, a routine moved, your notification hours widened, a source to connect. Accept does it at once, Later brings it back in two weeks, Never closes it.
    • 🎭 Your personality in the voice — In Live, in Live direct, on a call with you and in the spoken comments, the voice speaks in the personality chosen in LIA Style, facts unchanged. A call to someone else stays cordial.
    • 🧭 From a card to its tool — An e-mail, an event, a contact, a task, a file or a light shown in the chat opens in the Tools. On the home, a click opens the item in its tool, and More actions starts with the direct ones: mark as read, archive, done, postpone.
    • 🎨 Your style — Choose your icons in Settings › Appearance: Lucide, Fluent Color or Streamline Flex. Automatic switches between light and absolute black at the hours you choose.
    • ✉️ Cards shaped like their content — An envelope for a mail, an invitation for an event, a folder for files, the sources in the margin of a research, all in your palette. A location opens an interactive map once its cost is shown, and air quality and pollen join the weather.
    • 🔎 Find and sort — Knowledge spaces are searched by their name or a file’s, sorted, and keep their favourites apart, right after Meetings in the menu. The activity timeline and every section of Alerts search, filter and sort, received SMS included. A meeting is deleted from its row.
    • 👤 Contacts and connections — Write a contact with LIA, ask LIA to Call one of their numbers, and find the calls and texts in Latest exchanges. A message to a connection asked in words now leaves without a confirmation card.
    • 🦾 Companions that move — Arms, wrists, legs and feet follow listening, thought and speech wherever a companion has them, and winter scarves fit every silhouette. Smiley leaves the catalogue: a saved choice moves to the default companion.
    • 🔧 Fixed — A Microsoft To Do task due today no longer shows as late east of Greenwich. A call to someone else no longer takes your personality, an answering machine hears your portal’s message rather than one LIA composed, and visiting a public page no longer changes your language.
    • ⚙️ For administrators — Each JEV decision threshold can be set within its bounds, with thirty days of counted judgements beside it, and mails can show Reply expected. A knowledge space can hold up to 10,000 documents.

Inside LIA: Technical Insights

Explore the architecture, integrations, and engineering behind LIA through our technical articles.

Start with what would truly help you.

A project to prepare, a day to organize, an assistant to host: explore LIA and choose the workflow that suits you.

Or install my own LIA

Sign-up by email: you confirm your address, then the administrator activates your account (automatically on a demo instance). Optional services depend on your configuration.

Or read our philosophy first →