Aikido penetration testing

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Aikido penetration testing working in a real project rather than a sandbox.

   Set up Aikido penetration testing in this project — enhance your security with AI-powered penetration testing. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Run dynamic penetration tests before a compliance review

   The record lists this as one of the jobs Aikido penetration testing is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Aikido penetration testing for run dynamic penetration tests before a compliance review. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Aikido penetration testing is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Aikido penetration testing before I publish. Check AI-powered testing and identify vulnerabilities, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Surface exploitable vulnerabilities directly in the project view

   A second job the record lists for Aikido penetration testing, useful once the first path works.

   Extend this project so Aikido penetration testing also covers surface exploitable vulnerabilities directly in the project view. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Aikido penetration testing?

  Aikido penetration testing is Lovable's Security feature: Enhance your security with AI-powered penetration testing. Aikido empowers workspaces to conduct dynamic penetration testing to identify vulnerabilities, sync findings to security views, and generate reports for compliance and reviews, enhancing project security.

• Is Aikido penetration testing GA or in beta?

  Aikido penetration testing is generally available (GA) on Lovable.

• What Lovable plan includes Aikido penetration testing?

  Aikido penetration testing is available on all Lovable plans.

• When did Aikido penetration testing launch?

  Aikido penetration testing launched on Apr 2, 2026.

• Security center updatesSame category, also GA · Apr 2026
• Audit LogsSame category, also GA · Mar 2026
• Workspace Authentication PolicySame category, also GA · Apr 2026