A controlled environment for automated work
A VPS for running authorised market tools with clear operating and key boundaries.
Content revised · English
- Architecture to evaluate
- Linux API worker / Windows terminal
- Prepared starting points
- 4 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- Linux API worker / Windows terminal.
- Use keys with the narrowest permission.
- Recover application state deliberately.
Linux API worker / Windows terminal
A Linux API worker and a Windows MetaTrader/cTrader-style terminal need different operating systems and maintenance. Verify application support and licence rights. Choose region from measurements to the real broker or exchange endpoint rather than an untested proximity claim.
Use keys with the narrowest permission
Keep API credentials outside source code and logs, and disable withdrawal permission unless a separately justified workflow requires it. Track each attempted operation with an identifier and reconcile uncertain results before retrying. A timeout can occur after the remote action has already succeeded.
Recover application state deliberately
Use consistent PostgreSQL or SQLite backups as appropriate, and configure durable queues carefully. Monitor connectivity and failed actions; preserve a tested stop mechanism. Infrastructure availability does not remove market risk or guarantee an automated strategy’s result.
Choose proximity with evidence
A regional label does not prove latency to an exchange. Test the actual endpoint and connection quality, and confirm that the software, API and account permit automated use.
Separate keys and permissions
Give automation only the exchange permissions it needs. Avoid withdrawal permissions where they are unnecessary, protect secrets and restrict access to the server's administration interface.
Build failure handling
Use order limits, position controls and an explicit stop mechanism. Record errors and reconcile state after outages. Infrastructure availability does not establish a trading strategy's performance or financial safety.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Umbra 2
Give web applications, containers or a private tunnel two AMD EPYC virtual CPUs, 4 GB of ECC memory and 60 GB of NVMe storage. Root access on KVM, a 1 Gbps port and 3 TB of monthly transfer provide more room than the entry configuration without moving to dedicated hardware.
- Compute
- 2 vCPU (AMD EPYC)
- Memory
- 4 GB DDR4 ECC
- Storage
- 60 GB NVMe SSD
- Transfer
- 3 TB / month
billed monthly
Umbra 4
Balance four AMD EPYC virtual CPUs and 8 GB of ECC memory with 120 GB of NVMe storage for several services or a growing application. This KVM configuration includes a weekly snapshot, 6 TB of monthly transfer on a 1 Gbps port and a 20 Gbps network mitigation tier.
- Compute
- 4 vCPU (AMD EPYC)
- Memory
- 8 GB DDR4 ECC
- Storage
- 120 GB NVMe SSD
- Transfer
- 6 TB / month
billed monthly
Dusk 4
Move remote work and Windows applications onto four virtual CPUs, 8 GB of DDR4 memory and 120 GB of SSD storage. The configuration includes Windows licensing, administrator access and a multi-user RDP option, alongside 6 TB of monthly transfer and a 20 Gbps network mitigation tier.
- Compute
- 4 vCPU (Xeon)
- Memory
- 8 GB DDR4
- Storage
- 120 GB SSD
- Transfer
- 6 TB / month
billed monthly
Dusk 8
Give heavier Windows applications eight virtual CPUs, 16 GB of DDR4 memory and 240 GB of SSD storage. Administrator RDP and a configuration supporting up to 20 users sit alongside a 1 Gbps port, 10 TB of monthly transfer and a 40 Gbps network mitigation tier.
- Compute
- 8 vCPU (Xeon)
- Memory
- 16 GB DDR4
- Storage
- 240 GB SSD
- Transfer
- 10 TB / month
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
What latency is available to my exchange?
No measured Ombra route is published. Test the actual broker/exchange endpoint from the chosen location, including timeouts and reconnect behaviour.
Can I run MetaTrader or another Windows terminal?
Only on an appropriately supported Windows product with the required licence rights. A Linux API worker has a different deployment model.
Are CPU pinning and live migration active?
No low-jitter pinning or live-migration platform is connected. Such requirements need a verified plan and an operational agreement.
How should I recover the bot after a failure?
Restore consistent application state, reconcile uncertain remote actions before retrying and use least-privilege keys. Maintain a tested stop mechanism; hosting does not remove market risk.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.