About Lanthorn
Built by people
who read the fine print.
Lanthorn began in a small Lisbon office as a simple idea: an assistant that answers like a careful colleague and always shows where the answer came from. Today we are 32 people in five cities.
32
people on the team
5
cities, one shared desk
2024
first prototype
1,400
teams ask Lanthorn daily
Four habits
we will not trade away.
01
Show the source
Every answer ends with the passages it used. If we cannot point to it, we do not say it.
02
Ask before acting
Lanthorn drafts, suggests and waits. Nothing is sent, changed or deleted without a person saying yes.
03
Read only what you may
Answers respect the permissions you already have. A private channel stays private, even to us.
04
Stay quiet by default
No pings, no streaks, no growth tricks. The best assistant is the one you forget until you need it.
From a side project
to a daily habit.
2024
First prototype
Two engineers, one shared drive and a question: can an assistant cite its sources?
Late 2024
The first 50 teams
Design partners in Lisbon and London use it every day and tell us what breaks.
2025
Sources in every answer
Citations become the product. Permissions follow each source, line by line.
2026
1,400 teams
Integrations with the tools teams already use, and a home in five cities.
Next
Answers you can act on
Drafts that wait for your yes, and an assistant that knows when to stay quiet.
The people
behind the answers.
Inês Moreira
Co-founder, CEO · Lisbon
Tomás Ferreira
Co-founder, CTO · Lisbon
Clara Vidal
Head of research · London
Daniel Novak
Applied AI · Toronto
Hanna Lindqvist
Design lead · Stockholm
Ravi Menon
Customer success · London
Sofia Brandt
Platform engineer · Berlin
Kai Tanaka
Security · Berlin
Where we work
when we are not remote.
Lisbon studio
Our first office, above a print shop. Big windows, late lights.
The quiet room
No calls, no screens on the wall. Where the hard reviews happen.
Thursday reviews
Once a week, everyone reads the answers Lanthorn got wrong.
Open roles
Four seats at the table.
Not the right role?
Write to us anyway. Tell us what you would build, and which answer you would never want an assistant to get wrong.