Lumivara

Service · Open-source companion

ABAP Enclave

A privacy-first AI toolkit for ABAP teams that runs entirely on your own hardware: a locally hosted open-weight model (via Ollama) wired into VS Code, plus a CLI of capability modules — so no ABAP source ever leaves your network (suitable for regulated and air-gapped landscapes) and there's no per-seat cloud-AI licence. Developers get context-aware help in their existing workflow, with abaplint enforcing Clean ABAP before anything reaches a transport. Delivered as modular workstreams scoped to your landscape, plus an open-source kit you keep.
zcl_order_status.clas.abap — VS Code
abap-enclave · local 
METHOD set_status.
  UPDATE zorders SET status = @iv_status
    WHERE order_id = @iv_id.
  rv_user = sy-uname.
ENDMETHOD.

abaplint: 2 Clean ABAP issues (direct write, sy-uname)

Continue
/gen-tests for set_status 
CLASS ltc_status DEFINITION FOR TESTING
  DURATION SHORT RISK LEVEL HARMLESS.
  METHODS updates_status_row FOR TESTING.
ENDCLASS.

Generated by the local model — no code left the network.

Continue wired to the local abap-enclave model, abaplint enforcing Clean ABAP — the prompt, the completion and your source all stay on your machine.

Book a call Get the open-source kit View source

Zero data egress

Your ABAP is your business logic. The model, the prompts, the completions and the source all stay on your network — nothing is sent to a third-party API. Viable in regulated and fully air-gapped SAP landscapes where cloud assistants are a non-starter.

No per-seat AI licence

Open-weight models run on hardware you already own, instead of a recurring per-developer cloud-AI subscription. Add developers without adding licence cost.

Clean ABAP, enforced in the editor

abaplint with a tuned ruleset flags Clean ABAP and Clean Core issues as developers type — and in CI — so problems are caught before they reach a transport.

Real uplift in the existing workflow

Context-aware help and a CLI of capability modules live alongside the VS Code your team already uses — no new SaaS, no context-switching.

The engagement

Composable workstreams, scoped to your landscape

Not a fixed-price SKU. The right model, hardware, ruleset and capabilities depend on your landscape, so ABAP Enclave is delivered as modular workstreams — take the ones you need.

1

Local LLM stand-up & model selection

We install and configure Ollama on your chosen hardware, then benchmark candidate open-weight code models for quality, latency and footprint on your stack — nothing leaves the network.

2

VS Code workspace setup (ABAPfs + Continue)

We wire VS Code to your on-prem ABAP through the ABAP remote filesystem extension and connect Continue to the local model — chat, inline edit and tab-autocomplete — telemetry off.

3

abaplint Clean ABAP ruleset tuning

We adapt the open-source abaplint ruleset to your team's standards and target ABAP release, so Clean ABAP is enforced consistently in the editor and in your pipeline.

4

CLI capability rollout & enablement

We configure the abap-enclave CLI to your landscape and bring your developers up to speed on the capability modules and the read-only-by-default workflow.

5

Ongoing tuning retainer

Optional

An optional, rolling engagement to refresh models as stronger open-weight ones ship, extend the ruleset, and keep the setup current as your landscape evolves.

Pricing is scoped per engagement rather than listed as a fixed number. Tell us about your landscape and we'll size it together.

The toolkit

One air-gapped CLI; capability modules plug in

The open-source kit ships a pip-installable abap-enclave CLI. A shared foundation (ADT + local-LLM clients) means the capability modules stay thin, consistent, and read-only by default.

Read-only

ATC Finding Triage

abap-enclave atc-triage

Pull ATC / Code Inspector findings and let the local model explain each one — root cause, S/4HANA simplification context, business impact — and propose a concrete Clean ABAP fix, grouped by remediation pattern. On-prem and zero-egress; suggestions are advisory and a developer applies the fix.

Read-only

Unit-Test Generation

abap-enclave gen-tests

Draft ABAP Unit test classes (AAA structure, test doubles via CL_ABAP_TESTDOUBLE) for your classes with the local model. Dry-run by default — tests are written to local files for review; writing back into the system is opt-in and double-gated. A developer reviews and runs the output before relying on it.

Read-only

Documentation & Legacy-Code Explainer

abap-enclave gen-docs

Crawl a package and let the local model summarize each object — purpose, processing flow, inputs/outputs, dependencies — into a browsable Markdown docs set. The fastest way to understand inherited or pre-migration code. Read-only by default; pushing ABAP Doc comments back into source is opt-in and gated. Summaries are model-generated — spot-check them.

Setup

Stand up the stack in one command

One idempotent bootstrapper (install.ps1 on Windows, install.sh on macOS / Linux) installs the editor stack in a fixed, logical order — online or fully air-gapped with --offline. Re-run any time; it skips what's already there.

  1. 1

    VS Code

    The editor — via winget / Homebrew / snap online, or a vendored package when air-gapped.

  2. 2

    Ollama + a code model

    A local LLM server on localhost, then the tuned abap-enclave model built from the Modelfile.

  3. 3

    Extensions

    Continue, the ABAP remote filesystem and abaplint — wired to the local model.

  4. 4

    Config

    Continue config, workspace settings and the abaplint ruleset, staged into your project (never overwritten without --force).

# Windows (primary)

.\install.ps1

# macOS / Linux

./install.sh

# air-gapped (install only from ./vendor)

.\install.ps1 -Offline

install.ps1

PS> .\install.ps1 -Workspace C:\git\my-abap

ABAP Enclave bootstrapper (Windows)

Mode: online | Model: qwen2.5-coder:7b

==> VS Code

[ ok ] VS Code installed.

==> Ollama

[ ok ] Ollama installed.

==> VS Code extensions

[ ok ] Continue.continue installed.

[ ok ] murbani.vscode-abap-remote-fs installed.

[ ok ] larshp.vscode-abaplint installed.

==> Model

Pulling 'qwen2.5-coder:7b' — resumes if interrupted...

[ ok ] Model 'abap-enclave' ready.

==> Config

[ ok ] Continue config → ~/.continue/config.json

[ ok ] settings.json → .vscode/settings.json

[ ok ] abaplint.jsonc → abaplint.jsonc

✓ ABAP Enclave stack is ready.

Open-source kit

The kit you keep

MIT-licensed and part of the ABAP & RAP Utilities. Runnable defaults the service tailors to your landscape.

install.ps1 / install.sh

Step 1 — the one-command bootstrapper for the editor stack (VS Code, Ollama + model, extensions, config). Online or air-gapped.

Modelfile

Step 2 — the Ollama Modelfile the installer uses to build the `abap-enclave` model with a Clean ABAP / Clean Core system prompt.

cli/

The pip-installable `abap-enclave` package — shared ADT + Ollama foundation and capability subcommands.

README.md

Setup, the zero-egress rationale, the CLI + config schema, and how the service tailors it.

Browse the kit on GitHub

How it fits Clean Core

ABAP Enclave complements the Clean Core assessment & modernization service: the assistant and its tuned abaplint ruleset keep new ABAP clean as your team modernizes, so the gains from remediation don't erode — all on your own network.

Bring private AI to your ABAP team

Book a call and we'll scope an ABAP Enclave engagement to your landscape — model selection, secure wiring, ruleset tuning and the CLI capabilities, with an open-source kit you keep.

Book an assessment Take the free audit