On-premises systems

Your premises. Your organisation. On-site intelligence.

The system is created for the customer’s own premises. Design and implementation are led by Strangstad specialists. AI is used in that work as a controlled production method, so delivery stays consistent and documented. Commissioning is carried out on site. The organisation operates the system.

Request a briefing Platforms Aella

On-site intelligence, mobile communications, and the site ledger — on infrastructure you operate.

Linux hosts Rust services On-prem ready You operate it

How the work is carried out

Created for your site. Operated by your organisation.

The same on-premises system is supplied in one of two forms. After implementation, operation is arranged in one of two ways. In every case the system remains on infrastructure the customer operates.

A development project

The system is designed and built for the site, from the brief through commissioning. Scope and modules are agreed in writing. Accountability for what is delivered remains with Strangstad specialists.

A finished system

Modules that are already complete are adapted and integrated at the site. Saga, Aella, Stella, Skjal, Heim, Thala, Hermod, and Skarð are that library. The same commissioning and the same documentation apply.

Your specialist takes over

A specialist in the customer’s own organisation is trained on the system during implementation. At handover, that specialist operates it. The system, the data, and the keys remain with the organisation.

Or a service agreement

Where the organisation prefers it, Strangstad Tech continues after implementation under a service agreement (SLA). The scope of operation, and the response that is expected, are set in that agreement. The system still runs on the customer’s infrastructure.

How a site is delivered

From brief to production

A short brief is enough. Software is licensed once. Travel and hardware are quoted. The work is a development project or a finished system. After implementation, the site is operated by your specialist, or by Strangstad Tech under a service agreement.

  1. 1Brief

    Spaces, staff, and mail. A short brief is sufficient.

  2. 2Quotation

    Software is licensed once. Travel and hardware are quoted.

  3. 3Installation

    On your Linux systems. On-site delivery, or customer download.

  4. 4You operate

    The site remains yours. After implementation, your specialist operates it, or Strangstad Tech continues under a service agreement. Messaging is not analysed by us.

Operator consoles

Saga for the organisation. Stella on the office workstation. Skjal on the telephone.

Saga console
Saga
Stella GUI with Aella
Stella
Skjal chat
Skjal
Heim surveillance panel
Heim
Thala server monitoring
Thala
Skarð wallet
Skarð

The consoles as they run in production.

Site walkthrough →

Reference installation

We operate the same stack we deliver

Strangstad Tech — our own office, Norway

Strangstad Tech operates this stack at our office in Norway. Saga for the organisation. Aella at the workstation through Stella, and on mobile through Skjal. Heim monitors physical spaces. Thala monitors servers. We already operate mail, so Hermod is only for sites that do not. Skarð is in production.

Hours
Weekdays 08:00–15:00 Europe/Oslo
Place
Strangstad Tech — our own office, Norway

What runs here

  • Saga + Rune + Edda — the organisation
  • Aella in Stella at the desk, Skjal on the phone
  • Heim watches rooms
  • Thala watches servers
  • Mail we already run — Hermod is not installed here
  • Skarð is live
View the walkthrough Specify this site

Aella. Skjal. Skarð.

On-site intelligence, site communications, and the site ledger.

On-site intelligence
On-premises site intelligence

Aella

On-site intelligence for inference, memory, jobs, and workflows — installed on your infrastructure.

  • 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.
  • Aella mind · Stella operator console · optional paid Skjal path
Details →
Site communications
Mobile site communications

Skjal

End-to-end mobile communications between people. Aella can join a room as a paid add-on; that path is decrypted so she can reply, and is disclosed. Human-to-human rooms stay end-to-end.

  • Include Aella in conversations and existing groups
  • Designed for the telephone; Stella covers the office workstation
  • Aella mind · Stella operator console · optional paid Skjal path
Open Skjal →
Site ledger
Site ledger · SKAR / ð

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)
  • Self-hosted ledger · zero internal fees · SKAR and Flís
  • Zero internal transfer fees
Details →
Advisory at no charge

A brief is enough to begin.

Software licensed once

Travel and hardware are quoted separately.

Two installations

Saga · Rune · Edda · Aella · Stella · Skjal

Operates without the WAN

Designed to continue when the public network does not.

How a site is installed

Products are licensed in the groups in which they are installed.

Required together

Saga installation — supplied together

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

Required together

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.

Recommended · separate

Recommended — separate products

Not included in the Saga or Aella installation. Heim monitors physical spaces. Thala monitors servers. Specify them when the site requires those functions.

Platforms → · System →

Why this architecture

Public-cloud AI and SaaS keep inference, identity, and messaging on someone else’s infrastructure. When the link drops — or policy forbids the connection — those products stop.

We supply the opposite. Aella runs inference on your infrastructure. Operators reach her from Stella. Staff may add her to Skjal as a paid, disclosed path. Saga, Rune, and Edda operate the organisation without a public-cloud identity provider. Heim and Thala are separate products — physical spaces and servers — when specified. The system is created by Strangstad specialists. AI is used in the design and the build under their direction. It is commissioned on site, and the organisation operates it.

Machine roles

A full site uses specialized machines for org apps, AI, the operator desktop, fleet ops, and long-term storage. Smaller installs combine hardware; the product groups stay the same.

Org & webConsole

Saga, Rune, Edda, public web, and Skjal — the human entry surface for the site.

AI computeAella

Aella runtime: models, agents, jobs, and short-term operational memory for the AI product.

Operator edgeStella

Stella — the operator console for Aella. Not every desk.

Fleet opsThala

Thala server monitoring and remediation. Separate recommended product.

Memory & archiveStorage

Long-term media, backup archives, and durable knowledge stores for the site.

System →

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.