@fmerian Quick question: in multi-cloud setups like AWS + GCP, how does AutoTriage prioritize runtime threats across environments without missing blast radius?
Report
Awesome product, @flxg! I spent 5 minutes on the page.
The "Secure everything you build, host, and run" line is a bold promise.
The hero section caught my eye for one reason. You claim to fix vulnerabilities automatically with AI AutoFix. Then below, under the Unified Platform section, you list 16 categories of tools you replace. That's a lot to digest.
Here's the tension.
A developer landing on your page reads one central system. But... the page immediately shows a long list of 16 things you replace. That creates cognitive load. Got it?
And a user might think this is a platform and then be handed a shopping list of features.
The middle section has a strong stat: "Cut false positives by 85%." But it's buried under a HOW IT WORKS block.
That's your strongest differentiator. A security lead needs to see that number before they see how you do it.
I attached a screenshot to show what I mean.
Spotted 3 other things that need to be tightened. Happy to share.
Report
Security built into Lovable is a great move. How deep does it scan?
Report
Interesting — do you test and improve only the code, or the server environment as well? Very often, breaches don’t happen through the code itself.
Replies
The State of Vibe Coding 2025 report highlighted a security challenge. @Lovable is addressing it with @Aikido Security. Promising.
@fmerian Quick question: in multi-cloud setups like AWS + GCP, how does AutoTriage prioritize runtime threats across environments without missing blast radius?
Awesome product, @flxg! I spent 5 minutes on the page.
The "Secure everything you build, host, and run" line is a bold promise.
The hero section caught my eye for one reason. You claim to fix vulnerabilities automatically with AI AutoFix. Then below, under the Unified Platform section, you list 16 categories of tools you replace. That's a lot to digest.
Here's the tension.
A developer landing on your page reads one central system. But... the page immediately shows a long list of 16 things you replace. That creates cognitive load. Got it?
And a user might think this is a platform and then be handed a shopping list of features.
The middle section has a strong stat: "Cut false positives by 85%." But it's buried under a HOW IT WORKS block.
That's your strongest differentiator. A security lead needs to see that number before they see how you do it.
I attached a screenshot to show what I mean.
Spotted 3 other things that need to be tightened. Happy to share.
Security built into Lovable is a great move. How deep does it scan?
Interesting — do you test and improve only the code, or the server environment as well? Very often, breaches don’t happen through the code itself.