From GitHub issue to SAP transport — governed end to end.
GitHub is the control plane. Cleverpath is the orchestrator. Your S/4HANA system stays the system of record. Here is every step a change takes.
Seven steps, three control gates
A functional user opens a GitHub issue
No developer required to start. A guided issue template captures the business need in plain language — the report, workflow, value help, or custom field you've been waiting on.
Cleverpath receives the webhook and creates a branch
The orchestrator picks up the issue instantly, creates a dedicated branch, and dispatches the right AI worker for the job — Claude Code or Codex.
The AI worker generates the change
CDS views, RAP behavior, services, annotations, and unit tests — generated against your system's real metadata via our custom MCP server.
Tests run in a sandbox client Control gate
Unit tests, abaplint, and ATC checks run before any human spends a minute on review. Failures go back to the worker, not to your team.
A senior developer reviews the PR Control gate
A human expert — ours or yours — reviews the code, the tests, and the checks. Nothing merges without explicit senior approval. This gate is mandatory and cannot be bypassed.
On merge, abapGit pulls the code and a transport is created
The merge is the trigger. Code lands in your DEV system via abapGit and a standard SAP transport is created — the same release process you run today.
Every action is logged and attributable Control gate
Who asked, what was generated, who reviewed, what shipped — the full chain is recorded, exportable, and ready for your auditors.
The orchestration flow
-
GitHub Issue
Functional user creates an issue from a template
-
Orchestrator
Webhook received, branch created, AI worker dispatched
-
AI Worker
Code, tests, and artifacts generated
-
PR + Review
Senior engineer reviews before merge
-
abapGit + Transport
Code pulled, transport created on merge
-
SAP S/4HANA
Deployed to DEV via standard transports
The technical stack we bring
GitHub
The control plane — issues, branches, reviews, and merges drive everything.
Cleverpath orchestrator
Receives webhooks, manages branches, and dispatches AI workers.
Claude Code & Codex
The AI workers that generate code, tests, and artifacts.
Tailscale
Private, zero-trust connectivity into your DEV landscape.
GCP Cloud Run
Default orchestrator runtime — or run it in your own cloud or VPC.
abaplint + ATC
Static checks and SAP's own quality gates on every change.
LiteLLM gateway
One controlled gateway for all model traffic — observable and swappable.
Custom MCP server
Gives AI workers safe, structured access to your SAP metadata.
Standard SAP transports
Changes move through the release process you already trust.
What stays in your hands
Your GitHub org holds the code. Your SAP system stays the system of record. Your reviewers approve every merge. The pipeline accelerates your process — it never replaces your authority over it.
See it live
Book a fit call and we'll walk the pipeline on a real example from your backlog.