Home › Documentation

PumpRug Documentation

PumpRug launches a token on pump.fun, buys it from a set of freshly generated wallets in the same transaction bundle, holds until a trigger you choose, sells, and sweeps every remaining lamport back to your funding wallet.

Every account on a PumpRug server is an isolated workspace. Your funding wallet, token queue, launches and live log belong to you alone — no other user can see or touch them.

The shape of it

draft ──▶ funding ──▶ launching ──▶ bought ──▶ selling ──▶ sold
                                       │
                                       └── any step can end in ──▶ failed

1. Draft — you describe the token (name, symbol, image) and the money (how many wallets, how much each spends).
2. Funding — PumpRug generates a dev wallet plus N buy wallets and funds them all in one batched transfer.
3. Launching — the token is created on pump.fun. The dev buy is an instruction inside the create transaction, and the other wallets ride the same Jito bundle.
4. Bought — it stops here and waits for you, unless you armed an auto-sell trigger.
5. Selling → sold — every wallet exits, then all SOL is swept back to your funding wallet and empty token accounts are closed to reclaim their rent.

Where to start

• Getting started — create an account and add a funding wallet.
• How it works — the launch engine in detail.
• Launches — creating and running a single launch.
• Campaigns — launching a whole queue of tokens in sequence.
• Selling & recovery — exits, auto-sell triggers, and getting stranded SOL back.
• Accounts & security — isolation, key encryption, Google Sign-In.
• API reference — every endpoint.
• FAQ & limitations — including what PumpRug does not protect you from.