Pre-launch

Know where your organization relies on AI — and what to do when that changes.

Heisterlux is being built to show which AI your organization depends on, why that reliance was considered justified, and which decisions may be affected when something shifts. So the next step can be proportionate, not improvised.

Heisterlux is an independent project currently in development. The platform is not yet available for customer use.

From visibility to action

Heisterlux follows one line of reasoning, from knowing what is there to knowing what to do.

VisibilityRelianceChangeImpactActionVisibilityRelianceChangeImpactAction
  1. Visibility

    Which AI systems and AI-enabled services are in use, where, and through which access route.

  2. Reliance

    What the organization depends on them for, how critical that is, and why it was considered acceptable.

  3. Change

    What shifted: a model version, the terms of access, the application around it, or the way it is used.

  4. Impact

    Which applications, decisions and reliances a change may affect — and where the evidence is not enough to say.

  5. Action

    A suggested next step that fits the size of the change and the stakes of the reliance. People decide what to do.

Four distinctions, kept explicit

"We use AI for this" usually compresses several different things. Heisterlux is being built to keep these distinctions explicit, because each can change on its own.

Organizational use and relianceWhat we depend on it for, and whyrests onA concrete useFor example: drafting replies to complaintsdescribed byAI system or capabilityWhat produces the outputDeployment ContextHow access is obtainedApplication or serviceWhere the AI appears
The three descriptors are separate. None of them determines the others, and the relationships are not one-to-one.
  • AI system or capability

    The model or AI capability that produces the output.

  • Deployment Context

    How your organization obtains access to that capability — for example an organization-managed licence, a personal subscription or an API agreement. It describes the access route, not where the AI appears.

  • Application or service

    The product or service in which the AI capability appears or is available.

  • Organizational use and reliance

    What the organization depends on a concrete use for — a task or decision — and why that was considered acceptable.

How they relate

  • One AI capability can be available in several applications, and one application can offer several capabilities.
  • The same capability can be reached through different Deployment Contexts, with different terms and controls.
  • An organizational use points at the concrete combination that is actually used. It is not tied one-to-one to any single layer.
  • A change can touch any of them. Whether it matters depends on what the organization relies on — and that is for people to judge.

A host application such as a word processor, a meeting tool, a mail client or a design tool is where an AI capability appears. It is not how access to it is obtained, so it is not a Deployment Context.

Why this matters now

None of this is unusual. What is hard is knowing, when it happens, what it may touch.

Confidence is earned. Not generated.

Help shape the future of Heisterlux.

We're building Heisterlux in the open. Follow our progress, share your ideas, and help us understand what organizations really need from AI governance.