TRACE D-IT / DIGITAL INFRASTRUCTURE EVIDENCE

Review a technical case.
Integrate your records.
Deliver reports with sources.

We help support, platform and security teams turn infrastructure files into a review that can be checked. We can work on a case using existing profiles, adapt a source or automate delivery, within an agreed scope.

Problem
Scattered records, different formats and reviews that are difficult to continue.
Work
We define the question, check the sources and prepare the review or integration needed.
Result
A deliverable with facts, references and limits that another technician can check.

Assisted review · Custom adaptation · Optional automation
The application and each integration have their own development scope.The multisource framework is a technical development within TRACE D-IT.

THE PROCESS AT A GLANCE01—03
Your infrastructure
Your files
Your question
TRACE D-ITImport · Review · Preserve
PROFILE SPECIFIC
THE DELIVERABLEFacts. Sources.
Open questions.
HTML / JSON report
From a file to a review your team can continue.
Process diagram · Compatibility and scope agreed in advance.
Explore a technical example and its source
01

Every observation,
with its source.

02

A review
you can recover.

03

A report
that preserves context.

WHAT WE CAN WORK ON WITH YOUR COMPANY

Three specific engagements.
One shared foundation.

You can contact us without using Kubernetes. We first check which files you have and what TRACE can address today. Review, adaptation and automation are scoped and priced separately.

Find your starting point
01 / CASE REVIEW

Prepare an explanation another technician can continue.

You have files from an incident or review and need to separate facts from open questions.

Work and deliverables
What we do
We import compatible material, review its observations and relationships, and preserve the link to its source.
What you receive
A reviewed deliverable, HTML/JSON report and coverage limits. Case preservation follows the selected profile and agreed conditions.

Existing profilesCompatibility assessed before the engagement.

Discuss a review
02 / SOURCE ADAPTATION

Incorporate the records your infrastructure uses.

Your file format or the information you need to represent does not fit an available workflow.

Work and deliverables
What we do
We assess an authorised sample, define fields, identities and relationships, and develop the contracted importer or adaptation.
What you receive
An agreed integration scope, implementation and checks, with instructions, supported inputs and limitations.

Custom adaptationFeasibility and budget confirmed before development.

Discuss another source
03 / DELIVERY AUTOMATION

Connect the review to recurring work.

Your team repeatedly queries results or prepares deliverables and needs a defined workflow.

Work and deliverables
What we do
We scope queries and permissions, then connect a compatible path through an API or n8n workflows.
What you receive
The agreed workflow, configuration, operating guide and end-to-end checks. Access and support are defined for each environment.

Optional integrationExisting connections and extensions with their own scope.

See n8n status

We price a defined piece of work and deliverable. An available adapter does not establish compatibility with every format, general causal diagnosis or measured savings.

Conceptual scene of a technician reviewing documents alongside infrastructure equipment

THE TEAM'S PROBLEM

The next technician needs more than a screenshot.

CONCEPTUAL SCENE · REVIEW AND HANDOFF

A review changes hands. Files and conclusions exist, but reconstructing which data supports each statement can take work.

TRACE brings together observations from the received material, their provenance and their limits. The team can check what the file shows and decide what to investigate next.

01 / CHECK

Return to the original data

See the observation alongside the file, its source field and the received value. You can return to the data that supports it.

Output: observation with source
02 / CONTINUE

Resume a preserved case

The operator retains the case and can reopen the authorised workspace. The review can continue after a restart.

Output: recoverable review
03 / DELIVER

Explain what has been checked

Share the report and its limits. Another technician can read it and continue the investigation without automatically receiving the originals.

Output: HTML / JSON report
BENEFIT TO BE MEASURED

We aim to reduce manual preparation, handoff errors and repeated reviews. We do not yet claim time or financial savings: these must be measured against each team's current procedure.

A SHARED STRUCTURE

One common framework.
A scope for each source.

The engine provides a common structure for importing files, representing observations and preserving their provenance. It is applied through specific profiles: each source has its own formats, rules and limits.

  1. 01

    Scope

    A question, an authorised collection and the review scope.

  2. 02

    Organise

    Import the format and represent the received material while preserving its origin.

  3. 03

    Check

    Review observations, declared relationships and coverage.

  4. 04

    Preserve

    Retain results and integrity within the selected profile.

  5. 05

    Deliver

    Prepare a deliverable that explains the data and its limits.

