Isolation.
Turbine can give each user a dedicated runner. One user's code cannot reach another user's bot.
Product · Sandbox Runtime
Turbine ships the bot. The runner trades.
Turbine can deploy each bot to a dedicated sandbox runner provisioned on a third-party compute provider. Kalshi API keys live in the runner. turbinefi stays out of the trading path.
CustodyKeys in runner
ComputeThird-party provider
Top-upsX402
Runner runs the bot. Bot trades Kalshi. Turbine builds and deploys the strategy, then steps out of the trading path. The runner keeps trading even if turbinefi is offline.
One deploy. The runner takes it from there.
The runner has the Kalshi keys. The runner runs the strategy. Turbine compiles your sentence, hands the artifact to the runner, and walks away. We can be offline tomorrow and your bot keeps trading.
X402 is an HTTP-native standard for agent payments. Turbine tops up your runner's compute balance directly with the provider, so the financial path between you and the compute is not running through us as a middleman.
Compute billed at cost.
You see the runner balance in your account. The compute provider sets the price; we do not mark it up. The turbinefi subscription pays for the Studio where Turbine builds the bot in the first place.
turbinefi sees
Your runner has
Strategy English & spec
Yes
Yes
Generated Python
Yes
Yes
Kalshi API keys
No
Yes
Live positions and fillsSurfaced in Studio when you open the analytics tab
Yes
Yes
Account balance with Kalshi
No
Yes
Observability.
Turbine can surface live positions and fills in the Studio analytics panel. The runner is the source of truth.
Pause anywhere.
Turbine can stop the bot from any browser with one click. The runner stops accepting new trades immediately.
Survives turbinefi.
Even if the turbinefi control plane is offline, your runner keeps trading the most recent strategy you pushed.
Beta pricing
$99/ month
Seven days free. After that, $99 a month (limited time, reg. $199).
- BasicCloud sandboxes, your Kalshi keys, every supported venue. Sandbox compute billed at cost via X402 top-ups.
- $99/moLimited time. Reg. $199.
- ProFunds and serious quants. API access, multi-strategy, concierge support. Contact us.
- $299/mo
Is it safe to give turbinefi my Kalshi API keys?
Turbine never stores your Kalshi API keys. The keys are passed straight from the deploy wizard to your sandbox runner as environment variables, where they live for the runner's lifetime. We do not log them and they are not in our database.
Where is my turbinefi bot sandbox hosted?
Turbine provisions a runner for you on a third-party compute provider (Locus). The runner has its own URL, its own filesystem, and its own env vars. You top up the runner's compute budget via X402, an HTTP-native standard for agent payments.
What is X402 and why does turbinefi use it?
X402 is an HTTP-native standard for agent payments. Turbine uses it to top up your runner's compute balance with the provider, so the financial path between you and the compute is direct rather than running through turbinefi as a middleman.
Can I export my bot and run it outside turbinefi?
Yes. Every bot exposes its Python and its DSL spec. You can copy the Python and run it in your own infrastructure with your own Kalshi keys.
Who pays for sandbox compute on turbinefi?
You do. The compute provider charges your runner; Turbine tops the runner up via X402 from credits you buy. The turbinefi subscription covers the Studio. Compute is billed at cost.