We make the complicated simple.

We use Artificial Intelligence as a lever on every process. Most of it goes into our own projects. The rest goes to companies that want help making the same shift: away from SaaS, toward custom-built tools they own outright.

Founded
2019
Based in
Karlsruhe
Working on
Infrastructure, Intelligence, Innovation
The visible spectrum  / 01
Vision  /  where this is going

The pure SaaS model is ending.

Artificial Intelligence has made custom software cheap: cheap to build, and cheap to own. Most of the industry has not noticed. We have, and we have built around it.

We use Artificial Intelligence as a lever on every process. One-time work. One-time price.

What we care about.

Artificial Intelligence is our lever on every process. These principles guide us when we use it.

01 / Focus

Every complicated problem has a small core.

We find it, build around it, and stop. Artificial Intelligence speeds up the search, it does not replace it.

02 / Lever

Artificial Intelligence on every process.

We use it everywhere we work. What used to take months now takes days. On request, we show you how to use it the same way.

03 / Ownership

What we build, the customer owns.

One-time work. One-time price. No subscription, no lock-in. Maintenance and operations by us are possible, never required.

04 / Direct

No middlemen. We work directly.

Direct contact with the people who need the work done. No account managers, no procurement theatre, no handoffs.

FAQ  /  What we hear most

Common questions.

When should a company run its own Kubernetes cluster?

Once several production services with distinct scaling or availability needs run in parallel, or when data sovereignty requires EU-based infrastructure. Below that, simpler platforms like individual VMs or managed PaaS are usually enough.

How do you install MicroK8s on a single-node Ubuntu server?

Install snapd, then snap install microk8s --classic, enable the DNS, hostpath-storage and ingress add-ons, install the Longhorn prerequisites (open-iscsi, cryptsetup) and copy the kubeconfig to the local machine. Full step-by-step guide: MicroK8s installation part 1 – server setup.

How do you get automatic TLS certificates on MicroK8s?

Install Cert-Manager, create a Let's Encrypt ClusterIssuer, and request the certificate per Ingress resource. The ingress-nginx controller resolves the HTTP-01 challenge automatically; renewal then runs without manual intervention. Step-by-step: MicroK8s installation part 2 – Cert-Manager, Longhorn, and encrypted storage.

How do you set up encrypted storage with Longhorn on MicroK8s?

Install Longhorn, create a LUKS secret with a strong password, and define a dedicated StorageClass with encrypted: "true". Set this StorageClass as default so new PVCs are encrypted automatically. Full kubectl sequence: MicroK8s installation part 2 – Cert-Manager, Longhorn, and encrypted storage.

Why do pods with Longhorn volumes stay in ContainerCreating?

In nine out of ten cases, KUBELET_ROOT_DIR is set incorrectly. MicroK8s places kubelet under /var/snap/microk8s/common/var/lib/kubelet, not under the default path. Debugging steps and checklist: Troubleshooting Longhorn volume mount issues on MicroK8s.

Can Artificial Intelligence be used in a GDPR-compliant way?

Yes, when it runs on-premises or in a private cloud and sensitive data never leaves the organisation. Enterprise LLM servers on your own hardware or in certified EU data centres are the common route.

Do you deploy AI agents for clients?

Yes. AI agents take over tasks that used to run manually or through rigid automation: structured extraction, rule-based decisions, data flow with checks. We build them embedded into existing software, not as isolated demos. When an agent earns its place, it stays; when it does not, it goes.

Can VBA macros be migrated to modern Office Add-ins?

Yes, via the Office.js API for Word, Excel, PowerPoint, and Outlook. The new add-ins run identically on desktop, web, and mobile; VSTO covers cases the JavaScript surface does not yet address.

Who owns the code after a custom software project?

The client, when the contract says so. For custom-built projects, full handover of source code and documentation is the norm; subscription models typically keep the software with the provider.