Security & Operations

Every change traceable. Every access governed.

This page answers the questions your IT department will ask — before they ask them.

Governance instead of sprawl

The entire configuration lives versioned in Git:

  • Every change is a commit — with author, timestamp and diff
  • Approvals through review workflows — no unreviewed state goes live
  • Controlled rollouts — per environment and tenant, with version pinning

Identity & permissions

  • Central sign-in via OpenID Connect (Keycloak)
  • Roles and groups managed centrally, effective down to individual operations
  • Screen lock on inactivity — platform-wide, cannot be disabled, work state is preserved

Open interfaces, no lock-in

  • Typed OData APIs for all data
  • Machine-readable metadata contract ($metadata)
  • Optimistic locking via ETags — conflicts are resolved in a merge dialog instead of silent overwrites

Multi-tenant, isolated

  • Clear hierarchy: tenant → environment → instance
  • Full isolation between tenants
  • Automated onboarding — and residue-free deletion

Operating models

Technically the same platform (Kubernetes):

  • Hosted — operations, updates and availability included
  • On-premises — data sovereignty and local autonomy in your own data center

Support & responsibility

A clear responsibility matrix instead of ticket ping-pong:

  • Platform maintenance — operations, availability, updates, security: with the platform operator
  • Application maintenance — configuration, processes, user support: with your integration partner or team
  • One contact for your report — the cause is routed to where it gets solved

See for yourself.