Computing deployer reputation for ~27k real Pump.fun deployers means a validator gRPC feed, an indexing pipeline, terabytes of storage, and bond attribution — or a €99 file. Here's the honest cost breakdown, including where building your own still wins.
Building a product on Solana data?
Skip the Geyser pipeline — embed KOL flow, deployer reputation, and the all-DEX firehose over REST, WebSocket, or webhooks. The Business tier (€400/mo) is the self-serve embed license at 500k calls/day — Enterprise adds white-label & redistribution.
We are a data company and we still tell people to build their own in one specific situation: you need it real-time. The dataset is a current-state snapshot. It is perfect for backtesting, rug-screening a launch against a known deployer, enriching a token table, or filtering deployers for a sniper's allow-list. It is the wrong tool if your product depends on scoring a deployer the second they launch a brand-new token, because a downloadable file is a point in time, not a live feed.
| Your need | Best path |
|---|---|
| Backtest / research on deployer outcomes | Buy the file — snapshot is exactly right |
| Rug-screen a launch by its deployer's track record | Buy the file — look up the wallet, done |
| Enrich a token table with deployer stats | Buy the file — it's a join key away |
| Seed a sniper allow/deny list | Buy the file, refresh periodically |
| Score deployers in real time, at launch | Build it, or use our API — a static file can't |
| Millisecond-fresh reputation in your own trading loop | Build it — you want to own the latency |
That last row is the honest concession. If sub-second freshness inside your own execution path is the whole point, you do not want a file and you may not even want our API — you want your own node and pipeline, latency you control end to end. For everything short of that, the file wins on every axis that matters, and the API covers the real-time middle without you owning a validator.
Roughly 27,000 real Pump.fun deployers — every wallet that has bonded at least one token, with spam stubs excluded — one row each, with bonding_rate, runner_rate, post_bond_survival_rate, post_bond_2x_rate, best_token_peak_mc, and a tier from elite to cold. It is a current-state snapshot whose earliest launches reach back to January 2024. It costs €99 as identity-scrubbed, SHA-256-checksummed CSV.gz with a free 5,000-row sample.
You can, but it requires a validator-grade transaction feed, a decode-and-index pipeline that never misses a graduation, multiple terabytes of retained history, and correct bond attribution with spam exclusion. That is weeks of engineering plus an ongoing infrastructure bill to reproduce a €99 file you can download in minutes.
When you need reputation in real time — scoring a deployer the instant they launch, inside your own trading loop. A downloadable file is a snapshot, not a live feed. For that case, run your own pipeline or use our , which streams the same intelligence without you hosting a node.
Tools mentioned
Live health scores, average ratings, and direct links on MadeOnSol.
MCP server powered by Solana Agent Kit for on-chain actions
Telegram trading bot for Solana — snipe new tokens, set limit orders, auto-sell, and copy trade with built-in MEV protection
Unified crypto API covering 120+ blockchains, 200+ exchanges, and 10,000+ DeFi protocols with wallet, market, and portfolio data
Browser-based IDE for developing and deploying Solana programs
Native Solana support inside the MetaMask browser wallet
Build a deployer sniper bot
Access deployer alerts, bonding stats, and tier data via API. Free tier: 200 requests/day.
New customers try Pro free for 5 days — card, cancel anytime.
import { MadeOnSol } from "madeonsol";
const client = new MadeOnSol({ apiKey: "msk_your_key" });
// Elite deployer alerts with KOL buy enrichment
const { alerts } = await client.deployer.alerts({ limit: 5 });
// Top deployers by bonding rate
const { deployers } = await client.deployer.leaderboard({ tier: "elite" });Building a product on Solana data?
MadeOnSol isn't an RPC or another generic token API — it's Solana memecoin intelligence that's painful to build in-house, pulled from dual-region gRPC shred streams: sub-second from the on-chain event to your app.
Signals you'd otherwise build
KOL & smart-money flow from 1,000+ labeled wallets, deployer reputation, coordination clusters, linked-wallet entity resolution, and an all-DEX firehose.
Embed it in your product
The Business tier (€400/mo, self-serve) licenses you to display MadeOnSol data inside your own product — 500k calls/day, 10 WS + 5 firehose connections. Enterprise above adds white-label & redistribution rights and custom endpoints.
Evaluate first, commit later
Test everything on a free ULTRA key — no commitment. If it fits, we scope volume or white-label pricing.
Keep reading
Analytics
Four ready-to-analyze Solana datasets — 1.25M scored wallets, 1.5M priced KOL trades, 27k real deployers, plus genesis-complete Robinhood Chain — as scrubbed, checksummed CSVs with free 5,000-row samples.
Analytics
A €149 CSV of Robinhood Chain intelligence indexed from block zero — deployer reputation, smart-money scores, and token lifecycle since the 2026-04-30 genesis. No incumbent has genesis-complete RHC history, because the chain is too new to have one.
Analytics
1.25M Solana wallets, each pre-scored with win_rate, net_pnl_sol, roi, bundle_rate and a 0–1 bot_confidence label — a ready-made feature table for copy-trade backtests and model training.
Analytics
On-chain datasets built for reproducible research: SHA-256 checksums, fixed temporalCoverage windows, identity-scrubbed pseudonymous rows, and schema.org/Dataset JSON-LD that makes every set citable and discoverable in Google Dataset Search.
Analytics
The sol-kol-trades dataset stamps price and market cap at execution on every one of 1.5M+ rows — so you can compute realized copy-trade PnL with no price oracle and no look-ahead bias.
Guides
Robinhood Chain has no public mempool, so early token discovery is a data race, not a gas war. Here's how to catch new RHC tokens on the bonding curve before they graduate into Uniswap.
Enjoyed this article?
Real-time KOL trades, Pump.fun deployer intel, and 1,200+ ranked Solana tools — free to explore.
Open the KOL TrackerThe sol-deployers dataset is €99: a CSV of roughly 27,000 real Pump.fun deployers — every wallet that has bonded at least one token, with spam stubs excluded — each row carrying bonding_rate, runner_rate, post_bond_survival_rate, post_bond_2x_rate, best_token_peak_mc, and a tier from elite down to cold. It is a current-state reputation snapshot whose earliest launches reach back to January 2024. The question this post answers is the one every data team asks before buying: couldn't we just build this ourselves? You can. Here is what it actually takes, and where the €99 file wins versus where rolling your own is genuinely the right call.
The short version: building a one-time reputation snapshot from scratch is weeks of engineering and a running infrastructure bill to reproduce a file you can download this afternoon. Building a real-time deployer feed is a different project, and there the buy-vs-build math flips — which is why we sell the snapshot as a file and the live version as an API.
Deployer reputation is not a query you run against a public endpoint. It is a derived metric that sits on top of a full ingestion-and-attribution pipeline. To produce the columns in sol-deployers yourself, you need every one of these:
Reputation requires seeing every Pump.fun deploy, buy, sell, and bonding event — not a sampled subset. That means a gRPC/Geyser stream from a Solana validator (self-hosted or a paid provider), because polling public RPC will rate-limit you and drop transactions long before you have full coverage. We go deep on this exact trade-off in Solana API vs self-hosting a node: a managed streaming plan is a real monthly line item, and a self-hosted node is bare-metal hardware plus bandwidth plus the person who keeps it alive.
A firehose is not data; it is a firehose. You need a service that decodes each transaction against the Pump.fun program layout, identifies deploys, tracks each token's bonding-curve progress, and detects the graduation event. Streams stall, nodes lag behind the tip, and programs rename their instructions — every gap is a token you either double-count or miss, and a missed graduation silently corrupts the deployer's bonding_rate. Getting this reliable is the bulk of the engineering.
Reputation is computed over history, so you have to retain the trade and deploy history — not just the latest state. That is a growing multi-terabyte store with its own tiering, indexing, and vacuum strategy. The naive version fills a disk in weeks; the maintained version is an ongoing storage cost plus DBA attention.
This is where most home-grown attempts quietly go wrong. You have to correctly attribute each token's graduation back to the deployer wallet, distinguish real deployers from the spam factories that mint-and-abandon in bulk, and denormalize per-token outcomes (survival, 2x, peak market cap) back onto the deployer. The methodology behind the numbers is documented in our Pump.fun deployer analysis of 561k wallets — the point of that piece is that turning 561k raw deployer wallets into ~27k real ones with trustworthy stats is the entire job. Skip the spam-exclusion step and your "elite" tier is polluted with wallets that got one lucky launch out of three thousand.
| Build it yourself | Buy sol-deployers | |
|---|---|---|
| Transaction feed | Validator gRPC or paid stream (monthly) | Included |
| Indexing pipeline | Weeks of engineering + ongoing maintenance | Included |
| Storage | Multi-TB, growing, with tuning | Zero |
| Bond attribution + spam exclusion | Bespoke, easy to get wrong | Done, ~27k real deployers |
| Time to first usable data | Weeks | Minutes |
| Upfront cost | Engineering time + infra spend | €99, one-time |
| Ongoing cost | Infra + maintenance forever | Zero (it's a file) |
| Reproducibility | Yours to guarantee | SHA-256 checksummed, fixed snapshot |
None of the "build" line items are hypothetical. They are the same pipeline we run in production to power the deployer-hunter tool and the API. The €99 is not a data-access fee; it is the amortized output of that pipeline handed to you as a file, with the spam already filtered and the attribution already correct.
That post explains how the reputation is computed and points at the on-site tool. This post is about buying the finished, filtered file — the ~27k real deployers — at /datasets/sol-deployers. Same data, different intent: one explains the method, the other hands you the output.
Deployer reputation looks like a lookup and is actually a pipeline: validator feed, indexing, terabytes of storage, and bond attribution with spam excluded. Reproducing it to get a one-time snapshot costs weeks and a running infra bill; the finished, spam-filtered file of ~27k real deployers costs €99. Buy it when you need a snapshot for backtesting, rug-screening, or enrichment — build it (or use the API) only when real-time freshness is the actual product. The file, the free sample, and the full column list are at /datasets/sol-deployers. For the citation-grade research angle across every set, see the academic and quant guide, and for the full catalog start at the datasets hub.