Locus Deployments

Turbine partnered with Locus (YCF25) to give each Studio user an independent server for strategy execution. The result is a deployment flow that feels simple in the browser while preserving a permissionless execution model.

What Locus provides

Locus provides the compute environment where a user's runner lives. The runner is the place where the approved strategy evaluates markets, reads the configured data sources, and submits venue actions using the user's credentials.

From the user's perspective:

  • Studio builds the strategy,
  • Studio helps backtest the strategy,
  • Studio deploys the strategy,
  • Locus hosts the user's independent runner,
  • the runner executes the strategy.

Why independent runners matter

Independent runners keep live execution separated by user and strategy.

This is useful because:

  • users do not need to share a single pooled trading process,
  • live credentials can be scoped to the user's runner,
  • strategy updates are isolated,
  • runner state is easier to reason about,
  • failures are easier to contain,
  • users can stop or revise their own deployment.

The product should feel easy, but the boundary matters: Turbine Studio is the build and control surface; the runner is the execution surface.

Deployment lifecycle

  1. Provision

    Studio creates a runner for the user when needed.

  2. Configure

    The runner receives the strategy artifact, environment, and required credentials.

  3. Start

    The runner begins evaluating the strategy loop.

  4. Observe

    Studio surfaces status, logs, and execution information from the runner.

  5. Update

    A revised Studio strategy can be deployed to the runner.

  6. Stop

    The user can stop a strategy when the thesis breaks, limits are reached, or they want to revise behavior.

Credential boundary

Venue credentials should be treated as live trading secrets. The intended model is:

  • the user supplies the credentials needed for their strategy,
  • credentials are passed to the user's runner,
  • credentials are not a Turbine-owned trading account,
  • credentials should not be exposed in docs, logs, prompts, or screenshots,
  • users remain responsible for the permissions and safety of their venue accounts.

AI agents should never ask a user to paste credentials into a public prompt or doc. Use the Studio credential flow.

Permissionless execution

The deployment flow is designed so a user can run strategies without asking Turbine to manually operate a bot for them. The user approves the strategy, provides credentials, deploys to their runner, and can stop or revise the deployment.

This does not remove trading risk. It changes who controls execution.

What these docs intentionally omit

These docs do not describe private deployment internals, runner implementation details, or Turbine's control-plane architecture. AI agents do not need that information to use Studio safely.

The public model is enough:

  • Studio drafts and tests strategies.
  • Locus hosts independent runners.
  • Runners execute the approved strategy with user-scoped configuration.
  • Users monitor and control the deployment.