Live
Step 01
Website and checkout
The customer-facing layer is now focused on direct copy, cleaner navigation, working checkout, and clearer public pages.
Release notes / Release history / Product status
BiasForge Beta / public build
Customer notes, not vague release hype.
This page is the public BiasForge release log. It keeps shipped changes, customer-facing fixes, and in-progress product lines in one place so people can see what changed and what is still being verified before it is pushed harder.
Current focus
What is actively being tightened right now.
Website and checkout
The customer-facing layer is now focused on direct copy, cleaner navigation, working checkout, and clearer public pages.
Benchmark and training
Benchmark is moving from raw strategy output into tracked styles, preset models, historical import, and repeatable learning.
News and event flow
The next release lane is a sharper news stack built from exports, official APIs, and event tagging instead of filler headlines.
Access and dashboard
Get Access, login, and the private dashboard entry are now public-facing instead of buried in future plans.
Roadmap line
What is live, what is still being verified, and what is next.
The roadmap stays here so customers can see the real order of work instead of reading polished copy and guessing what is actually available.
Live
Step 02
Benchmark and training
Benchmark is moving from raw strategy output into tracked styles, preset models, historical import, and repeatable learning.
Building
Step 03
News and event flow
The next release lane is a sharper news stack built from exports, official APIs, and event tagging instead of filler headlines.
Building
Step 04
Access and dashboard
Get Access, login, and the private dashboard entry are now public-facing instead of buried in future plans.
Current stage
Current product state, kept explicit.
This section stays simple on purpose: current stage, current goal, and where the benchmark layer is right now before public boards and deeper private research are opened wider.
Current stage
Public build
Preset models, webhook learning, replay import, and style tracking are already live, but public benchmark boards are still being verified.
Goal
Rank what actually works
The target is to compare presets, sides, and styles by market and timeframe instead of judging the whole stack as one vague result.
Where we are now
Collecting and cleaning
Right now the benchmark layer is about gathering cleaner trade history, keeping models separate, and only publishing boards once the data is solid.
Customer Notes
What changed for customers.
Each note explains what was changed, what is included in the release, and what customers should actually expect from it.
Buildingv0.7.0
Next build
News desk, access, and dashboard layer
Release note
The next customer-facing build bridges into the private research layer: cleaner news collection, clearer access handling, and the first useful dashboard surfaces.
Release scope
4 included2 customer notes
Forex Factory calendar export ingestion is being prepared as the first macro-events feed.
X, TradingView, Binance, and Bybit collection lanes are being staged into one news stack.
Livev0.6.0
March 29, 2026
Site refresh and release notes
Release note
The public site, navigation, favicon handling, and release-notes flow were tightened in one pass so BiasForge reads more like a real product.
Release scope
4 included2 customer notes
Homepage and shop copy were cut down and made more product-specific.
A dedicated public updates page replaced scattered roadmap copy.
Livev0.5.0
March 28, 2026
Benchmark training and preset tracking are live
Release note
BiasForge can now collect benchmark events, retrain from stored data, import trade history, and compare styles by preset instead of one blurred result.
Release scope
4 included2 customer notes
TradingView benchmark webhook collection is running on the VPS.
Models are separated by preset so workflows stay clean.
Livev0.4.0
March 28, 2026
Checkout overlay and handoff were cleaned up
Release note
The checkout flow now feels more native to BiasForge. TradingView usernames are captured before payment and the overlay path is cleaner.
Release scope
4 included2 customer notes
TradingView username capture is now part of the checkout path.
The checkout overlay issue was fixed through the checkout subdomain split.