You can now chat with Lovable in @telegram.
Message Lovable like you would a teammate. Kick off multiple tasks across any project, ask for insights, or start a new build. It’s your co-founder on the go.
We're in Stockholm. You know how there are some places where you think "Nice place to visit, but I wouldn't want to live there"? Stockholm is the kind of place that makes you want to live there.
Shoutout to our community champions in the chat who help builders round-the-clock!
We're working with Discord to get everyone back in (and hopefully preserve our streak).
This week we opened Lovable's new Stockholm HQ.
Since the beginning, we've built Lovable on the thesis that in-person is a competitive advantage. A decision that takes hours on Slack takes five minutes at a desk. You overhear the right thing at lunch and course-correct before it becomes a problem.
In person also brings us closer to our colleagues, it injects energy, and it makes our work more human.
The opportunity is here to catch, to build a generational company out of Europe, and do the work of our lives together.
We found a bug in Google's Kubernetes networking layer that was causing sporadic errors for our users.
I wrote a blog about how we tracked it down across two layers of infrastructure failures: lovable.dev/blog/hunting-n…
Last week we hosted our second @Lovable design night in Stockholm.
>100 of Stockholm's finest, with people travelling from as far as South Africa to join!
Thanks @doctorbaytas for ranting about dark mode, @marinaanddesign for showing beautiful work, @six7 for explaining sources of truth, and @DanHollick for showing off fun tools.
Want to speak at our next one? DMs are open.
We have been testing GPT-5.5 in early access.
Our evals show it’s the most capable model for people taking on complex builds with technical depth.
• 23.1% fewer tool calls per request
• 10% better at breaking through roadblocks
• 12.5% higher scores on our hardest benchmarks at the same cost
In november I hosted a Founder dinner and there was a literal Llamacorn.
I just landed in Oslo, and we’re running it back. 10 sundays, 10 founders, 1 dinner, 1 (or more) mythical animals.
I’m also using this post to leverage @sophianabilg into saying yes to having a llama at next weeks @Lovable event in Oslo we’re hosting together.
Comment “Llamacorn” and Sophia will send you a invitation for next week if theres space. 🎸🦄
Lovable had an incident this week, and I’m proud of our team for deploying a fix within hours of learning about it. But things shouldn’t have gone this way in the first place, and I take accountability. I’m sorry.
The team learned about the incident on X because our own vulnerability disclosure process was broken. That’s not because of our partners at HackerOne. It’s on us. We could’ve reacted much sooner and I never want people to think that the only time we care about an issue is if it goes viral. We care that everyone who uses Lovable can trust it, and trust us, to do right by them. We appreciate and need ethical hackers to help us make the product safer, and security researchers should know we value them.
We also made decisions in our product that might’ve felt logical when we launched but feel really out of touch with user expectations now. It doesn’t matter what the intent was, it matters that we make decisions that keep customer trust at the forefront at all times. We’ve done a lot of work on this in the last year, and when things like this incident happen, it shows me there is more to do.
So we’re going to do more and we’re going to communicate about it better.
Lovable should be the safest place to build.
Full write-up from the team and me below, including everything we're changing immediately.