In short
- Burp Suite comes in a free Community Edition and a Professional edition listed at $499. PortSwigger also sells Burp Suite DAST for scanning at scale and Burp AT, an AI agent for pentesters.
- Burp does not find flaws alone. It gives a skilled person the means to find them. The result depends on the operator and the hours spent.
- ZAP is the free, open source alternative. Caido is a newer toolkit with a free Basic plan. Both are for people who test by hand.
- The flaws that matter most in AI-built apps are about access: a stranger reading a table, user B reading user A's record. You can test both with a browser's developer tools and two accounts.
- If you do not want to become the operator, choose an automated test that proves each finding with the request that worked, and check its limits.
On this page
- What Burp Suite is, and what it costs
- Why Burp Suite needs a skilled operator
- Alternatives if you test by hand: ZAP and Caido
- Alternatives if you do not test by hand
- What a tester would check first, without Burp
- When Burp Suite is still the right tool
- Where Keybrum fits, and what it does not do
- Questions
- Sources
What Burp Suite is, and what it costs
Burp Suite, made by PortSwigger, is the standard toolkit of web penetration testers. PortSwigger presents the Professional edition as the leading web penetration testing toolkit in the world. At its core is an intercepting proxy: your browser's traffic passes through Burp, where you can read each request, edit it, and send it again. Around the proxy sit tools to repeat requests with variations, compare responses and, in the paid edition, scan for known flaw patterns.
| Edition | Price on portswigger.net | What it is |
|---|---|---|
| Burp Suite Community Edition | Free, no licence needed | The proxy with history, Repeater, Decoder, Sequencer and Comparer, and a demo version of Intruder. PortSwigger describes it as the essential manual toolkit for learning |
| Burp Suite Professional | $499. Everyone who uses it needs their own subscription | The full manual toolkit with Burp Scanner built in, the full Intruder, and project files to save your work |
| Burp Suite DAST | On request, tailored to your needs | The same scanning engine run on a schedule or in a pipeline across many applications, for security teams |
| Burp AT | $19, $89 or $249 per user a month for individuals, on top of Professional | An AI agent that works inside Burp for pentesters. In public beta |
Nothing here is a criticism of Burp. It is a reference among professional testers, the Community Edition is a generous way to learn, and PortSwigger's Web Security Academy is free. The question for a founder is different: is a tester's toolkit what you need?
Why Burp Suite needs a skilled operator
Burp is closer to a workshop than to a machine. PortSwigger's own description of the Professional edition is a toolkit "for pentesters and bug bounty hunters". Three things stand between installing it and getting an answer about your app:
- You must know what to try. The proxy shows you a request that fetches invoice 871. Burp does not tell you to try 872 with another account. That idea comes from the tester.
- You must read the result. A response with status 200 can be a leak or an empty page. Telling them apart means understanding your app's data and what each account should see.
- The scanner covers patterns, not ownership. The built-in scanner in the Professional edition looks for known flaw classes such as injection and cross-site scripting. Whether user B may read user A's record depends on your data model, which no general scanner knows.
A professional needs days on a small app to cover it well, which is why a manual pentest is priced by the day. The pentest cost guide gives the ranges. A founder who opens Burp for an evening will learn a lot about HTTP and little about their app's real exposure.
Alternatives if you test by hand: ZAP and Caido
If you do want to do the testing yourself, or you are hiring someone who will, two products compete with Burp directly.
| Tool | What its own site says | Price | Good to know |
|---|---|---|---|
| ZAP (Zed Attack Proxy) | "A free, open-source penetration testing tool", now presented as ZAP by Checkmarx. It works as a proxy between your browser and the app, with passive and active scanning | Free | Has a quick start mode that crawls and scans an address. Its documentation says the crawler cannot fill forms as a person would, so manual browsing reaches more of the app |
| Caido | "The web hacking toolkit designed to scale manual testing through AI and teamwork", for bug bounty hunters, pentesters and security engineers | A Basic plan that is free forever, limited to 2 projects. Paid Individual and Team plans | Caido states that it is not open source |
| Burp Suite Community Edition | The essential manual toolkit | Free | No scanner and no saved project files, which the Professional edition adds |
All three ask the same of you as Burp does: knowing what to look for. ZAP's automated scan is the closest thing to a button, and it is a reasonable first look. Its results are alerts to review, with false positives, and they say nothing about access between two accounts unless you set that up yourself. The guide on website vulnerability scanners explains how to read such results.
Alternatives if you do not test by hand
Most founders who search for a Burp alternative do not want a different proxy. They want the result a tester would give them. The options, from lightest to heaviest:
| Option | What you get | Where it stops |
|---|---|---|
| A vulnerability scanner | A list of known patterns found on your pages: missing headers, old versions, some injection classes | Alerts to interpret. Little about who can read whose data. See pentest vs vulnerability scan |
| A proof-based automated pentest | Attacks run for you on the live app, as a stranger and as two accounts. Each finding is the request that worked | Only the flaw classes it has attacks for. See automated pentests |
| An AI pentest | AI agents explore your app and report what they could exploit, often with a formal report | Price, and the limits you must set on a live app. See the list of AI pentest tools |
| A manual pentest | A person with Burp, your roles and your business rules in mind | A snapshot, priced by the day. See pentests for startups |
The right choice depends on who is asking. If a customer or an auditor wants a pentest report, they usually mean the last line. If you want to know before launch whether your users' data is open, the second line answers in minutes.
What a tester would check first, without Burp
The first hour of a professional test on an AI-built app looks the same almost every time. You can do it with the developer tools already in your browser. Use your own app and two test accounts you created.
- 1
Watch what your app calls
Open your app, press F12 and select the Network tab. Use the app as a normal user. Each line is a request: note the ones that go to your API, or to an address ending in
supabase.coorgoogleapis.com. That list is what a stranger can call. - 2
Replay a request without your session
Right-click a request that returned private data and choose Copy as cURL. Paste it in a terminal, remove the
Authorizationheader and theCookieheader, and run it. A private route should answer 401. If the data still comes back, the route is public. - 3
Replay it as the second account
Sign in as your second account in a private window. Take the id of a record the first account created, and request it from the second account, by its address in the app or with the copied cURL and the second account's headers. You should get a 403 or a 404. The record itself is an IDOR.
- 4
Read what the page ships
In the developer tools, search across the loaded files for
service_role,sk_liveandsk-. A match is a secret key in public: rotate it, then move the call to your server. See API keys exposed in the frontend. - 5
Check the headers
Look at the response headers of your main page for
Content-Security-PolicyandStrict-Transport-Security. Missing headers are rarely a leak alone, and they are quick to add. The security headers guide has the values.
For a Supabase app, the fix for step 2 or 3 is nearly always row level security with a policy that names the owner:
alter table public.your_table enable row level security;
create policy "Owners read their rows"
on public.your_table for select
to authenticated
using ( (select auth.uid()) = user_id );For an API route of your own, the fix is two checks inside the handler: is there a session, and does this record belong to that session's user. The Supabase RLS guide and the API penetration testing guide show both.
When Burp Suite is still the right tool
- You want to learn web security. The Community Edition and PortSwigger's free Web Security Academy are a solid start. Nothing teaches you your own app like watching its requests.
- You hired a pentester. They will very likely use Burp Suite Professional, and that is a good sign. You do not need your own licence.
- Your app has unusual logic. Credits, payouts, approval chains: flaws in those are found by a person who understands the rule and tries to bend it. No automated tool, ours included, replaces that.
Where Keybrum fits, and what it does not do
Keybrum is the automated pentest we build for apps made with Lovable, Bolt, v0, Replit, Cursor, Claude Code and Base44. It does the first hours of a tester's work with no operator. It reads the routes and tables named in your JavaScript, then attacks. On Supabase it reads tables with the public key, tries inserts and updates on other people's rows, calls database functions and lists storage buckets, as a stranger and as two accounts. On Firebase it tests Firestore, Realtime Database and Storage rules. On your own backend it calls API routes as a stranger and as two accounts it creates. It confirms leaked keys with read-only calls, and checks for exposed .env files, AI endpoints anyone can spend, unsigned Stripe webhooks, security headers, and known Next.js and React flaws proven by behaviour.
Every finding is the request and the response, with personal data redacted, so you see what a tester would show you in Burp without running Burp. Your coding agent reads the fix through Keybrum's MCP server, and the same attack runs again until it fails.
It is not a proxy and not a replacement for a person. You cannot craft your own requests in it. It finds only the flaw classes in its library, so business rules specific to your product are out of its reach. It never tests delete access, and it only attacks an app whose owner proved ownership. A one-time report on one app is €49. Plans start at €29 a month excluding VAT for 5 apps and attack every deploy.
Questions
What is the best free alternative to Burp Suite?
ZAP is the usual answer: it is free, open source and does the same core job as an intercepting proxy with a scanner. Burp Suite's own Community Edition is also free, without the scanner. Caido has a free Basic plan limited to 2 projects.
How much does Burp Suite cost?
On 13 November 2026, PortSwigger listed Burp Suite Professional at $499, with a subscription needed for each person who uses it. The Community Edition is free. Burp Suite DAST is priced on request. Burp AT, the AI agent, costs $19 to $249 per user a month for individuals, on top of Professional.
Is Burp Suite hard to learn?
The interface takes an afternoon. Knowing what to test takes much longer, because Burp shows you requests and leaves the ideas to you. PortSwigger's Web Security Academy is free and is a good place to start.
ZAP vs Burp Suite: which should I use?
For learning and for a tight budget, ZAP costs nothing and has an automated scan mode. Burp Suite Professional adds its scanner, saved projects and an extension store, which is why people who test for a living tend to pay for it. For a founder, the choice matters less than the question of who will do the testing.
Can I use Burp Suite to test my Lovable or Bolt app?
Yes, on your own app. Proxy your browser through it and you will see the calls to Supabase and to your functions. The checks that matter are the ones in the steps above: no session, then a second account. The Lovable security guide lists what these apps expose.
Do I need Burp Suite if I use an automated pentest?
Not to get a first answer. An automated test covers the common flaw classes without an operator. Burp becomes useful when you or a tester want to dig into logic specific to your product, which automated tools do not model.
Sources
- 1.Burp Suite: products and editions, PortSwigger
- 2.Burp Suite Professional, PortSwigger
- 3.Burp Suite Community Edition, PortSwigger
- 4.Burp Suite DAST pricing, PortSwigger
- 5.Burp AT pricing, PortSwigger
- 6.Web Security Academy, PortSwigger
- 7.Getting started, ZAP
- 8.Caido home page, Caido
- 9.Pricing, Caido
- 10.Row Level Security, Supabase Docs