A shared structure does not establish that two sources describe the same entity or have a common cause.

THE FRAMEWORK GOES BEYOND ONE EXAMPLE

Your systems.
Compatibility we check.

The foundation covers different infrastructure families. What we can deliver depends on the profile, version and available files. This directory distinguishes existing paths from integrations we still need to assess with you.

Explore the sources Open each family to see its status and scope.

KubernetesSpecific path

What exists

Factual review of JSON exports, with resources, declared reasons, owners and sources. TRACE Case is a local preview application.

How we would approach it

Check format and scope for a review. The available interface supports this profile only.

OpenTelemetryIndependent path

What exists

An OTLP JSON profile with spans, declared references, review and replay. The n8n integration has been checked separately.

How we would approach it

Agree the supported profile and operation. It is not automatically part of TRACE Case or the Kubernetes cloud operator.

Containers, virtualisation and cloudDocker · Proxmox · Host/VM · CloudAdaptation foundation

What exists

Framework profiles for Docker, Proxmox, host/VM and cloud, with historical synthetic conformance checks.

How we would approach it

Review a sample, version and fields. Connecting your infrastructure or the interface may require a contracted adaptation.

Identity, security and networkingIAM · SIEM/EDR · Network/DNS/FirewallAdaptation foundation

What exists

Profiles for IAM, SIEM/EDR-OCSF and network/DNS/firewall. Their contracts and limits are checked separately.

How we would approach it

Confirm which export is supported and which relationship is evidenced. Universal vendor or product compatibility is not promised.

Windows / EVTXSeparate technical track

What exists

Specific Windows evidence work, outside the TRACE Case interface.

How we would approach it

An individual assessment of the case and its files. This is not offered as an import already available in this application.

Profiles are not merged because they share names. A relationship across sources or a causal explanation requires evidence and checks compatible with that case.

TWO ENGINE EXAMPLES

Check the result.
Return to the source.

OUR OWN SYNTHETIC DATA

A guided exploration of actual engine outputs generated before publication. This website does not run the engine or receive your files.

Example exploration

Loading public examples…

WHAT EXISTS TODAY

What you can
evaluate today.

TRACE D-IT is our digital infrastructure line. The multisource framework is one of its technical foundations; TRACE Case is an application built on it. OpenTelemetry and n8n have their own paths. We distinguish what is available from development still pending.

Multisource framework

The shared foundation

Available today

Import, representation and provenance contracts for different technical profiles.

View scope and limits

Current scope

Nine adapters with historical synthetic conformance checks. Each source's readiness is verified separately.

TRACE Case

PREVIEW · Local application

Available today

Kubernetes import, review with sources, a recoverable workspace and an exportable report.

View scope and limits

Current scope

A preview for Linux / Python 3.12, one operator and a browser on the same computer. Visual review and execution without elevated privileges are still pending qualification.

OpenTelemetry

INDEPENDENT PATH

Available today

Import of supported OTLP spans, canonical evidence, review, replay and access through its own SDK/API.

View scope and limits

Current scope

A separate delivery. This profile is not yet part of the TRACE Case interface.

API and n8n

OPTIONAL INTEGRATION

Available today

Authorised query paths for Kubernetes and OTLP already checked with n8n.

View scope and limits

Current scope

Access and expiry conditions belong to each profile. The new Case application is not yet connected to those paths.

SOFTWARE DISTRIBUTION

TRACE Case is a source-code preview package for Linux/Python 3.12. No general installer has been published. Rights and notice review, use by an ordinary user and visual application checks remain open. Native Windows support and network collaboration require further development.

OFFER LIMIT

We do not establish an attack cause, propagation or enterprise resilience here. Report integrity does not authenticate the origin of the files.

ONE ENGINE, DIFFERENT WAYS TO USE IT

TRACE preserves the review logic. The local application, API and n8n are different ways of using specific paths; they do not automatically share every profile or permission.

n8n

INTEGRATION STATUS

The n8n connection
is already developed.

