--- url: "https://predictiontoolkit.com/tools/polyrust/" publisher: "PredictionToolkit" dateModified: "2026-11-03" --- [← Starter projects & resources]() Learning & media # Polyrust: Rust strategy framework with paper mode and replay Polyrust is a public Rust repository for building Polymarket strategy infrastructure, not a validated ready-to-run profitable bot. [**3.0**/ 5Editorial rating]() [Editorial assessment]() [Read the Polyrust repository and README]() github.com **Available on:** Rust · Self-hosted **Pricing:** [See plans and costs ↓]() [Screenshots]() [Explore alternatives]() **Availability: public** [Starter projects & resources]() [Strategy builders]() +1 more [Backtesting]() ## Screenshots and interface Product preview1 / 1 Documentation reviewed without executing the code or connecting funds. ## What is Polyrust? The nniel-ape repository documents an event-driven engine, strategy traits, execution backends and local persistence, plus historical replay, parameter sweeps and an Axum/HTMX monitoring dashboard. It separates simulated execution from live CLOB integration and describes local or container deployment with Rust 1.85 or later. The README warns that a missing configuration file can leave the Rust structure’s default in live mode. Set POLY\_PAPER\_TRADING=true explicitly for simulation and validate the configuration before considering live credentials. This review covers the repository snapshot of 26 October 2026; it did not run or security-audit the code. A redistribution licence and future maintenance cadence were not established. ### Who it is for - Rust developers building event-driven strategy infrastructure. - Researchers studying paper execution and historical replay models. ## Features and coverage - **Strategy traits and registration** Implement the documented strategy trait and register it with the engine, tracing how market events become strategy actions. - **Paper and live execution backends** The architecture separates simulated execution from live CLOB integration; configuration must deliberately select the intended mode. - **Backtests and monitoring** Study documented replay, parameter-sweep and persistence components alongside the Axum/HTMX monitoring dashboard. ## Workflows with Polyrust ### Trace the architecture Follow market events through the engine to a strategy and examine how the execution backend processes its actions. ### Select simulation explicitly Inspect configuration and set POLY\_PAPER\_TRADING=true before evaluating a strategy or replay output; do not assume missing configuration selects paper mode. ## Pricing and total cost Reading the public repository is distinct from paying to run an adaptation. The reviewed record does not establish a hosted subscription; infrastructure, data and live-trading costs need separate consideration. **Access:** The README specifies Rust 1.85 or later and local or container deployment. Public source access does not establish a redistribution licence. ## Getting started **Before you start:** Missing configuration can fall back to live mode; explicitly set POLY\_PAPER\_TRADING=true for simulation. 1. Read configuration and execution-backend documentation. 2. Inspect the source and Rust 1.85-or-later requirements in an isolated development environment. 3. Set POLY\_PAPER\_TRADING=true explicitly and validate simulation behaviour before considering live credentials. A Rust 1.85-or-later local or container environment is required; the configuration fallback must be understood before running code. ## Useful links ### What to check - Missing configuration can fall back to live mode; explicitly set POLY\_PAPER\_TRADING=true for simulation. - No code, strategy or live backend was executed or security-audited in this review. - Sample strategies and replay output are not independently validated profitable performance. - Redistribution licensing and a future maintenance cadence were not established. A closer look ## Ratings & reviews Editorial rating **3.0**/ 5 0 user reviews PredictionToolkit editorial ### Our take on Polyrust A detailed engineering reference with paper and replay components. The missing-configuration fallback is a significant operational caveat, and the code’s quality and security were not audited. Based on documented features, setup and access terms. [How we rate]() ### User reviews 0 The main score switches to user ratings after 5 published reviews. **Be the first to share your experience** A specific example helps the next person choose the right tool. ## Related tools [Browse category]() ![Goldsky Compose official framework presentation and workflow illustration]() ![Goldsky Compose logo]()[Goldsky Compose]() Infrastructure**3.5**Editorial A framework for durable TypeScript tasks spanning external services and blockchains, with market and copy-trader solution guides. - Access TypeScript · Cloud Compare local strategy infrastructure with hosted workflow orchestration. ![polymm README explaining the retired Python bot and limitations]() [polymm]() Learning & media**3.5**Editorial Educational source code and a retrospective on a retired Polymarket sports market-making bot. - Access Python · Source code Study a separate implementation and its documented execution failures. ![functionSPACE official demonstration of numerical-outcome markets]() ![functionSPACE logo]()[functionSPACE]() restricted Learning & media**3.0**Editorial Compare yes/no, range, linear and custom payoff shapes through a public prototype for market-design research. - Access Web · Developer package Also in Starter Projects and Builder Resources. ## Frequently asked questions about Polyrust ### Does missing configuration always mean paper mode? No. Without a configuration file, the Rust structure’s fallback can select live mode. Treat simulation as an explicit configuration choice and verify it before using live credentials. ### Are its sample strategies proven profitable? No independent performance validation was performed. Treat them as code to study and test. ### Is there a hosted subscription? None was established by the review. The repository is public; hosting, data and live-trading expenses are separate. ### What environment is documented? Rust 1.85 or later, deployed locally or in a container according to the README. In this profile