AI agent environments

Realistic, resettable environments to test and train AI agents

An AI agent environment is a realistic copy of the systems an agent works in, with masked or synthetic data, the business context it needs and the same starting point for every run. We build them from your own SAP, CRM, documents and messages, so you can test, train and compare agents before they touch live systems.

For AI and platform teams, agent builders, SIs and AI labs.

TDM for SAP is on SAP StoreRuns on-premises, in private cloud or hybrid
environment · invoice-dispute-07baseline saved
SAPCustomer 0001004521 · Kestrel Foods GmbH
Open item 90031877 · €12,480.00
CRMAccount Kestrel Foods GmbH
Case 00012931 · Invoice dispute · Open
Inbox"Invoice 90031877 is wrong"
From accounts@kestrel-foods.example
DocumentsInvoice_90031877.pdf
€12,480.00 · matches the SAP record
Synthetic customer. The same IDs and values in every system.
Same customer in every system
Same start for every run
Built for agents
Data the agent can act on, run after run
  • Happy path, exception, failure and adversarial scenarios
  • No real people in prompts, logs or traces
Works alongside the agent stack you already have
SAP JouleYour own agentsUiPathTricentis ToscaAny evaluation frameworkREST and CI/CD

Availability

What you can use today, and what's still in early access

Available today
  • Test Data Agent
    Builds the environment from a business scenario
    Request access
  • TDM for SAP
    Masking, subsetting and generation for SAP and connected systems
  • Masked agent test systems
    A masked baseline for Joule or your own agents, reset through the API
    SAP AI agent testing
  • 48-hour proof for documents
    50 of your own documents, masked, for a fixed fee credited when you go ahead
    Get a proof
Early access and engineer-led
  • SAP RL environments
    Scored, resettable SAP tasks for training agents
    Apply
  • Messages and documents at scale
    Emails, chats and PDFs that match your records, engineer-led today
    Learn more

Why environments

Evals check the answer. Environments check the decision.

An evaluation tool tells you whether an agent's answer looks right. An environment tells you whether its actions are right: it gives the agent real business context to act on, a known correct outcome, and the same starting state every time.

AgentModel, prompts, tools and memory
SAP JouleYour own agentsAny framework
EnvironmentSynthesizedData, system state, scenarios and a reset point
Masked baselineScenariosExpected outcomesReset point
Your systemsWhere the agent will act in production
SAPCRMService deskInboxDocuments
Alongside
Evaluation and observability

Reads the traces and the end state, then scores each run: did the agent take the right action?

Your eval toolTracingRed team
Where an environment sits in the AI agent stack. Your evaluation tool scores the run; the environment is what the agent runs in.
01
Agents change what they touch
A posted document leaves the system in a new state. The next run needs the old one back.
02
They cross systems
One task can touch SAP, a CRM, an inbox and a PDF. The data has to agree across all of them.
03
They need business context
Open items, credit limits and approval rules decide the right action. Clean fixtures don't have them.
04
Real data leaks
Whatever an agent reads can end up in prompts, traces, logs and model weights.

What you can do

One environment, three jobs

The same environment follows an agent from first prototype to every later release.

Test

Test before every release

Validate agents on realistic scenarios, then rerun the same suite before you promote a new version.

Train

Train on work that's safe to learn from

Resettable environments with scored tasks for reinforcement learning, fine-tuning and model comparisons.

Protect

Keep real data out of AI

Mask and synthesize the documents, prompts and traces that agents and LLMs see, from the first prototype on.

Test Data AgentGenerally available

Describe the scenario. The Test Data Agent builds the environment.

It works out which records and system states a test needs, then generates, masks or subsets production-representative data, with referential integrity and business rules intact.

  • Maps the entities, records and states a test needs
  • Builds happy-path, exception, failure and adversarial scenarios
  • Refreshes environments as applications and data change
  • Triggered from REST APIs and CI/CD pipelines
  • Runs inside your boundary, under your existing controls
Test Data Agent
Scenario
A customer disputes an invoice. The agent may issue a partial credit memo, but only within its approval limit.
Environment ready
  • Customer with three open invoices in SAP
  • Approval limit set for the agent's user
  • Matching CRM account and open case
  • Edge case: a dispute above the limit
  • Baseline saved for the next run
