Skip to content
Illustration: a small block outpost and a red rocket on its pad atop a desert mesa, rows of crates on the plain below
Apache · private beta

Every wallet behind
your launch.

Apache is the launch terminal: main, funding and buyer wallets in one cabinet, bulk moves that run on their own, and a workspace for your whole team. Projects, launches and statistics come next.

2,000
Wallets per workspace, in folders
20
Buyer wallets funded per transaction
9 → 1
Wallets swept per collect transaction
0
Private keys that reach your browser
How it works

From an empty workspace to funded wallets.

Three steps, done once per launch. After that, moving money around is a click and a confirmation.

  1. 01

    Open a workspace

    Create a workspace for the launch team and invite people as owners, admins or members. Wallets, folders and transfers belong to it.

  2. 02

    Set up the wallets

    The main wallet holds the money, funding wallets split it, and buyer wallets are generated in bulk into folders, as many as the launch needs.

  3. 03

    Move SOL in bulk

    Distribute to a whole folder or collect it back in one job, and watch it go step by step. Every transaction is simulated before it is sent.

The wallets cabinet

Hundreds of wallets, one view.

Main, funding and buyer wallets with live balances read from the chain, rolled up per folder. Built for one to two thousand wallets per workspace without slowing down.

Main walletyour treasury
Funding 1splits SOL out
Funding 2keeps flows apart
launch-0724 wallets
launch-0824 wallets
SOL moving funded buyer walletIllustration of the wallets cabinet

Folders that scale

Buyer wallets live in folders. Built for one to two thousand wallets and hundreds of folders per workspace, with filters and natural sorting.

Bulk distribute

Fund a whole folder from a funding wallet. Up to 20 buyer wallets per transaction, sent in parallel batches.

Bulk collect

Sweep SOL back from buyer wallets into one wallet, 9 per transaction. The richest wallet pays the fee, so the target needs none.

Encrypted custody

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.

Live balances

Main, funding and buyer balances read straight from the chain, rolled up per folder, so you see where the money sits.

Deposit and move

Deposit with an address or QR code, then move SOL between any of your wallets with one confirmation.

Bulk moves

Press Start, close the tab.

A bulk move is a job. You review it, press Start, and our worker sends it step by step. One step is one transaction: signed and saved before it goes out, then sent again and checked until the chain says confirmed, failed or expired. Only then does it try again, three times at most.

  • Distribute: one funding or main wallet to up to 20 buyers per transaction
  • Collect: up to 9 wallets into one, the richest pays the fee
  • Your pace: wallets per transaction and a random pause between steps
  • Pause, resume and retry failed steps; progress live on every page
Distribute · launch-07Funding 1 → 24 buyer walletsRunning
2.00 of 2.40 SOL sentStep 2 of 2
  • Step 1 · 20 walletsone transaction, landedConfirmed
  • Step 2 · 4 walletsattempt 1 of 3Sending
Pause between steps: random, 2 to 6 sIllustration of a job
Workspaces

One cabinet for the whole launch team.

Wallets, folders and transfers belong to a workspace, not to a person. Invite your team, give each member a role, and everyone works from the same live balances.

Roles

Owners, admins and members. Each sees the same cabinet with what their role allows.

Invites

Bring people in with an invite. Several workspaces per account, one for each team or client.

Money stays inside

Members move SOL between the workspace's own wallets. Sending out of it is for owners and admins.

Who sent what

Every transfer records who started it, so a busy launch day can be read back later.

Custody

Keys stay put.

Apache wallets are custodial and live on Solana mainnet. So the keys stay on our servers, encrypted, and nothing is sent without a dry run first.

Keys sealed per wallet

Every key is encrypted with AES-256-GCM and bound to its own address, so one can never stand in for another.

Never in the browser

The app shows addresses and balances. Keys are read only at the moment a transaction is signed, on the server.

Simulated first

Every transaction is built and simulated before it is signed, so a move that would fail never leaves.

Behind Cloudflare

Traffic is filtered for attacks and encrypted on every hop, from your browser to our servers.

Roadmap

Live today, next in line.

Apache is in private beta and growing fast. Here is what you can use now and what we're building next.

Trading with ApeSync

Live in Apache now

On mainnet
  • Main, funding and buyer wallets in folders
  • Bulk distribute and collect, run as jobs
  • Deposits, withdrawals and transfers in SOL and USDC
  • Team workspaces with roles and invites

Coming next to Apache

In development
  • ProjectsGroup wallets, launches and results by project, so each token has its own space.
  • LaunchStart a token launch from Apache and line your wallet sets up around it.
  • StatisticsSpend, returns and activity across projects and wallets, in one view.
FAQ

About Apache

What teams ask before their first launch.

What is Apache?

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.

How many wallets can a workspace hold?

The cabinet is built for one to two thousand wallets and hundreds of folders per workspace, with filters, natural sorting and paged tables, so a big launch stays readable.

Can my team work in it together?

Yes. A workspace has owners, admins and members, who join by invite. Wallets, folders and transfers belong to the workspace. Members move funds inside it; sending out of the workspace is for owners and admins.

What if I close the tab during a bulk move?

Nothing changes. Bulk moves run as jobs on our worker, not in your browser. Each step is one transaction, signed and saved before it goes out, and checked until the chain confirms it, rejects it or it expires.

Who holds the keys?

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.

Is it on mainnet?

Yes, Solana mainnet only. There is no test network mode, so every move is real money. That is why every transfer is simulated before it is sent.

What comes next?

Projects to group wallets and results per token, launching a token from Apache itself, and statistics across projects and wallets. They arrive during the beta, one by one.

Illustration: later that night, the rocket is a bright point high above the mesas, its contrail arcing up
Private beta, sign ups open

The doors
are open.

Make an account today. During the beta an admin opens Apache and ApeSync for each account, so there may be a short wait.

Join the private beta

Free to join. ApeSync only earns on sells that make a profit.