The integration lets the operator's workflows query TRACE paths. The local application does not depend on n8n. These are the evidenced states; a private connection is not presented as a public installation.

n8n × TRACEINTEGRATION DIAGRAM
Your workflowAuthorised query
TRACEAPI / HTTP Request
ResultCompatible profile
Integration developed · Operation depends on the profilePrivate connection. Catalog node pending.
Integration developed and tested

API and HTTP Request queries

Query workflows for Kubernetes and OTLP executed separately. Each profile retains its scope and access conditions.

Privately deployed

Kubernetes operator

A private operator deployment exists. That operator uses Kubernetes. The OTLP path remains separate.

Verification pending

The user's cloud workflow

Access from the user's computer, complete workflow execution in the cloud service and operational recovery have not yet been established.

Not yet available

A node installable from the catalog

The connection currently uses API and HTTP Request. Publishing and verifying a catalog node is a later step with its own completion requirements.

What has been checked and what is pending

Workflows were executed in n8n 2.45.7 for Kubernetes and OTLP separately. The private operator deployment contains Kubernetes. A published or verified public catalog node and the complete cloud path from the user's computer are not established here. Qualification of one version does not claim that it is the latest available.

If your team uses n8n

Tell us which task you repeat, which data it uses and what the next tool must receive. We assess the workflow and agree access, installation and support. The n8n editor is not offered here as a customer service.

Discuss automation

DOCUMENTATION TO TAKE AWAY

Understand the scope.
Explore the examples.

Read what we offer, what we need from your team, what is developed and what requires adaptation. The kit lets you compare synthetic inputs and reports without sending your company's information.

The PDF guide, kit documentation and instructions below are in Spanish. This page provides the offer, requirements, product status and collaboration information in English.

The kit contains documentation and examples; it is not a software installer. The TRACE Case source preview has its own requirements and distribution checks. Installation, adaptation or automation is agreed after compatibility has been assessed.

R&D COLLABORATION / TRACE D-IT

Seeking R&D partners.
For industrial IT/OT.

We are looking for companies to develop and assess TRACE D-IT applications for incident review in industrial IT/OT environments. The case, sources and capabilities to be built are agreed together.

WHAT WE BRING

The TRACE D-IT technical foundation

A multisource framework, evidence representation, file references and existing integrations, within each profile's scope.

WHAT WE ARE LOOKING FOR

Industrial knowledge and validation

Sector expertise, complementary technical development and an authorised environment where the use case can be assessed against agreed criteria.

We start from a specific need and define contributions, work, usage conditions and checks. General application to industrial IT/OT is a development and validation objective of this collaboration.

Propose a collaboration

BEFORE GETTING STARTED

Practical questions.

Does TRACE already explain why a system failed?

The paths shown identify declarations and relationships in the files and keep their limits visible. They do not turn an ERROR or Pending state into a root cause. A causal explanation requires a compatible case, evidence and a validated capability.

Do I need to send my records to this website?

No. The demonstration contains only public synthetic examples. The available application processes files selected locally. Authorisation, custody, scope and usage arrangements are agreed before working with real evidence.

Can the report transfer the entire case?

The report can be shared for reading and review. Its ZIP does not reimport a mutable workspace. Reopening applies to the operator's authorised workspace under each profile's conditions.

Do you only work with Kubernetes?

No. It is the first local application with a specific path. OpenTelemetry has another profile and the framework covers other infrastructure families. A new source or integration is assessed before an adaptation is agreed; we do not promise to support every file.

Do I need ChatGPT, an AI API or n8n?

The deterministic paths shown work without an AI API. n8n is an optional operator integration with its own requirements. TRACE Case uses its own local interface.

What does local mean for the current delivery?

TRACE Case is a preview for Linux and Python 3.12, with one operator and access from the same computer. The host is part of the trust model. It does not encrypt metadata or originals at rest and does not provide a boundary against the computer's administrator. Network collaboration requires further development and qualification.

How does this differ from my usual tools?

We propose the complete process of preparation, source-linked review, preservation and delivery. Savings compared with your tools or a simple procedure must be tested in your work. If the current procedure achieves the same result with less effort, that finding should be recorded.

PUBLIC SYNTHETIC FILE

Example input

Download input JSON ↓