Operate
Give the runtime a stable place to process every candle.
Gimmer runs on the user-controlled machine or configured runtime. A laptop that sleeps, reboots, loses network access, or closes the app cannot continuously operate a local strategy.
Choose an operating model
| Model | Good fit | Main responsibility |
|---|---|---|
| Local desktop | Supervised use while the computer remains on and connected. | Prevent sleep, keep the app running, and monitor updates and network. |
| Dedicated computer | Long-running strategies without sharing the device with daily work. | Maintain power, security patches, backups, and remote access. |
| VPS or remote host | Always-on operation with stable networking and a managed runtime. | Secure the host, restrict access, monitor resources, and back up local state. |
| Configured AI runtime | AI Decision strategies that depend on a separate runtime profile. | Keep both the strategy executor and AI service healthy with safe failure behavior. |
Prepare an always-on host
- Use a supported operating system and architecture. Install the matching Gimmer release asset.
- Secure access. Use key-based remote authentication, restrict inbound ports, and protect the administrator account.
- Set accurate time. Enable time synchronization because candle and exchange authentication depend on timestamps.
- Prevent unattended sleep. Configure the host and desktop session so the required process remains active.
- Preserve local state. Back up the workspace and document the restore and exchange-reconciliation procedure.
- Monitor liveness. Alert when the app, connection, or strategy stops processing expected candles.
Monitor more than process uptime
A running process can still have a stale exchange connection or stuck strategy. Use the latest expected closed-candle event per running strategy as the primary liveness signal. Also monitor disk space, memory, clock drift, network reachability, exchange errors, and pending order state.
Availability does not remove risk
A VPS can improve uptime but introduces another system to secure, patch, fund, and recover. It does not guarantee fills, correct data, profitable decisions, or uninterrupted exchange access.
Plan restart and recovery
- Restart one component at a time and record the time.
- After restart, verify the last processed candle for every running strategy.
- Confirm that catch-up processing is idempotent and does not duplicate orders or positions.
- Reconcile external exchange state before enabling live execution again.