What is strategy hosting?

Strategy hosting is infrastructure that runs a trading strategy on the user's behalf: the platform owns the runtime, the market-data feed, and the execution loop, and the strategy itself is the deployable artifact. Pancake hosts AI-built prediction-market strategies — versioned, verified, and run server-side with a public ledger-backed record.

The term separates two jobs that usually get conflated: authoring a strategy and operating it. Authoring is research — rules, parameters, evidence. Operating is infrastructure — uptime, data feeds, execution, monitoring. Strategy hosting is the product category where a platform takes the second job entirely.

Most existing options host something adjacent to the strategy rather than the strategy itself. A VPS hosts your code, and you operate it. A bot platform hosts preset bot logic keyed to your exchange account. A charting tool hosts alerts that still need a bridge to act. In each case the strategy's history lives in a private log or a platform dashboard — there is no independently checkable artifact.

Pancake's implementation makes the strategy the unit of hosting: a declarative spec, immutably versioned, where each version carries its result at a permanent URL (/<handle>/<strategy_slug>/v/<version_n>). Deploying a version creates a paper deployment — the platform runs the rules against live Polymarket data with simulated fills and appends every event to a write-once ledger.

The verification layer is what distinguishes hosting from mere running: results are reproducible (open-source deterministic engine, content-hashed inputs, SHA-256 result hash) and scoped honestly (the verification boundary names what was verified, what was agent-supplied, and what was not modeled). Live venue execution is a v2-roadmap capability built on the same artifacts.