Portfolio Visualizer alternative: when to switch and when not to

Portfolio Visualizer is the reference tool for backtesting asset allocations, and if what you want to test is a set of weights, it does that job well and has for over a decade. People look for an alternative for a few specific reasons: they want to test a rule that is not on Portfolio Visualizer's menu, they want daily rather than monthly data, they want an API or an AI agent to drive it, or they want to avoid an annual subscription for occasional use. This page compares Portfolio Visualizer and ENSEMBLE on each of those points, states where Portfolio Visualizer remains the better choice, and dates every claim. Competitor facts were checked on September 3, 2026 against portfoliovisualizer.com/pricing.

What Portfolio Visualizer does well

It is worth being specific, because for these use cases you should keep using it.

• Breadth of analysis. Portfolio backtesting, Monte Carlo simulation, portfolio optimization with an efficient frontier, factor regression, asset correlation analysis, and fund research, all from one account. No other single tool in this category covers as much.
• Asset-class backtesting. The Backtest Asset Allocation module works at the asset-class level with data back to 1972 for US stocks and bonds, which is far longer than any ETF history allows.
• Tactical allocation models. A module for moving-average timing, momentum, dual momentum, target volatility, and market-valuation rules, chosen from a fixed menu with configurable parameters.
• Planning rules. Its withdrawal analysis carries tax treatment, required minimum distributions, and Social Security assumptions that ENSEMBLE simulations do not model yet.
• Maturity. The tool has been used by academics, advisers, and the Bogleheads community for years, and its outputs are widely understood.

Pricing and limits, as of September 2026

ENSEMBLE's pricing is on the pricing page and in machine-readable form at /pricing.md. Portfolio Visualizer's is at the link above; if it has changed since this page was updated, trust their page.

Where the tools differ

What you can express

Portfolio Visualizer is form-driven. You choose from the rules it has implemented and set their parameters. That covers fixed allocations completely and tactical strategies partially: dual momentum, moving-average timing, and target volatility are on the menu; a rule that combines them, or one that uses a lookback the form does not offer, or one that treats two sleeves differently, is not.

ENSEMBLE is description-driven. You write the rule in a sentence, and the platform writes the code. "60 percent SPY and 40 percent TLT, but move the SPY sleeve to BIL when SPY closes below its 200-day average, rebalanced monthly" is one sentence and one model. So is a risk parity sleeve with a trend filter on the bond position, or a momentum rotation with a volatility cap. If you can describe it completely, it can be tested. See how to backtest a portfolio for what a complete description contains.

The trade-off is that a menu is faster when the thing you want is on it. For a plain 60/40 backtest, Portfolio Visualizer's form takes fewer seconds than typing a sentence.

Data granularity

Portfolio Visualizer's Backtest Portfolio module uses monthly returns by default. ENSEMBLE uses daily closes for every backtest. For a fixed allocation the difference in compound return is small, but it matters for two things: maximum drawdown, which monthly data understates because the worst day rarely falls on a month end, and any rule that is evaluated more often than monthly, which monthly data cannot test at all.

ENSEMBLE's history is limited to the ETF era, roughly twenty years of daily data. Portfolio Visualizer's asset-class module reaches back to 1972 with monthly data. If your question is about the 1970s, use Portfolio Visualizer.

The implementation

Portfolio Visualizer returns results. ENSEMBLE returns results and the Python that produced them. For a fixed allocation this hardly matters. For a rule-based strategy it matters a great deal, because the way a tool handles the edge cases, such as what happens on the first rebalance date or what "monthly" means when the month ends on a weekend, determines the result, and with a form you cannot see those choices. The common mistakes guide covers why this matters. The code is also yours to keep: it downloads as a standalone script, and a risk parity or momentum rule on ENSEMBLE is your construction, written out in full, rather than a menu item whose internals you have to take on faith.

Composition

ENSEMBLE models hold assets, other models, or both, to any depth. A client model made of a fixed core and two tactical sleeves is one model with three components, each with its own tear sheet, and the platform computes the look-through holdings. Portfolio Visualizer backtests one portfolio at a time and does not compose them.

Sharing and persistence

Every ENSEMBLE model has a public tear sheet URL that anyone can open, an embeddable version, and a nightly rerun that keeps it current with the latest session. Portfolio Visualizer saves portfolios on paid plans and shares via links, but results are computed on demand rather than maintained.

Agents and automation

Portfolio Visualizer has no API, so nothing can drive it except a person in a browser. ENSEMBLE exposes every capability through a REST API and a hosted MCP server, which means Claude, Cursor, or a custom agent can build and read models directly. The AI agents section covers this in depth. If agent-driven research is part of your workflow, this is the decisive difference.

A live example

The card below is an ENSEMBLE model of the portfolio most people test first in either tool. The figures are computed from daily data, net of simulated costs, and refresh nightly; open the full tear sheet to see the equity curve against SPY, the drawdowns, and the generated code.

Choose Portfolio Visualizer if

• You want factor regression, efficient-frontier optimization, or withdrawal analysis with tax and Social Security rules built in.
• You need asset-class history back to the 1970s.
• You test many fixed allocations and want them side by side in one report.
• The tactical rule you want is on the menu and you do not need to modify it.
• You prefer a form to a sentence.

Choose ENSEMBLE if

• The strategy you want to test is a rule that is not on anyone's menu.
• You want daily data and the implementation, not just the result.
• You want to compose models out of other models and see the look-through.
• You want a public, shareable tear sheet that updates nightly.
• You want the current allocation as a file your custodian can import (Altruist, Interactive Brokers).
• You want an API, or you want an AI assistant to do the research.
• You would rather pay for what you use than for a year in advance.

Using both

Many people do. Portfolio Visualizer for planning analysis and long-history asset-class work; ENSEMBLE for rule-based strategies, composition, and agent workflows. The tools do not compete on most of the rows above, and the honest summary is that Portfolio Visualizer is the broader analytics suite and ENSEMBLE is the more expressive backtester.

Backtests are hypothetical, past performance does not guarantee future results, and ENSEMBLE is research software rather than an investment adviser. Portfolio Visualizer is a product of Silicon Cloud Technologies, LLC and is not affiliated with ENSEMBLE.