Grouped the way they install

Platforms & modules

Grouped the way they install. Saga with Rune and Edda. Aella is the mind; Stella is the operator console. Skjal is human E2E chat. Heim and Thala are separate recommended products. Skarð is the live site ledger.

Linux hosts Rust services On-prem ready You operate it

Saga installation — supplied together

A Saga installation includes Rune and Edda: the organisation console, device sign-in, and the Saga database as one stack.

S-BASE

Saga Organisation console

Saga is where the organisation runs. Installing Saga means installing Rune and Edda with it — console, device sign-in, and database as one stack.

  • Documents, vault, meetings, incidents, and projects
  • Suite launchers for connected applications
  • Shop, catalogue, and commercial operations
  • Always with Rune (device sign-in) and Edda (Saga database)

On-prem console · ships with Rune and Edda

Shop →

S-RUNE

Rune Device identity & suite SSO

Rune is the trusted-workstation sign-in that ships with Saga. A small agent on the PC proves the device; suite apps then open as the same person.

  • Device key on the workstation you already trust
  • One-click sign-in to Saga, Stella, Thala, and Skarð
  • Skjal uses the same Rune/callsign proof — it is not a suite OIDC tab
  • Email OTP via Hermod remains the fallback when a PC has no agent

Ed25519 device proofs · suite SSO · required with Saga and Edda

Software →

S-EDDA

Edda Saga database

Edda is Saga’s Postgres. Users, modules, vault, documents, shop products, and site configuration live here. It is not optional and it is not a separate product you skip.

  • Canonical store for Saga users, modules, and vault
  • Shop catalogue and commercial records
  • Site configuration the rest of the suite reads
  • Stella keeps its own catalog DB when the Aella install is present

Postgres · required with Saga and Rune

Email login needs a mail server. Install Hermod, or point Site Identity at a mail server you already run. Rune on the workstation does not need mail.

Aella installation — supplied together

Aella is the mind. Stella is the operator console. Skjal is human E2E; Aella-in-Skjal is a paid add-on.

AI

A-CORE

Aella On-site intelligence

Aella runs on the site’s AI servers. Operators access it from the Stella workstation console and from Skjal on mobile devices, including existing conversations and groups.

  • Inference — Depth, memory, and job execution on the local network — context from your systems, not a public service.
  • Access — Workstation access through Stella. Mobile access through Skjal. Direct messages and existing groups.
  • Operations — Jobs, workflows, and approvals on site. APIs and agents for work that should not wait on a conversation.
  • Customer sites have no public widget. This site’s demo chat is schedule-limited and talks to our reference Aella at Strangstad Tech — not your production instance. Models and memory on a customer site stay on that site unless you connect an external service.

Aella is the on-site mind. Stella is the operator console. Skjal is human chat; Aella-in-Skjal is a paid add-on and is plaintext to her.

Details →
Aella on Stella GUI Office desktop

A-STELLA

Stella Operator console for Aella

Stella is the office workstation console for Aella. Operators open it from the suite and work conversations, jobs, and workflows on a full screen.

  • Aella on the operator workstation
  • Jobs, workflows, vitals, and media
  • Suite sign-in from Saga with the same Rune session
  • Operator console — not required on every staff desk

Rust console · suite sign-in · office desktop · required with Aella and Skjal

System →
Mobile

K-SKJAL

Skjal Mobile site communications

Skjal is the mobile communications client for the site. When Aella is installed, staff can include it in a conversation. It is also human-to-human end-to-end messaging.

  • Include Aella in conversations and existing groups
  • Human-to-human E2E (1:1 and groups)
  • Designed for the telephone; Stella covers the office workstation
  • Self-hosted · logout purge · Rune/callsign login (not a suite OIDC tab)

Rust relay · browser E2E · mobile-first · required with Aella and Stella

Details →

Skarð — site ledger

Live sovereign ledger for the site. Spend Flís in the shop; hold Skarð (ð) as whole coins.

Ledger live

Skarð Site ledger · SKAR / ð

Skarð (ð) is the self-hosted sovereign ledger for your site — named for the Nordic word for a shard, a piece that could be broken from an armring. 1 000 Flís make a shard; 1 000 shards make a Ring (visual scale only). Spend Flís on merch today; operate the ledger yourself.

  • Spend Flís on merch in the public shop (live)
  • Hold and spend SKAR/Flís at published suite rates
  • Holding benefits and consulting spend at published rates
  • Self-hosted ledger · zero internal fees · SKAR and Flís

Rust ledger · Skarð/Flís · own Incus container · Stella treasury · Saga shop

Details → Shop →

Roadmap

Core products in production. Further fleet and integration work is scheduled.

Planned

Factory multi-core

Site manifest provision across five cores — one install story from base Saga to full Aella stack.

In production

Skarð

Site ledger in production: treasury, shop purchase and spend, consulting redemption — published rate and utility.

Planned

Thala + Cortex packs

Deeper monitoring, backup RPO policies, and heal defaults per SKU for customer fleets.

Planned

Skjal suite link

First-class launcher from Saga; optional high-assurance profile factory inject.