INSTITUTE FOR APPLIED AI & SOVEREIGN SYSTEMS SKÅNE, SWEDEN (EST. 2022) Latest Paper: The Reader Was Missing (Oct 2026) →
Lab Estate: Nominal (58ms · 11 peers)
13:03:40 CET
Bitware Labs Applied AI & Systems Research · Skåne

Bitware Labs / Engagement

How engagements work

The lab is one person, with 40+ years behind a screen. Not much work is taken on: if it does not interest me, I decline. What follows is how a job actually runs: private by default, then delivered.

Bitware Labs sovereign mesh and bare-metal cluster architecture blueprint.
Figure 1. Bitware Labs sovereign WireGuard mesh and bare-metal cluster architecture.
  1. 01Short brief
  2. 02Scope if interested
  3. 03Private work
  4. 04Delivery

Start here

Send a short brief, not a sales form

Same inbox as everything else, read by the person who would do the work. Replies within two working days. I do not take on much: if it does not interest me, or it is a poor fit, you hear that in the first reply.

  • What is broken, missing, or needs building
  • Where it runs today (cloud, own iron, mixed)
  • Whether you lean audit, build, or retainer
  • Timing and a rough budget if you have them
Open the contact form

henke@bitwarelabs.com

Engagement shapes

Scope

Most work is one of these, or an audit that turns into a build. Pick a shape to open the form with it preselected.

Technical schematic for Audit engagement

Audit

Quoted per engagement ask and you get a number, not a discovery call

A read of what you already have.

  • Infrastructure, security posture, or an AI system already in production
  • Written findings ranked by what actually bites first
  • Every finding reproduced before it is reported
  • Fix list you can hand to someone else, no lock-in
Start with this shape →
Technical schematic for Build engagement

Build

Quoted per engagement ask and you get a number, not a discovery call

The work itself, done by the person you wrote to.

  • Agents and memory systems, infrastructure, security, software
  • Handed over documented and runnable by one person
  • Your hardware where it should be, your accounts, your data
  • No subcontracting, no account manager in the middle
Start with this shape →
Technical schematic for Retainer engagement

Retainer

Quoted per engagement ask and you get a number, not a discovery call

Someone whose job it is when it breaks at 02:00.

  • Monitoring, patching, backup verification, incident response
  • Hosting on dedicated iron, built by hand
  • A standing block of hours for changes
  • Cancellable monthly, it should hold on merit
Start with this shape →

Rates depend on scope and on how much of the estate is already in a state worth building on. Describe the problem and you will get a figure back, not a questionnaire.

How it actually goes

Process
Step 01

You write, I answer

Not a form to a sales queue, the same inbox that gets everything else, read by the person who would do the work. Replies come within two working days, in English. If it is not something I should take, you will be told that in the first reply rather than the third meeting.

Step 02

Written scope, if it interests me

Only if the brief interests me. Then: what is being built, what is explicitly not, what I need from you, and what it costs. Short enough to read in one sitting. If the shape of the problem is still unclear, that is what an audit is for, and an audit is a fixed fee, so the uncertainty is mine rather than yours.

Step 03

Private work, then delivery

I do the work privately. No public progress pages, no open worklogs, no status theatre. You hear from me when there is something real to decide or when delivery is ready. Client work stays under NDA: I do not discuss clients publicly.

Step 04

Delivery that actually hands over

Documented, on your accounts, on your hardware, runnable by someone who is not me. The test is simple: could a competent engineer take this over without calling? If not, it is not finished. Retainers exist because people want them, not because the handover left a gap.

What delivery includes

Handover

When a build is done, it should run without me. The checklist is the same whether the job was an audit or a system.

  • Your accountsDomains, cloud, registrars and API keys in your name.
  • Runnable codeA repository you own, with instructions a peer can follow.
  • DocumentationHow to start it, watch it, back it up, and shut it down.
  • Live environmentStaging or production you can reach, not a demo on my machine.
  • Known limitsWhat is explicitly out of scope, written before the invoice.
  • Next stepOptional retainer, or a clean stop with no lock-in.

What to expect either way

Terms in plain words
  • i.
    No subcontracting The person you correspond with is the person who writes the code. Nothing is passed to an agency you never agreed to.
  • ii.
    Your accounts, your infrastructure Domains, servers, registrars and API keys in your name from the start. Nothing is held hostage by an offboarding process.
  • iii.
    Data stays where it should Local-first by default. If something must go to a third-party API, you are told which, why, and what leaves the building.
  • iv.
    Confidentiality as standard Private by default. Client work is not discussed publicly and is not written up here with names. An NDA is normal, not a special request.

Some work is better placed elsewhere.

Said early, so nobody spends time finding out slowly:

  • Windows work. Not taken.
  • Apple, iOS, and macOS client work. Not taken.
  • People-facing community or networking gigs. Product and engineering yes; schmoozing no.
  • Pure chat-UI or hype demos. Systems meant to survive production, not demo theatre.
  • Anything needing a big team. One person is the wrong answer if you really need four.
  • Public case studies naming clients. Not done. The lab shows its own work; clients stay private.
  • WordPress sites and plugin work. Not hosted here and not built here.

If it is one of these, say so in the first email and you will get a straight answer plus a pointer to someone who does it properly.

DEPARTMENT CORRESPONDENCE & INDUSTRIAL COMMISSIONS PGP KEY ID: 53C91896B657212C

Principal Investigator Office · Skåne, Sweden

Correspondence, Audits & Research Commissions

Inquiries regarding technical audits, autonomous agent architecture, sovereign infrastructure builds, or academic correspondence are read directly by the Principal Investigator. Please describe the system, where it operates, and the scope required. Replies are sent within two working days.

Direct correspondence: henke@bitwarelabs.com

Submit a Commission Brief Commission Terms & Scope PGP Public Key