What is Grand Thera?

Why Grand Thera exists

Most enterprise systems can show what happened. Fewer systems can tell decision makers what changed, why it matters, and what should happen next. Grand Thera is designed for decision-critical environments where fragmented information, uncertain signals, and delayed execution create measurable financial risk.

The goal is not another dashboard layer. The goal is a reliable operating layer for direction: one that turns data into interpretable signals, connects those signals to agents, and supports action with traceable context.

Core products

Grand Thera's public positioning is organized around a decision-grade ecosystem. The following concepts are safe to reference publicly and provide the vocabulary for this documentation.

Open Engineering vs Closed Production

Grand Thera can publish open engineering artifacts while keeping product implementation closed. This separation keeps the public surface useful for developers, investors, and partners without leaking the systems that create the company's operational edge.

Decision-critical use cases

The ecosystem is built for teams that operate with fragmented data, high uncertainty, and real business consequences. Public examples should describe outcomes and architecture patterns, not private implementation details.

Architecture pattern

The public architecture can be described as a decision loop. Each layer has a clear role, and production details can stay abstract while the engineering intent remains understandable.

Deployment posture

Public material should keep deployment claims precise. Grand Thera describes TheraOS as deployable within client infrastructure, with critical data and decision workflows kept under client control. The docs should avoid exposing topology, credentials, data schemas, private integration contracts, or production diagrams.

Getting started

Use the public surface to understand the ecosystem, inspect the open engineering material, and explore the API documentation entry point.

Open Engineering

Open Engineering is the public surface for Grand Thera's demonstration APIs, dashboards, and inspectable engineering artifacts. These examples are intentionally transparent: they show how the analytical layer behaves without releasing closed production systems.

const response = await fetch(
  "https://api.thera-os.com/open-engineering/regimes/analyze",
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      prices: [100.0, 101.0, 102.2, 103.1, 104.4],
      window: 5,
      n_regimes: "auto",
      auto_method: "bic"
    })
  }
);

const result = await response.json();
console.log(result.latest_regime, result.transition_matrix);

const response = await fetch(
  "https://api.thera-os.com/open-engineering/neural-sde/forecast",
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      series: [100.0, 101.0, null, 102.5, 103.2],
      steps: 100,
      simulations: 1000,
      targets: [112.0, 116.0, 120.0]
    })
  }
);

const result = await response.json();
console.log(result.forecast_mean, result.target_probabilities);

const response = await fetch(
  "https://api.thera-os.com/open-engineering/symbolic/fit",
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      target: "margin",
      features: ["price", "volume", "volatility"],
      maxTerms: 6,
      selectionCriterion: "bic"
    })
  }
);

const model = await response.json();
console.log(model.formula, model.metrics);

git clone https://github.com/grandthera/AIT-Simple_RegimeDetection.git
cd AIT-Simple_RegimeDetection
python -m venv .venv
pip install -e .
python examples/neural_sde_forecast_demo.py

The generated HTML dashboards can be opened locally or through the public demo links above and used as inspectable examples of modeling assumptions, uncertainty visualization, and engineering care.

Resources