Join the Isla list

Thoughtfully built.

Join the list

Company

We build environments for ideas.

Garðr is a technology company focused on thoughtful, coherent computing — from small utilities to foundational systems.

What Garðr is

Products that earn their place.

Garðr builds software, systems and products that are meant to belong together. Some are small and exact. Some will be foundational. The ambition is the same at every scale: technology that feels considered, holds up over time and is plainly made with care.

We are not interested in more technology for its own sake. Progress is measured by whether what we make improves the place it lives in — a desktop, a phone, a workflow, a day.

Each product keeps its own identity. What connects them is a shared standard and a shared Core.

garðr

/ˈɡɑrðr/ · GAR-thr

The name

A place where things belong.

Origin
Old Norse — the same element preserved in Miðgarðr, or Midgard.
Meaning
An enclosure; a courtyard; a protected place; a world defined by its boundary.
Saying it
GAR-thr. The ð is the voiced “th” in this.
Writing it
Garðr, always — and gardr only where a system cannot carry the ð.

The symbol

The environment may change. The Core remains.

Two guards define a protected opening; a Core of light is held within it — raised, so it is guarded rather than resting on the ground.

  1. Core

    People · Ideas · Life

  2. Guard

    Protection · Security · Trust

  3. Gateway

    Access · Growth · New possibilities

  4. Garðr

    Thoughtfully built.

The Garðr symbol is composed of a Core (people, ideas, life), guards (protection, security, trust) and the gateway they form (access, growth, new possibilities).

What we hold to

Environment, protection, possibility — and craft.

  • Environment

    Products are conceived as parts of a coherent place, not isolated utilities.

  • Protection

    A bounded environment should feel dependable, private and respectful of the people in it.

  • Possibility

    The gateway is open: protection without confinement, structure without stagnation.

And beneath all three, craft

Interfaces, defaults and engineering decisions should feel considered rather than ornamental.