Perplexity
A phenomenal research tool. A dangerous place to build a commercial product.
What This Is
Perplexity is an AI answer engine. Ask in plain English, get a cited synthesis drawn from live sources across the web. Not a list of links — an actual response that quotes, attributes, and reasons through the material. In under four years it became one of the most-used research tools online — north of 100 million monthly users across its products at last count.
In 2025 they launched Perplexity Labs, which extends the product into territory that overlaps with vibe coding: generating working code, building visualizations, creating dashboards, producing small applications inside Perplexity. Since then they've shipped Comet, an agentic browser that's now free on every platform, and a $200/month Max tier with background assistants that run tasks while you sleep. To anyone watching this space, the ambition is not subtle: Perplexity wants into the builder game.
This chapter exists because founders, developers, and creators keep asking whether Perplexity belongs in their stack. The honest answer is uncomfortable: Perplexity is among the best research tools in this guide, and one of the worst places to build anything you intend to ship commercially.
That's not a contradiction. It's a product positioning choice baked directly into Perplexity's Terms of Service. And it matters enormously depending on what you're trying to do.
Who Should Use This
Researchers, students, the intellectually curious. One of the finest research assistants ever built. Use it to learn topics, explore landscapes, understand trade-offs, find primary sources. This is what it's designed for and licensed for.
Developers exploring options before they build. Understand a new framework before committing. Compare two libraries. Decode an unfamiliar error. You're not building with Perplexity here — you're informing yourself before building elsewhere. That distinction matters legally and practically.
Anyone producing non-commercial content. Personal blog posts, hobby projects, learning journals. The terms restrict commercial exploitation, not all use.
Who it is emphatically NOT for: anyone building software they intend to sell, distribute commercially, or use in a paid service. If that's you, this chapter is a warning, not a recommendation.
The License Problem (The Heart Of This Chapter)
The restriction that disqualifies Perplexity for commercial building is stated plainly. Section 5.2 of their Terms of Service prohibits users from "exploit[ing] the Services for any commercial purpose." And in case anyone hoped that was an oversight, the January 2026 ToS update doubled down: personal, non-commercial use only — paid Pro subscribers included — plus a blanket ban on automation and scraping.
What "exploit for any commercial purpose" actually means is broader than most users assume. It is not limited to reselling Perplexity itself. It covers any use where Perplexity's output is incorporated into, or facilitates, a commercial product:
- Founder uses Perplexity to generate code for a SaaS feature → exploiting for commercial purpose.
- Developer uses Perplexity research to write a paid tutorial → exploiting for commercial purpose.
- Builder embeds a Perplexity Labs chart in a client dashboard → exploiting for commercial purpose.
The "download it and leave" workaround does not work. Section 5.2 also prohibits downloading, modifying, copying, distributing, or creating derivative works from any information obtained from or through the Services. The output you generate in a Perplexity session is information obtained through the service. Copying it into a separate codebase reproduces that information. Selling the resulting product is offering for sale information obtained through the Services. The clause is drafted to foreclose exactly the workaround most users reach for.
Output ownership gap. OpenAI's terms explicitly assign all output rights to the user. Anthropic's do too. Perplexity's consumer ToS contains no such clause. Third-party legal analysis has flagged this silence as a meaningful gap. Users relying on Perplexity output for anything consequential are leaning on general legal principles rather than contractual rights — a weaker position than what every competitor offers.
Taken together: Perplexity is licensed as a personal and research tool. Its terms aren't accidentally restrictive — they're deliberately positioned to prevent the kind of commercial building that has exploded around vibe coding. If you're shipping a product, Perplexity isn't the right tool. Not because it can't do the work, but because you're not licensed to use the output for that purpose.
What Perplexity Labs Can Do (And Why It's Tempting)
Worth acknowledging directly: Labs is impressive. Working HTML/CSS/JS prototypes. Interactive data visualizations. Small dashboards with real, live data. Research-grounded content artifacts.
For non-commercial exploration this is wonderful. Sketch an idea for a personal project. Visualize data for an internal report. Prototype a concept before committing a weekend. The research-grounded nature of the output produces artifacts more interesting than what a pure code generator would produce.
The problem hits the moment you decide to turn that prototype into something real. The prototype itself is information obtained through the service, covered by the restrictions above. You can't take it and rebuild commercially. Excellent for personal use. Ambiguous for anything else. Explicitly prohibited for commercial exploitation.
What To Use Instead (The Safe Commercial Path)
If your reason to consider Perplexity is commercial building, every other tool in this guide is a better fit. Cursor, Claude Code, Lovable, Bolt, Replit, v0, Windsurf, Base44, GitHub Copilot — all grant clear commercial usage rights on the code you generate. They've largely converged on commercial-friendly licensing because that's what the builder market requires. Perplexity made a different choice. Respect that choice by using their product for what it's licensed to do.
The safe research-to-build pattern:
- Use Perplexity (or any research tool) to learn what you need to know.
- Follow the citations to primary sources.
- Internalize the information.
- Build the product in a commercially-licensed tool, grounded in those primary sources you traced.
Don't paste Perplexity output into your build. That's the line.
For a research tool that does permit commercial use of output: Claude and ChatGPT both grant commercial rights in their consumer terms. For most workflows, either will serve as well as Perplexity with full commercial clearance.
Cost
Free. Genuinely usable for individual research. The Comet browser is free too, on every platform.
Pro $20/mo ($200/yr). More powerful models, more queries, access to Labs.
Max $200/mo ($2,000/yr). Unlimited Labs, background assistants running while you sleep.
Enterprise Pro $40/user/mo. Separate API products with their own terms.
The honest note: pricing isn't the determining factor for whether Perplexity belongs in your stack. Licensing is. A $20/month tool you can't use commercially isn't a better deal than a $20/month tool you can.
What It's Good At
Research: Five stars. Citation discipline, follow-up questions in-thread, synthesis quality on complex topics. Often better than general-purpose chat for source-grounded answering.
Learning: Five stars. Citations build a better mental model than ungrounded AI. Accelerates comprehension without fabricating false confidence.
Building commercial products: One star. Not a capability rating — a licensing rating. Do not use, regardless of what the product can technically produce.
The Story
A founder I know spent her first month researching a B2B analytics tool for small marketing agencies. Competitor positioning, SaaS pricing patterns in adjacent categories, architectural approaches other analytics tools use. Perplexity was perfect for that month. She came out with a clear thesis, a shortlist of technical approaches, and a set of primary sources she trusted.
Then she started building — in Cursor. Not Perplexity.
She didn't paste Perplexity output into Cursor. She didn't ask Perplexity to generate code she'd then edit. She used her own understanding — developed through Perplexity research but not dependent on Perplexity output — to prompt Cursor, which has commercial-friendly licensing on everything it produces.
Research phase: Perplexity-accelerated. Build phase: Cursor-executed. Commercial product: clean.
Six months later, when she sat down with investors and a diligence questionnaire asked what tools she used: straightforward answer. Nothing in her shipping product was licensed under terms that restrict her ability to sell it.
That matters more than most founders realize until they're mid-diligence reading fine print on tools they used in month one.
Where It Bites
Commercial-use restriction. The headline. Read Section 5.2 of the ToS before you make any decision about using Perplexity in a revenue-adjacent workflow. "Everyone else uses AI to build" is not a legal defense.
Output ownership gap. Even setting aside the commercial restriction, Perplexity doesn't explicitly assign output rights where competitors do. Weaker legal position. Matters most at moments of scrutiny: diligence, contract review, IP audits.
The "everyone else is doing it" trap. Many founders use Perplexity to build things they later try to sell. That doesn't make the practice legal. It means many founders are sitting on a risk they haven't internalized.
Gavin's Rule: Read Section 5 Before You Commit
Every AI tool has a usage-restrictions clause. Most are friendly to commercial building. Some are not.
The five minutes it takes to read those clauses before you commit saves weeks of rework if you later discover you built on output you weren't licensed to use commercially.
For Perplexity, the clause is 5.2 — prohibits commercial exploitation of the Services and information obtained through them. For Claude, OpenAI, and most commercial IDEs, the equivalent clause grants commercial rights.
The difference matters enormously and is always spelled out in plain language. Read them.
Bottom Line
Perplexity is one of the best research tools in existence. And one of the worst tools to build a commercial product on.
Its Terms of Service explicitly prohibit commercial exploitation of the Services and of any information obtained through them. Unlike every other tool in this guide, it does not explicitly assign output ownership to the user.
Use it for research, learning, personal projects — it will serve you brilliantly. Use a different tool when it's time to build something you intend to sell.
The restriction isn't a detail you can work around by copying output into a different editor. It's written into the license in a way that anticipates and forecloses exactly that workaround.
Respect the terms. Use the right tool for each job. Keep your commercial product on licensing you can defend.
— Gavin