FredAI
One consumer assistant brand using appropriate models and modes for different tasks.
PLANNED EXPERIENCETHE FIRST PUBLIC DOSSIER / 001
FredAI is being designed as more than a single conversational model. Today we're opening the first public look at its proposed model families, platform structure and computing options.
Public design disclosure. This is not a claim that the models are trained, benchmarked or available.
DISCLOSURE 01 / THE LINEUP
One name cannot cover every workload. The proposed FredAI range has eight permanent core family names, with the separate Bit (Paced) family below Ember. Select a core family for its currently disclosed status.
Family numbers above identify the eight permanent core families; they are not a capability ranking. Ember starts the core lineup and Apex is its highest-tier concept. Roles for the other six core families remain unannounced.
Before Ember: Bit (Paced). Bit is a separate, smaller entry family planned for local Instant-only everyday assistance, balanced with extra emphasis on speed. “Paced” means infrequent major updates after initial release. Bit 1 remains in development; no trained weights, measured speed or release availability are being claimed.
DISCLOSURE 02 / THE PLATFORM
FredAI is intended to be the name of both the wider AI platform and its consumer-facing assistant experience. The diagram shows the proposed product organisation, not deployed infrastructure.
One consumer assistant brand using appropriate models and modes for different tasks.
PLANNED EXPERIENCECloud-powered services within FredAI products where a local model is not sufficient or not selected.
PROPOSED SERVICEA proposed external route for developers to access FredAI cloud models and services.
PROPOSED SERVICEDISCLOSURE 03 / ACCESS
Different devices and workloads need different deployment choices. These are the directions being explored rather than services promised at launch.
Free local model distribution is a design goal. Supported hardware, licences and actual model releases are not yet announced.
Cloud access is intended for workloads that need remote computing. Usage-based API pricing is envisioned, but no rates have been committed.
Lightweight instant-style modes and additional specialised experiences are part of the vision. SuperFred and UltraFred are proposed overlays.
DISCLOSURE 04 / WHAT REMAINS PRIVATE
We can share direction without pretending development is finished. These details are deliberately not announced in November.
NEXT / THE CHRISTMAS PROGRAMME