Apache is a Solana launch terminal, and home to ApeSync, our trading engine. We're running it with a small group of early users and opening the doors soon.
Apache is where launches are prepared: the wallets, the money, soon the launch itself. ApeSync is where they're traded: it buys first, copies the best wallets and gets out on time. One account, one login, a product chooser in between.
Everything around a Solana token launch in one place, starting with the hardest part to do by hand: hundreds of wallets.
A Rust engine that sees Solana trades before they execute, and acts in the same breath: snipes, copies and exits.
A launch runs on wallets: a main wallet with the money, funding wallets that split it, and dozens of buyer wallets that each need SOL at the right moment. Apache keeps all of them in one cabinet and moves SOL between them in bulk.
Buyer wallets live in folders. Built for 1–2 thousand wallets and hundreds of folders per account, with filters and natural sorting.
Fund a whole folder from a funding wallet. Up to 20 buyer wallets per transaction, sent in parallel batches.
Sweep SOL back from buyer wallets into one wallet, 9 per transaction. The richest wallet pays the fee, so the target needs none.
Keys are generated on our servers and encrypted with AES-256-GCM. They never reach the browser, and every transfer is simulated before it's sent.
Main, funding and buyer balances read straight from the chain, rolled up per folder, so you see where the money sits.
Deposit with an address or QR code, then move SOL between any of your wallets with one confirmation.
ApeSync is our trading engine, written in Rust and running in Frankfurt, one of Solana's busiest validator hubs. It reads transactions straight from the network before they execute, decides in microseconds, and sends from many wallets at once. Members steer it from a live panel.
It follows your team's dev wallets. The moment one of them creates a coin on pump.fun, from the site or any launch tool, every buy wallet fires its own transaction, aiming for the very same block.
Add a leader wallet and ApeSync repeats its pump.fun trades on the curve and on PumpSwap. Direct trades are caught before they execute; trades routed through Axiom, Photon, Jupiter and other tools moments after they land.
Every position carries a sell for 100% that is already signed and re-signed on each price move, so when a rule fires there's nothing left to build: it goes out in under a millisecond. Rules work on the bonding curve and after migration to PumpSwap, for sniped and copied coins alike.
The engine runs on our servers. The team and invited clients share it through a panel inside Apache, with live updates and nothing to install.
Engine state, feeds, launches and fills as they happen.
Value, PnL and curve progress per coin, with one-tap sells.
Buy wallets, per-wallet sizes and balances. Create them in bulk.
Every trade with its transactions, and who changed what.
A Solana block lasts about 400 milliseconds. Everything ApeSync does between seeing a trade and sending ours fits into two of them.
Same engine, same feeds. The difference is distance: Frankfurt sits a millisecond from the services that carry transactions to Solana's leaders.
Measured on our servers in October 2026. Network conditions vary from launch to launch.
Both products move real SOL on mainnet. So keys stay put, real-money actions take a deliberate step, and every change leaves a trace.
Apache encrypts every wallet key with AES-256-GCM; ApeSync keeps its keys on a locked-down engine server. The browser only ever sees addresses.
The trading engine has no public address. Only the panel talks to it, over a private network behind a firewall.
Everything starts in dry-run. Going live and withdrawing both ask you to type a confirmation first.
Arming, settings, sells and withdrawals are written to an audit log with who did it and when.
ApeSync opens only for members an admin lets in, one account at a time. Everyone else sees Apache.
Traffic is filtered for attacks and encrypted on every hop, from your browser to our servers.
The beta opens in stages. Each one lets more people in.
A small group uses the product while we fix what breaks. Accounts are added by hand.
Sign-ups open to everyone. Features keep changing as we learn what works.
Stable release. We'll announce the date here first.
Short answers. More once the doors open.
Apache is a Solana launch terminal. Today it manages the wallets a launch runs on: main, funding and buyer wallets in folders, with bulk transfers between them. Projects, launches and statistics come next.
Our trading engine for pump.fun and PumpSwap: it snipes your team's launches, copies leader wallets and exits positions by rules. It runs on our servers; invited members steer it from a panel inside Apache.
Not yet. During the private beta we add people one by one. Sign-ups open with the public beta.
Apache wallets are custodial: they're created on our servers and their keys are stored there, encrypted. You see addresses and balances and move funds from the app; keys never reach your browser.
Expect changes and the occasional bug. We may reset data between beta builds and will warn you before we do.
When it's ready, not on a fixed date. This page changes the day Apache opens sign-ups.
We're letting people in stage by stage. This page changes the day sign-ups open.