Fundamentals
Strategy as a Service Trading
Software became a service when distribution costs dropped to near zero. Before the cloud, software was sold on physical media — a disc, a license key, a one-time transfer of code from developer to buyer. After the cloud, the model inverted: you access behavior, not code. You pay for ongoing use. The developer keeps the IP, maintains the software, and earns recurring revenue. The buyer gets the capability without the infrastructure burden.
Algorithmic trading is undergoing the same structural shift. For most of its history, access to institutional-grade trading strategies required either building them yourself or handing your capital to someone who had. Both models are collapsing. The result is strategy as a service — a subscription model for algorithmic execution that separates the trading logic from the capital that runs it.
Why Strategy Access Has Always Been Gated
Quantitative trading strategies have existed since the 1970s. What made them exclusive was not the mathematics — it was the infrastructure cost and the distribution friction.
Running a systematic strategy required data feeds that cost thousands per month, execution infrastructure that assumed institutional API access, and legal structures (fund formation, prime brokerage relationships) that required minimum AUM in the eight figures to justify. Individual systematic traders existed, but the barrier to professional-quality execution was high enough to keep the category small.
The distribution problem was equally significant. A strategy creator had no clean way to share a validated approach with other investors without either selling the code outright (transferring the IP permanently) or forming a fund (taking on regulatory and operational complexity that most quant developers don't want). The middle ground — recurring, code-protected strategy access — didn't have a viable infrastructure layer.
So the market organized around three models: hedge funds for large-scale professional capital, prop trading for firm-employed quants, and retail speculation for everyone else. Serious systematic trading at retail scale was effectively an exception rather than a category.
What Strategy as a Service Means
Strategy as a service (SaaS trading) is a model in which algorithmic trading strategies are made available to investors on a subscription basis, with execution delivered through the investor's own brokerage account and the strategy's source code remaining with the creator.
Three components define the model:
Subscription access, not code transfer. The investor pays for the right to run the strategy — access to execution signals and the algorithm's behavior — not for ownership of the logic. The creator retains the IP. This is identical to how cloud software works: you use Figma, you don't own Figma's source code.
Investor-owned execution. The strategy executes against the investor's own brokerage account via API. No capital is transferred to the strategy creator or to the platform. The investor's Alpaca account remains in their name, at their brokerage, with their funds. The platform routes execution signals; it doesn't custody assets.
Creator-defined, investor-configured risk. The creator documents the strategy's risk profile — expected drawdown range, position sizing model, regime conditions, average hold time. The investor then configures their own parameters within those boundaries. Maximum loss per trade is set by the investor. Position size is investor-determined. The strategy executes within those limits.
This is the clean form of the model. Platforms that blur any of these three components — that take custody of capital, that transfer source code, or that give the investor no control over risk parameters — are running adjacent models (funds, licensing arrangements, signal services) that carry different characteristics and different risks.
How It Differs From a Fund
The comparison to a hedge fund is inevitable and worth making precise.
In a fund structure, the investor transfers capital to a manager who makes all execution decisions. The investor has no visibility into individual trades, no control over position sizing, no ability to exit a specific strategy without full redemption. The manager operates under an investment mandate, reports to LPs, and is subject to fund-level regulatory classification. The minimum investment is set by the fund, not the investor.
In a strategy as a service model, none of those conditions apply. The investor's capital never leaves their account. The investor sets the risk parameters. Execution follows the rules of the strategy, not the discretion of a fund manager. There is no LP relationship, no capital lockup, no redemption window. The investor can revoke API access and stop the strategy in real time.
The regulatory difference is significant. A fund manager exercises discretion over investor capital — a regulated activity. A strategy marketplace routes pre-defined algorithm signals to investor accounts — software execution. The distinction is the basis for different regulatory treatment, which is why platforms operating in this space are careful about what they are and are not doing with investor capital.
This also explains the Oyamori positioning: no fund custody, transparent execution, investor-controlled parameters. The model only works — both commercially and legally — if the capital separation is genuine.
What the Subscription Model Gets Right
The recurring revenue structure aligns the incentives between creator and investor better than either alternative.
Outright code sale misaligns incentives after the transaction closes. The creator has been paid; whether the strategy performs is no longer their problem. The investor bought something static that may degrade as market conditions change and has no ongoing relationship with the person who built it.
A fund misaligns incentives through fee structure. The standard "2 and 20" model charges management fees regardless of performance, creating a cushion that insulates the manager from underperformance. Investors in underperforming funds continue paying management fees while waiting for recovery.
A subscription model creates ongoing accountability. If a strategy stops performing, subscribers cancel. The creator earns only while the strategy delivers value. This is the alignment that subscription software achieves: the vendor is continuously incentivized to make the product worth keeping.
The model also makes sense for the creator's economics. A validated strategy with multi-year edge persistence is worth far more than a one-time licensing fee. Capturing a fraction of its value per month for the duration of its usefulness produces substantially better economics over time. See how this works in practice in how to monetize a trading algorithm.
The Oyamori Approach
Oyamori is the execution layer for the strategy as a service model. The platform exists to connect systematic strategy creators with investors who want to run validated algorithms without building them from scratch — and to do it in a structure where the capital separation is real, the edge documentation is required, and the investor controls their own risk parameters.
The catalog is the product. Not a fund. Not a managed account. A structured marketplace of validated algorithmic approaches, each with documented edge mechanics, configurable risk parameters, and execution via Alpaca's retail API. Investors choose what to run. Creators earn from what runs.
Strategy as a service is the model that emerges when distribution infrastructure catches up with strategy development capacity. That moment is now.