Always-On Trading

Your vault keeps trading while you are offline, for as long as our service is up.

How It Works

Unlike self-hosted trading bots that require your computer to stay running, Grid Master's trading engine runs on our infrastructure. Once your vault is active, it continues trading without any action from you.

Cloud-Based Execution

Our servers monitor prices and execute trades on your vault continuously while our service is up. We do not guarantee uptime.

What This Means For You

No Babysitting

Set up your vault and let it run. No need to monitor it constantly.

Close Your Laptop

The bot runs on our servers, not your device. Go about your day.

Works While You Sleep

Market moves at 3 AM? The bot handles it.

Check In Anytime

View your vault's performance, trades, and PnL from any device.

The Setup

You

Create vault, set parameters

→

Grid Master

Monitors & executes while the service is up

→

Solana / Robinhood Chain

Trades execute on-chain

Common Questions

Do I need to keep the website open?

No. Once your vault is created and active, you can close the browser. The bot runs independently on our servers.

What if the Grid Master servers go down?

Your funds stay in your vault. Trading pauses until service resumes, and you can still withdraw directly from the blockchain. We do not guarantee uptime.

Can I still control my vault when I'm away?

Yes. You can access the dashboard from any device to pause the bot, change its risk limits, or withdraw funds. The grid's price range and level count are fixed at creation and cannot be edited afterwards.

How quickly does the bot respond to price changes?

The bot monitors prices continuously and can execute trades within seconds of a grid level being crossed.

Is the platform scalable?

Not proven yet. Today one keeper service looks after every vault. The code can run more than one keeper instance, with each vault looked after by one instance at a time, but we have not tested it with large numbers of vaults and we do not publish a capacity figure. The keeper reads the chains through RPC providers that limit how many requests it can make.