Local history draft · published observations · real health, accounts and installation are unmeasured.
By We Are TitansCustomer help & documentation

PUBLISHED RECORDS · SOURCE AND DATE

Published release history

A record of what was observed and reported. Current service health, account access and installation are measured separately.

01 / RELEASE HISTORY

Dated release records

Record unavailable
Recorded onNot available
Observation ageUnknown
Published sourceUnknown

Loading a dated published record. Current service health remains unmeasured.

Current health: Unmeasured · A fresh page load does not refresh an observation.

02 / AVAILABILITY

Downloads and installation

INSTALLER STATUS

Installation evidence

A serving record or digest does not establish a current installer or a successful customer workflow. Installation needs its own verified package and receipt.

Unavailable until package and receipt are verified.

LLM credits and Titan.SavantLLM

Atlas prices do not include LLM credits. Hosted model subscriptions or usage credits are separate.

Coming soon: Titan.SavantLLM (sLLM), our free local-first tier.

Atlas’s core stays the same. Atlas and Nessa work with the compatible LLMs you connect; the runtime adapts to the selected model.

Planned setup with sLLM:

  1. Evaluate your system and available memory.
  2. Recommend a compatible LLM to deploy locally.
  3. Automatically connect the chosen model to SavantLLM.
  4. Run initial guided learning rounds to prepare support memory for daily life: preferences and context, not training or fine-tuning model weights.
  5. Focus local AI on personal life, home, work, email and home automation, with the connections and permissions you enable.

Compact local models, especially those selected for a 16 GB memory budget, are the starting point for everyday assistance. For demanding production coding, we recommend a frontier-model subscription rather than relying on this local tier alone.

Availability depends on hardware and model qualification. Suitability for a task must be checked on the chosen model. Local inference runs on your computer; model downloads, email synchronization and some connected services may still require internet access. Cloud inference requires your explicit choice.