Skip to main content
A strategy provider creates reusable investment strategies that one or more applications can offer to users. You can distribute a strategy through your own application, allow partners to distribute it, or make it available through Glider’s front end. A strategy does not hold user funds. Each enrolled user gets a separate portfolio with chain-bound smart accounts. The portfolio follows the strategy’s allocation, schedule, and execution settings.

​
What a strategy provider manages

The strategyId is the stable identifier for the strategy. It does not change when you update metadata, publish an allocation version, or change the schedule.

​
How the roles fit together

  • Strategy provider: Owns the source strategy and its ongoing updates.
  • Strategy distributor: Surfaces the strategy in an application and manages user enrollment.
  • Glider: Creates user portfolios and smart accounts, then executes the strategy for each enrolled portfolio using the smart account session key permissions.
One company can be both the strategy provider and the distributor. For example, you can create a private strategy and enroll users from your own application.

​
Choose how to distribute the strategy

Strategies are private by default. A private strategy can be used by your own tenant and surfaced to your users through the Two-Stage Enrollment flow. Set isPublic to true when you want other distributors and Glider to enroll users on your behalf. Give each distributor the stable strategyId. The distributor uses its own Glider API key to read the strategy and enroll users. Public status does not guarantee placement in Glider’s curated or top-performing collections. Glider manages curated placement, and top-performing placement depends on live strategy analytics.

​
Understand how updates work

The B2B API separates updates by intent: Publishing a new allocation version does not create a new strategy. The new version becomes active for the strategy, and enrolled portfolios use its target allocation during their next rebalance. Previous versions remain available in the version history. Setting isPublic to false stops new cross-tenant distribution. It does not delete portfolios that users already created from the strategy.

​
Manage the strategy over time

The provider remains responsible for the source strategy after distribution:
  1. Read the current strategy and version history.
  2. Validate the complete replacement allocation before publishing it.
  3. Communicate material allocation or schedule changes to distributors.
  4. Publish one new allocation version.
  5. Monitor strategy performance and enrolled portfolio behavior.
Keep the API key on a trusted backend. Use the Glider Console to get access and manage B2B API keys.

​
Next steps