Nomad Bitgrove applies predictive models to market data and surfaces decisions you can review before you act. No manual charting. No technical setup. Every output is logged for independent review.
Reviewing market data by hand is slow and inconsistent. A predictive model applies the same criteria to every data point, continuously, without fatigue or bias. The table below sets out the practical difference.
| Task | Manual analysis | Nomad Bitgrove model |
|---|---|---|
| Data reviewed | Limited by hours in the day | Continuous, around the clock |
| Consistency | Varies with fatigue and mood | Fixed criteria, every cycle |
| Record keeping | Often informal or absent | Logged and timestamped |
| Technical skill required | Moderate to high | None, by design |
The process is deliberately short. Each stage is visible to you, and nothing proceeds without the previous step completing correctly.
Market and account data is pulled into the platform automatically. You connect your account once; no spreadsheets or manual uploads are required afterwards.
The predictive model scores incoming data against historical patterns and current conditions, narrowing a large data set down to a short list of relevant decisions.
Approved decisions are executed within the limits you set in advance. You can review every action afterwards in the performance log.
We publish outcomes rather than projections. Figures in the log reflect what the model actually did, not a simulation of what it might do.
Every executed decision is written to the log at the moment it occurs, not retrospectively. Community members with active accounts can cross-check entries against their own account history, which makes retroactive editing impractical.
We do not remove unfavourable entries from the record. A complete log, including underperforming periods, is the only basis on which the model can reasonably be judged.
Capital preservation is treated as a primary objective, not an afterthought. The model operates inside fixed boundaries that you define before any decision is executed.
Before execution, each decision is checked against your stated risk limits. If a decision would breach those limits, it is discarded rather than adjusted. This keeps the model's behaviour predictable, even during unusual market conditions.
These settings are visible and editable at any time from your dashboard. Nothing is fixed permanently, and no limit is applied without your knowledge.
Nomad Bitgrove was built on a simple observation: most people considering an alternative income stream have the capital to act, but not the hours required to analyse markets manually or the technical background to build their own models.
The platform exists to close that gap, with a model that runs continuously and a log that lets you verify what it has actually done, rather than take performance on trust.
Read more about Nomad Bitgrove
No. Account connection is handled through a guided setup, and the predictive model runs without requiring you to write rules, code, or formulas. Your role is to set your risk limits and review the logs.
Withdrawal timing depends on your connected account provider rather than Nomad Bitgrove itself. Once a withdrawal request is submitted, it is processed on the next available settlement cycle, typically within a few UK business days.
Account data is encrypted in transit and at rest. Nomad Bitgrove does not sell account data to third parties, and access to raw data is restricted to the systems required to run the predictive model and maintain the performance log.
There is no fixed minimum enforced by the platform itself, though your account provider may set its own threshold. We recommend starting with an amount you are comfortable reviewing closely during your first few weeks.
Underperforming periods are recorded in the log alongside successful ones. Your risk limits, including drawdown thresholds, remain active throughout, and you retain the ability to pause the model at any time.
Have a question not covered here? Visit the full FAQ or contact our support team.
Setup takes a few minutes. You set the risk limits, the model runs continuously, and the log keeps a verifiable record of what it does.