Workflow Builder
Workflows are created using natural language and made accessible with parameters.
- Triggerable manually or time-based
- Multiple assets can be combined in one process
A new category of controlled AI automation for IT support.
The nordnung platform combines tickets, agents, workflow orchestration, credential control, and knowledge logic into one platform. In this form there is currently no direct product equivalent: four execution agents and two interaction agents resolve support cases quickly without losing governance, hosting in Germany, or GDPR compliance.
Product preview
Workflow across multiple levels
Hosted in Germany
A workflow can include multiple assets, such as Endpoint, Critical Systems, and VM Agent.
Onboarding example: AD user, M365 license, MFP address book and desktop setup in one flow.
Trigger: manual or time-based, such as nightly update checks.
Call with mandatory parameters such as first name, last name, email, groups and target system.
Platform model
What the nordnung platform brings together as a complete product
Not a loose collection of individual scripts, but a continuous process from initial contact to documented resolution.
01
From ticket to reliable execution
The nordnung Agent routes requests into a controlled execution path. This reduces manual handovers and keeps decisions traceable.
02
Agents work with clear boundaries
Each agent has clear scope, endpoints and approval logic. Automation stays productive without becoming an uncontrolled black box.
03
Knowledge logic instead of individual case thinking
Solved sessions are documented and made reusable. Quality improves over time instead of starting from zero on every ticket.
Modules
The central functional areas
The focus is on concrete product modules that are directly understandable for IT management and operations.
Tickets and intake
Inputs are classified early and transferred to appropriate agent paths.
- Suitable for L1 and L2 close cases
- Clear transitions instead of ad hoc support
Assets and applications
Assets, applications and methods are managed separately and connected in a controlled manner.
- Application = URL, path, portal or endpoint
- Methods can be customized for each application
Credential Management
Access data are independent objects with technical access control.
- HashiCorp Vault + AES-256 + hardware encryption
- Injection only on released assets
Knowledge base
Incidents are documented in a structured manner and prioritized depending on the context for new sessions.
- Recent incidents have higher priority
- Relevance is determined by time and context
Customizing
In addition to standards, individual processes and legacy flows can also be mapped.
- Own methods and integrations possible
- Product logic remains controlled
Inside
A look inside the platform
Real views from the nordnung.ai console — from the dashboard to tickets, credentials and the Microsoft 365 integration.
Dashboard
Usage, costs and open items at a glance: free minutes, resolved tickets and the status of all endpoints — traceable per month.
All views are taken from our demo environment with test devices and demo accounts.
Agent model
Six agents with clear roles
Two interaction agents stay close to the user. Four execution agents execute defined actions in technical environments.
Phone Agent
Vision Agent
Endpoint Agent
VM Agent
Critical Systems Agent
Cloud Agent
Credential Security
Credentials are stored in HashiCorp Vault with AES-256 and hardware encryption. Plain text remains outside the LLM context.
Leak notice
If a password appears in chat or screenshot, the nordnung Agent marks the incident and indicates that it has been compromised.
Knowledge Base
Sessions are documented in a versioned manner. Recent incidents are prioritized, older ones are given lower weight depending on the context.
Assets and applications
A workflow can serve the infrastructure across the board
The data model deliberately separates assets, applications, and credentials. This keeps control over which agent can execute which method in which context.
Assets are all devices with the nordnung Agent installed.
Applications describe destinations such as web portals, installation paths or SSH endpoints.
Credentials are independent units and are assigned to applications or assets.
The LLM does not receive any plaintext credentials, but only controls the injection endpoint.
Getting started in practice
Sales receive clear product evidence
The page intentionally shows concrete functional logic instead of abstract claims. This lets you connect demos, pilots, and later product visuals without rework.
Operational relief instead of a demo show
Recurring cases are depicted in a reproducible manner and are not improvised anew each time.
Safety as an operating principle
Scope, approvals and traceability are part of the workflow, not downstream compliance decoration.
Built for real enterprise environments
The platform is geared towards real support stacks, releases and mature system landscapes.
Directly pilotable
The described modules are structured so they can be validated clearly in a guided pilot.