Skip to content
NORKÄRŸM

NORKÄRŸM

A small software studio from Catalonia.

What NORKÄRŸM is

NORKÄRŸM (also written NORKARYM, without accents) is a small software studio from Catalonia.

We design, build and maintain our own digital products: a platform for organisations, a desktop app, a local AI engine, a predictive mushroom map and an online course.

It is run by its two co-founders, Adrià and Dani.

What we build, and where each product stands

KÄRŸ

In beta. Not in production yet; no paying customers.

A multi-tenant platform for businesses and the self-employed. Each organisation gets its own space with roles and permissions, an audit log of critical changes, and a hub of apps it can install. It runs on a staging environment today. It will go to production in phases: team and shifts first, then bookings, then the public website, then invoicing.

KÄRŸ Desktop

Public builds for Windows, macOS and Linux. It works with KÄRŸ, which is in beta.

The desktop app for KÄRŸ, built with Electron. It opens KÄRŸ and runs IkärÿA on your own computer. You can reach it from your phone through a relay designed to be blind: it passes encrypted traffic and is built so it cannot read it.

IkärÿA

Part of KÄRŸ, which is in beta.

The local-first AI of KÄRŸ. The engine is designed to run on your computer with local models and never to call models on the internet. Two principles: "the forge compiles, the local engine runs", and "the code decides, the model reasons": no critical decision is left to a model.

Bolet OS

In a testing phase (beta) at boletos.cat (in Catalan).

A predictive map of wild mushrooms in Catalonia. It combines forest, terrain, soil and weather data to estimate where and when mushrooms come up.

boletos.cat

Curs: Build apps with AI, from zero

Online at curs.norkarym.com (in Catalan).

A six-session online course for absolute beginners. Students go from "I don't know what happens inside an app" to building and publishing their own web apps with the help of AI, without knowing how to code. Its motto: "Ask for it and understand it; don't do it by hand."

curs.norkarym.com

KAMA (working name)

In exploration.

It aims to be a place where people and AI agents work together on creative digital projects.

The apps in KÄRŸ

KÄRŸ is for businesses and the self-employed. Each organisation installs, from its hub, only the apps it needs. KÄRŸ is in beta and goes to production in phases: team and shifts first, then bookings, then the public website, and invoicing last. The apps below are in development.

Team and time

  • Team: shifts, who is in today, and a mailbox for payslips.
  • Bookings: bookings and occupancy.
  • Calendar: appointments and the organisation's calendar.
  • Chat: messages inside the organisation.

Sales and stock

  • Orders: customer orders, with shipping.
  • Catalogue: the services and products you offer.
  • Inventory: what you have in stock.
  • Purchasing: orders to suppliers.
  • Payments: getting paid by customers.

Online and with others

  • Public address and website: each organisation gets its own address and public web page.
  • Network between organisations: organisations that work together can connect.
  • WhatsApp channel: to talk with customers on WhatsApp.
  • Electronic signature: to sign documents.

At the desk

  • Mascot: with voice dictation.
  • Desktop mode: a way of working in KÄRŸ as on a computer desktop.

Future

Economy and finance

We are preparing invoicing for VeriFactu, Spain's new system for verifiable invoices. It is not available yet.

Month-end closing, taxes and the depreciation of assets are also in preparation.

How we build: crew coding with Claude Code

We call it crew coding. It is not "vibe coding". A person directs a crew of Claude Code agents. Each agent has a role, its work is reviewed by other agents, and everyone follows written rules. People make every decision that matters.

Read the full article: Crew coding with Claude Code →

The crew

On one workstation, more than twenty Claude Code sessions work at the same time. Each one owns a lane: an app, a module or a repository. Each works in its own git worktree and its own range of ports, so sessions never step on each other's files or on the people's running environment.

A few sessions do not build product. They coordinate, and each one is named after its role. None of them governs: they watch, warn, route work, or carry out what a person decided.

Dashboard
what is waiting for the person, and releases to production
Messages
between sessions, and the person's decisions to whoever must act on them
Tax and legal
questions taken to the person in charge and to our advisers
Security
secrets, permissions, dependencies and audits
Screens
the visual line: reviews every screen change
Tests
failing CI, test gates and click-through tests on staging
Tools
for the agents: hooks, scripts and skills
Machine
memory, disk, ports and cost
Upkeep
whatever nobody is waiting for: forgotten work and weekly cleanup
Releases
versions

The rules that make it reliable

  1. The first rule: do not make things up. An agent that is not sure asks whoever knows. "I don't know" is a good answer.
  2. Plan before code. A new feature, screen or permission starts with a short written plan. The screen, security and legal reviewers read it at the same time, before any code exists.
  3. Every merge into our products needs a person's yes.
  4. Heavy work (installs, builds, test suites, screenshots) goes through a shared queue, so the machine does not choke.
  5. Every message between agents uses one format (INFO, QUESTION or BLOCKER) and is signed, so a person can always tell who said what.
  6. Lessons learned are written down where every agent can read them.

The forge

An internal console that builds apps with agents under human supervision.

A real example: this website

This page was rebuilt by a new Claude Code session. It first wrote a plan in an issue. The legal reviewer checked the legal notice, the screen reviewer checked the layout, and the security reviewer checked what would become public. Another session checked every fact against its source. A co-founder made the decisions from a phone.

Several machines, one way of working

The crew does not live on a single computer.

  • Each co-founder's computer has its own crew of agents, with the same roles.
  • A separate testing machine runs its own testing agent.
  • Agents on different machines never talk to each other directly. They write in a GitHub issue, and every message is signed with who sent it and from which machine.
  • People make the decisions from their phones.
  • KÄRŸ Desktop already has remote access: one shared computer can serve several people, and it is designed so that none of them sees what the others are doing.

It works: it has been tested with two people on two devices.

The coordination app

A desktop app with a dashboard that keeps people and agents in step. It tells each person what is waiting for them, with a recommended option, and sends alerts to their phone. It tells agents when to compact their context, and puts sessions to sleep and wakes them up to save memory. A chat view is being built.

GitHub

GitHub holds it all together: plans in issues, reviews in pull requests, lessons in a shared issue, and the common memory between machines. The rules are in the crew section.

Company details

NORKÄRŸM is the trade name of a sole trader (autònom) in Spain.

Legal notice

Contact

Write to us through the contact page. Contact page (in Catalan and Spanish)

Dani, co-founder, on LinkedIn