Step 01
Website and checkout
The customer-facing layer is now focused on direct copy, cleaner navigation, working checkout, and clearer public pages.
Customer-facing release notes for tools, checkout, benchmark, news, entities, map access, and account features.
Shipping now
Customer updates.
The customer-facing layer is now focused on direct copy, cleaner navigation, working checkout, and clearer public pages.
Benchmark is moving from raw strategy output into tracked styles, preset models, historical import, and repeatable learning.
The next release lane is a sharper news stack built from exports, official APIs, and event tagging instead of filler headlines.
Get Access, login, and the private dashboard entry are now public-facing instead of buried in future plans.
Platform coverage
Tools, benchmark intelligence, macro/news desk, entity/map intelligence, and account access.
Catalog
Catalog, benchmark, news, entities, map, and account access now sit together.
Public desk
Release notes focus on customer-facing intelligence, not internal build activity.
Platform
Checkout, access, order history, and private surfaces belong in the customer workspace.
Public beta
BiasForge is in a controlled beta window. The official 1.0 launch is reserved for the stable platform release after feedback, data, and workflow validation.
Current build
Public beta with paid access, founding slots, customer accounts, journal beta, model terminal beta, news, map, and admin operations.
Beta window
Use the beta period for customer feedback, reliability work, better data coverage, cleaner UX, and stronger tool packs.
Official launch
Reserved for the full public launch after the core customer, admin, data, support, and checkout paths are stable.
Founding access
Qualifying purchases can unlock capped early access.
Offer size
First 1,000 users
Access window
6 months
Launch code
Configured at checkout
Early members receive beta access while journal, news, map, model, and entity features expand.
Launch note
This public beta offer is capped and tied to qualifying purchases before the official 1.0 launch.
Bundle purchases qualify immediately. Three distinct paid solo tools under one account or checkout email also qualify. The 1-day trial does not count.
Release status
A simple view of the current customer-facing release path.
Step 01
The customer-facing layer is now focused on direct copy, cleaner navigation, working checkout, and clearer public pages.
Step 02
Benchmark is moving from raw strategy output into tracked styles, preset models, historical import, and repeatable learning.
Step 03
The next release lane is a sharper news stack built from exports, official APIs, and event tagging instead of filler headlines.
Step 04
Get Access, login, and the private dashboard entry are now public-facing instead of buried in future plans.
Current stage
This section stays simple on purpose: what customers can use now and what is still being verified.
Current stage
Preset models, webhook learning, replay import, and style tracking are already live, but public benchmark boards are still being verified.
Goal
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
Right now the benchmark layer is about gathering cleaner trade history, keeping models separate, and only publishing boards once the data is solid.
Release notes
Each note explains what shipped on the public BiasForge surface and what changed for customers.
Snapshot BF-0.8.1a
Version v0.8.1
Published June 20, 2026
Updated June 20, 2026
Release note
Founding access now follows clear purchase rules, shows remaining availability at checkout, and stays positioned as beta access before 1.0.
Snapshot BF-0.8.0a
Version v0.8.0
Published June 20, 2026
Updated June 20, 2026
Release note
The beta launch offer was packaged around paid access, the first 1,000 eligible purchases, and a 6-month founding window.
Snapshot BF-0.7.0a
Version v0.7.0
Published June 19, 2026
Updated June 20, 2026
Release note
Model pages gained the first chart terminal surface for candles, indicators, model context, and future BiasForge tools.
Snapshot BF-0.6.0a
Version v0.6.0
Published June 18, 2026
Updated June 18, 2026
Release note
The journal beta now imports broker or platform history, saves reviews, and summarizes trade behavior before deeper model training.
Snapshot BF-0.5.0a
Version v0.5.0
Published June 14, 2026
Updated June 17, 2026
Release note
The customer dashboard moved into an app workspace with access, orders, library, store, models, news, map, and integrations.
Snapshot BF-0.4.0a
Version v0.4.0
Published June 3, 2026
Updated June 13, 2026
Release note
BiasForge added the first connected entity and market-map layer for companies, venues, sectors, routes, and global context.
Snapshot BF-0.3.0a
Version v0.3.0
Published May 26, 2026
Updated June 14, 2026
Release note
The macro desk moved from a small static window into a calendar-led beta with source proof, impact labels, and bias context.
Snapshot BF-0.2.0a
Version v0.2.0
Published April 28, 2026
Updated May 1, 2026
Release note
Admin moved into a focused operations workspace for orders, access, service health, traffic, and support posture.
Snapshot BF-0.1.0a
Version v0.1.0
Published April 21, 2026
Updated April 23, 2026
Release note
Verified customer accounts moved into the product surface with login, registration, recovery, and dashboard entry.
Version v0.0.7
Published April 7, 2026
Updated April 20, 2026
Release note
Paid checkout now connects orders, TradingView usernames, and customer order history in one flow.
Version v0.0.6
Published March 29, 2026
Updated May 26, 2026
Release note
BiasForge now has clearer navigation, tighter product pages, and a dedicated place for shipped updates.
Version v0.0.5
Published March 28, 2026
Updated June 3, 2026
Release note
Benchmark results are grouped by workflow so public scorecards stay easier to compare.
Snapshot BF-1.0.0
Version v1.0.0
Target After public beta
Updated Target: after beta validation
Release note
BiasForge 1.0 is reserved for the official launch after the beta improvement window, with stronger packs, broader data coverage, and a cleaner customer platform.