Non-custodial & security
GRIDer is built so that you keep your funds and operate your own trading infrastructure. This page explains what that means, what your instance can and cannot do, and the security responsibilities that come with self-hosting.
The non-custodial model
There are two layers involved:
- Your exchange account or main wallet. It keeps custody of your funds. Its seed phrase or private key should never be entered into GRIDer.
- Trading access. A limited exchange-specific authorization your GRIDer instance uses to place orders. Its form depends on the venue — an agent wallet on Hyperliquid and Aster, a trading/API key on Lighter and Pacifica, a Stark key on Extended, and a session key on RiseX.
The crucial property of trading access:
It can trade, but it must never withdraw. Your GRIDer instance can place and cancel orders. It should not have permission to move, send, or withdraw funds.
GRIDer has no central backend that receives your trading secrets. Any API keys, agent wallets or trading credentials are stored in your own deployment.
You stay in control
- Revoke any time. You can revoke or rotate trading access directly on the exchange; that immediately cuts off the instance.
- Approvals can expire. Some trading approvals have a lifetime. As yours nears expiry, renew it so running grids can keep trading. See Instance setup.
- You own the server. If the server is compromised, the attacker may be able to trade with the permissions you granted, so use trading-only access and protect the machine carefully.
What GRIDer can and can't do
| Your GRIDer instance can | Your GRIDer instance should not be able to |
|---|---|
| Place and cancel orders for your grids | Withdraw or transfer your funds |
| Read balances, positions and fills | Access your seed phrase or main private key |
| Close a grid's position at market | Move funds to any other account |
| Record local history and PNL | Trade outside the permissions you configured |
Security measures
- Trading-only credentials. Create API keys or agent wallets without withdrawal permission.
- Self-hosted secrets. Trading credentials stay in your deployment, not in a GRIDer cloud backend.
- Server hardening. Keep the OS patched, restrict SSH, use strong authentication, and avoid exposing internal ports publicly. The one-click installer already does most of this for you — see the practical checklist in Protecting your instance.
- Encrypted storage where available. Use the software's encrypted secret storage and keep backups secure.
- Auditability. Review grid create/start/stop/delete events, order activity and exchange fills regularly.
Honest residual risk
No system is risk-free, and we won't pretend otherwise:
- The security of trading access depends on your server and operational hygiene. A full compromise of your server would be serious, but trading-only permissions mean an attacker should still be unable to withdraw funds.
- The biggest practical risk to you is the market risk of the strategy itself — a breakout against your grid — not custody. That's what Risk and range breakouts is about.
Your part
- Keep your main wallet and exchange account secure.
- Never give GRIDer withdrawal permission or your seed phrase.
- Revoke or rotate trading credentials when changing servers, ending a licence, or suspecting compromise.
- Back up your configuration and understand how to restore your instance before running large size.
Next: the FAQ.