AWS Marketplace Scraper – Competitor Pricing Monitor
Pricing
from $25.00 / 1,000 aws marketplace listing intelligences
AWS Marketplace Scraper – Competitor Pricing Monitor
Scrape and monitor public AWS Marketplace listings. Track competitor pricing, contract terms, positioning, categories, delivery model, and listing changes with clear before-and-after evidence for product marketing, marketplace, and procurement teams.
Pricing
from $25.00 / 1,000 aws marketplace listing intelligences
Rating
0.0
(0)
Developer
Marielise
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
AWS Marketplace Intelligence — Pricing & Listing Change Monitor
AWS Marketplace is where cloud-software vendors compete on far more than a logo and a star rating. A public listing can reveal a new annual contract dimension, a switch from usage-based to private-offer positioning, an expanded category footprint, or a rewritten message aimed at a new buyer. Checking those pages manually is slow, easy to miss, and impossible to scale across a meaningful competitor watchlist.
AWS Marketplace Intelligence turns public AWS Marketplace product pages into a structured, repeatable competitive-intelligence dataset. Paste direct AWS Marketplace product URLs—or add labelled targets such as “Q4 AI-security competitor”—and receive the fields a marketplace, product-marketing, partnerships, or procurement team actually needs: seller, product type, categories, rating and review count, public overview and highlights, pricing model, private-offer and trial signals, visible pricing dimensions, support contact, and a source-linked change record.
This is not a generic website scraper. It understands public AWS Marketplace product pages and keeps a snapshot for every stable prodview listing ID. Re-run the same watchlist on a schedule to see whether a competitor changed pricing, packaging, positioning, categories, reviews, or support details. Set Return only changed listings to create a compact alert-ready feed instead of exporting the same rows every week.
Who uses it
- AWS Marketplace sellers and channel teams monitoring competitor packaging, price visibility, trial cues, and category moves.
- Cloud software product marketers building reliable battlecards from source-linked public evidence.
- Competitive-intelligence agencies delivering repeatable marketplace reports without copying page text by hand.
- Cloud procurement and FinOps teams comparing public software purchasing models before engaging vendors.
Quick start
- Open the product page in AWS Marketplace.
- Copy its URL, for example
https://aws.amazon.com/marketplace/pp/prodview-xphnsjsox7vjw. - Add one or more URLs to AWS Marketplace product URLs.
- Run the Actor and export the Dataset as JSON, CSV, or Excel.
{"productUrls": ["https://aws.amazon.com/marketplace/pp/prodview-xphnsjsox7vjw"],"includeDescription": true,"onlyChanged": false,"snapshotKey": "security-competitors"}
For a recurring watchlist, keep snapshotKey unchanged and schedule the same input weekly. After the initial baseline run, set onlyChanged to true. Changed records include changedFields, previousSourceHash, and changedAt; unchanged listings are skipped from the Dataset while errors are always reported.
Customer-ready watchlist
Use Named watchlist targets when the output is going to a buyer, consulting client, or internal battlecard. It keeps their relationship and reporting tags alongside each live listing:
{"targets": [{"url": "https://aws.amazon.com/marketplace/pp/prodview-xphnsjsox7vjw","label": "AI-security competitor","relationship": "competitor","tags": ["AI security", "Q4 watchlist"]}],"snapshotKey": "ai-security-competitors"}
Each output then includes a customer-friendly changeSummary and customerTakeaway, not merely raw page data.
What each listing includes
| Field | Meaning |
|---|---|
productName, sellerName, sellerProfileUrl, listingId, productUrl | Stable listing identity and source links |
deliveryMethod, isDeployedOnAws | Public delivery/deployment signals when AWS exposes them |
categories, productType | Public AWS Marketplace classification when published |
pricingModel, hasCustomPricing, hasFreeTrial | Normalized public pricing and purchasing signals |
priceDimensions | Public table rows with raw price plus sortable amount, currency, and billingTerm |
positioningSummary | Short executive-ready positioning summary alongside the full public overview |
overview, highlights | Public positioning copy; disable with includeDescription for a pricing-only run |
rating, reviewCount, reviewStatus | Public review signals, including an explicit no-review vs unavailable distinction |
supportContact, supportUrl | Public vendor-support details when exposed |
watchlistLabel, relationship, tags | Your customer context for filtering, reporting, and battlecards |
status, changedFields, changeSummary, changeDetails, sourceHash | State plus exact previous/current values for scheduled-monitoring changes |
customerTakeaway | Deterministic commercial next step based on public price, review, and delivery signals |
Reliable, low-cost architecture
AWS Marketplace product pages are server-rendered, so this Actor uses direct HTTP requests and Cheerio rather than a headless browser. That keeps the run fast and cost-efficient. The default is two concurrent requests with a 500 ms request delay, three bounded retries, and a 45-second request timeout. Increase concurrency only for a larger watchlist; private offers, account-only purchase details, and login-gated information are intentionally not accessed.
A blank field means AWS did not publish that data on the public product page or it could not be safely extracted. The Actor never invents prices, product types, categories, or support contacts. A blocked, missing, or malformed page produces a transparent error record instead of an empty listing record.
Boundaries and responsible use
This Actor collects only public AWS Marketplace listing pages supplied by you. It does not log into AWS, access seller portals, retrieve private offers, bypass access controls, or make claims about a vendor's product quality or legal compliance. Use the resulting public data in accordance with AWS terms, applicable law, and your organization’s policies.
Suggested pay-per-event pricing
For Store publication, price successful listing records on a pay-per-event basis (for example, $0.01–$0.03 per parsed listing plus a small start fee). Error records and unchanged records skipped by onlyChanged should not be charged. This makes small ad-hoc research inexpensive while remaining practical for high-volume scheduled competitive intelligence.
Run locally
The same extraction and diff pipeline can be smoke-tested without an Apify account or browser:
npm installnpm run local -- --input input.example.json
This writes a local Dataset-shaped JSON file to .local/dataset.json and stores the monitoring baseline in .local/snapshots.json. Re-run the same command with "onlyChanged": true to verify the no-change path locally. Both files are ignored by Git.
Store pricing
This Actor is designed for Pay per Event pricing: $0.025 for each successfully saved marketplace listing plus Apify's standard $0.00005 start event. Error records are free. See ./PRICING.md for buyer segments, margin guardrails, and the exact Store configuration.