Illustrative. Emails, chats and PDFs can be added alongside; today that part is engineer-led.

Compare

How to test AI agents: four approaches compared

Most teams start with one of the first three. Each solves part of the problem; an environment is built to solve all of it.

ApproachReal business contextConsistent across systemsSame start every runNo real personal dataKnown right answerRuns in CI/CD
Copy of productionYesYesPartlyNoNoNo
Hand-written fixturesNoPartlyYesYesYesYes
LLM-written test dataPartlyNoPartlyYesNoPartly
AI agent environmentYesYesYesYesYesYes
Why not a copy of production?
It puts real customers into prompts, traces and logs, and you can't know the right answer for every record in it.
Why not hand-written fixtures?
They're too clean. No typos, missing attachments or contradictions, so agents pass tests they'd fail in production.
Why not let an LLM write it?
Generated text can mention accounts that don't exist, so the test measures failed lookups instead of agent judgment.

Evaluation frameworks aren't in the table because they don't supply data: they score runs on whichever of these you put underneath.

Results

Built on a platform enterprises already run

Agent environments use the same masking, subsetting and generation engine our customers rely on for test data today.

80%less time to provision test dataDeutsche Bank · via API in CI/CD
20bn+rows maskedHealthTech company
0security waivers across 14 priority applicationsSpecialty insurer

Glossary

Key terms in agent testing

AI agent environment
A realistic, resettable copy of the systems an agent works in, with masked or synthetic data, business context and scenarios.
Masked baseline
Production-like data with personal data replaced consistently, used as the starting point for every run.
Reset point
The saved state an environment returns to before each run, so results from different runs can be compared. SAP baselines are restored through the API; other systems are rebuilt from the same configuration.
Scenario
A business task, the data it needs and the outcome the agent should reach, such as posting an invoice with a price variance.
Expected outcome
The correct result of a scenario, known in advance. It can be an action, a refusal or an escalation.
Adversarial scenario
A scenario built to trick the agent, such as a hidden instruction in a PDF or a fraudulent bank-detail change.
Cross-system consistency
The same customers, IDs and amounts in every system, message and document an agent reads.
RL environment
An environment where an agent's actions are scored automatically and repeated many times, so it can learn from the results.

We've got you covered

Questions about AI agent environments

What is an AI agent environment?

A realistic copy of the systems an agent works in: masked or synthetic records, the business context around them and the documents and messages that refer to them, with a reset point so every run starts from the same state.

How do you test an AI agent before production?

Give it a realistic environment, a set of scenarios with known right answers, and a reset before every run. Run the scenarios, score the outcomes with your evaluation tool, add adversarial cases, then rerun the same suite before every release.

Why not test agents on a copy of production?

A copy puts real personal data into prompts, traces and logs, and resetting a full copy between runs is slow and expensive, so runs rarely start from the same place.

What can we use today?

The Test Data Agent and TDM for SAP are generally available. Masked SAP test systems for agents, with reset through the API, and the 48-hour proof for documents are available today; emails, chats and PDFs are delivered engineer-led. SAP RL environments are in early access.

How is this different from an evaluation framework?

Evaluation frameworks measure how an agent performs. The environment is what it performs in: the data, system states and scenarios. It works alongside whichever evaluation tool you already use.

Which systems can it cover?

SAP first, with particular depth in finance, procurement and supply chain. The platform also covers Salesforce, Oracle, Workday, Microsoft D365, ServiceNow and the major databases, plus emails, chats and PDFs that match the same records, delivered engineer-led today.

Does production data leave our environment?

No. It runs on-premises, in private cloud or hybrid, under your existing identity, network, security and governance controls.

Can we use it in CI/CD?

Yes. Provisioning is triggered through REST APIs and CI/CD pipelines, so every release can rerun the same scenario suite. See regression testing for agents.

Next step

Give your agents a realistic world to work in

We build one environment for a process you choose, run your agent in it and show a reset between two runs.

Production data stays inside your boundaryWorks with any agent frameworkNo real people in prompts or logs
Updated October 2026

SAP, S/4HANA, Joule and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Other names may be trademarks of their respective owners.