Independent SAP BTP Architect
Builder-side SAP BTP architect and creator of the Boundary Model.
I provide contract-bound architectural verdicts when SAP BTP extensions fail after go-live — particularly when documentation appears aligned, yet runtime behavior diverges from design intent.
This is architectural judgment — not implementation.
Former platform engineer at SAP; worked across multitenancy, identity propagation, integration boundaries, and lifecycle orchestration on SAP BTP.
The Boundary Model emerged from repeated post–go-live failures observed from inside the platform layer.
Who this is for
This site is for architects, technical leads, and decision‑makers facing post–go‑live instability in SAP BTP extensions.
Typical pattern:
Documentation appears correct.
Ownership is unclear.
Behavior differs by tenant, entry path, or identity context.
The system is “technically correct” — yet fails in practice.
What I actually do
- Diagnose boundary failures across runtime context, identity propagation, tenant isolation, data ownership, integration jurisdiction, and lifecycle authority.
- Issue a written verdict: what must change vs what must not change.
- Re‑establish jurisdiction: who owns what, and where.
What these engagements are not
- These engagements do not replace implementation teams.
- They are not designed for ticket execution or staff augmentation.
- They are not generic consulting support.
You may need an independent verdict when…
- It works in one tenant and fails in another.
- It works in Postman but fails behind AppRouter or Work Zone.
- It degrades months after go‑live during rollout or organizational change.
- Remediation requires changing trust models, subdomains, destinations, roles, or tenant routing.
- Multiple teams are involved and no one clearly owns the boundary.
Start here
Enter at the right depth. For the canonical reference, read the Boundary Model. For patterns and cases, browse Insights.
Boundary Model
Canonical definition of six boundaries and why traditional reviews miss these failures.
Read the model →Insights
Selected essays on identity, data, integration, and lifecycle failures in SAP BTP.
Browse essays →Work with me
Contract‑bound architectural judgment. Fixed‑scope verdicts — not implementation. See formats and expectations.
Engagement formatsWhen to call me
If an independent architectural decision is required, send a concise one‑page summary. You will receive a structured assessment — not a sales process.