SOLANA TOOLS / FOR TEAMS
Own your implementation path.
License the agreed project source code for your Solana product. A perpetual, non-exclusive commercial license can include modification rights for the Pump.fun and Raydium adapters.
A reviewable source delivery
Agree the code version, protocol modules, build instructions and deployment documentation before purchase. The current application exports a browser-based static site.
Build on the protocol adapters
The enterprise agreement can authorize modification of project-owned Pump.fun and Raydium integration code for your licensed product. Third-party SDK and service terms continue to apply.
Define automation separately
Server-side signing, unattended trading strategies, private API proxies and dedicated RPC scheduling are separately scoped development. The supplied workspace uses connected-wallet approval.
Architecture you can evaluate
Configure a browser-compatible Solana RPC endpoint. Independent chain reads run in parallel where implemented; multiple-account queries reduce serial request round trips.
Protocol swaps request Jupiter routes restricted to the selected protocol. The client checks amounts, slippage thresholds, program addresses and key accounts. Jupiter supplies routing; Solana Tools applies protocol constraints and transaction validation.
Transactions are constructed in the browser and approved by the connected wallet. Relevant flows verify the target network and simulate the transaction before signing.
Interaction time depends on RPC response, quote services, wallet approval and network congestion. No fixed execution latency or inclusion guarantee is offered.
Choose the delivery model
White-label Deployment
A branded deployment for the scope agreed in the commercial contract.
- Agreed brand, domain and interface changes
- Deployment and acceptance scope defined before delivery
- Source redistribution rights require a separate agreement
Enterprise Source License
A perpetual, non-exclusive commercial license for agreed project-owned code, with modification rights.
- Named source version and protocol modules
- Pump.fun and Raydium adapter modification within the agreed scope
- Third-party licenses and service terms remain applicable
Pricing is provided after a technical scope review. Network fees, account rent and external service costs are separate.
Technical and licensing questions
Can we modify the Pump.fun and Raydium integrations?
The enterprise source agreement can authorize secondary development of project-owned Pump.fun and Raydium adapter code for the licensed commercial product. Deployment count, affiliated-company use and redistribution limits must be specified. Third-party SDK, protocol-service and brand terms remain applicable.
What is delivered with white-label deployment versus source licensing?
White-label delivery covers the agreed branding, domain and deployment. Enterprise source delivery adds the named code, build documentation and agreed modification rights. Protocol modules, acceptance checks and support duration are listed in the contract.
Does the Raydium LP manager support every pool and Token2022 asset?
Coverage depends on pool type, operation and token extensions. Define creation, liquidity, position and fee-collection acceptance separately for each supported pool type. Code coverage is not a substitute for real-wallet acceptance with your intended assets.
Can we use our own RPC and run an unattended trading bot?
The current static frontend supports configurable browser-compatible RPC endpoints and connected-wallet signing. Private API proxies, server-side signing, unattended strategies and dedicated RPC scheduling are separately scoped work. Secret credentials must not be embedded in public frontend configuration.
How are delivery acceptance and protocol upgrades handled?
Bind acceptance to a code version and agreed protocol actions. Verify build and deployment, wallet signing, on-chain results and uncertain-confirmation recovery, retaining agreed small-value transaction records. Ongoing protocol adaptation, service fees and response times require separate maintenance terms.
Review your deployment with 0xF1
Share your target workflows, pool types, branding requirements and source-license needs. Use the contact options on fone.cc to request a technical walkthrough and a scoped quote.
Contact details and availability are maintained on the creator’s website.