Local execution with a clear separation
The local runner loads the strategy configuration, reads locally stored credentials, connects to the configured exchange, tracks order states, and stores operational trading data in a local database.
The Connector submits and reconciles exchange orders. NuxGrid.com is not the process that directly places each trading order.
- Configure
- Control
- Monitor
- Local bot
- Encrypted credentials
- Local operational state
- Binance
- OKX
- Bitstamp
- Bitkub
The browser can be closed. The bot continues running on your machine.
A three-step operation
NuxGrid.com provides the web console for configuration, control, monitoring, and account communication. The Connector communicates with the server through outbound HTTPS requests. It does not require an inbound web server on the Connector machine.
- Configure strategies
- Control and change parameters
- Track state and view history
- Execute orders
- Track states and positions
- Keep operational data locally
- Receive orders
- Execute transactions
- Hold funds
NuxGrid.com does not place orders directly on the exchange: the Connector executes them from your machine.
Yes, the bot keeps running
Yes. Closing the browser does not automatically stop the local runner.
The local process can continue while the web console is closed, provided the Connector machine, local services, exchange connection, account state, and strategy configuration remain operational.
An offline status describes communication with NuxGrid.com. It does not by itself prove that the local runner has stopped.
- The machine stays on
- The Internet works
- The exchange remains accessible
An offline NuxGrid.com status describes communication with the server. It does not by itself prove that the local runner has stopped.
Local trading may continue
The Connector keeps the last known account trading state locally. If the account was active before a temporary server outage, the local runner may continue using its local configuration and exchange connection.
Remote commands, configuration changes, monitoring updates, and alerts may be unavailable or delayed. If the last known state was suspended, the local runner remains dormant.
The Connector may continue with the last valid local state or configuration it knows when the required conditions remain available.
Encrypted credentials on your machine
Exchange credentials are encrypted before delivery from the browser. The Connector decrypts them locally, validates them directly with the exchange, and stores the validated values on the Connector machine.
Plaintext credentials are not included in the normal strategy configuration or telemetry payload. This should not be described as zero-knowledge security or as an absolute guarantee that keys can never be accessed. The local credential file is protected by operating-system permissions, but it is not encrypted at rest by NuxGrid itself.
The Connector private key remains on your machine.
Dependencies to keep in mind
Local execution reduces dependence on an open browser, but it does not remove dependence on the machine, its operating system, its network, the exchange, valid API access, or correct configuration.
NuxGrid is Bitcoin-first, although the live configuration accepts broader market symbols. The current live adapters support Bitkub, Binance, OKX, and Bitstamp.