Skip to main content
NewEU-hosted ITSM + CMDB, now in early access

The ITSM and CMDB platform built for European IT teams.

Run incidents, changes, assets, and service requests on one EU-hosted platform. Turn on DORA, NIS-2, BAIT, or GDPR controls only when you need them — nothing regulatory gets in your way until you ask for it.

Hosted in the EU (Hetzner)Schema-per-tenant isolationHash-chained audit log
Service Desk

Incidents

New incident
SLA at-riskReview
2
On your queue
My open
8
Assigned to you
Unassigned
3
Need a triage owner
DORA / NIS-2Reportable
1
Major or significant
All
IDTitleState
INC-0105
Server srv-app-03 nicht erreichbar
Monitoring · Infrastruktur
Resolved
INC-0127
VPN-Verbindung bricht ständig ab
Marcel Walter · Netzwerk
New
INC-0099
SAP-Anmeldung nicht möglich
Julian Krause · SAP
In progress
INC-0137
Zertifikat *.acme.de läuft ab
Monitoring · Infrastruktur
Assigned
INC-0026
Outlook synchronisiert nicht
Robin Vogel · Software
On hold
INC-0078
Exchange-Postfach über Quota
Robin Vogel · Software
Resolved

Connected to the stack European IT already runs

Microsoft 365DatadogPagerDutyMicrosoft SentinelIntuneSlackMicrosoft TeamsEntra IDJiraOktaGrafanaZabbixMicrosoft 365DatadogPagerDutyMicrosoft SentinelIntuneSlackMicrosoft TeamsEntra IDJiraOktaGrafanaZabbix
The problem

Most ITSM tools were built somewhere else, for someone else.

Teams in Europe end up paying for one of two things: a heavyweight platform priced and shaped for large enterprises, or a lightweight helpdesk that has no real CMDB and no answer when a regulation lands on your desk. Either way, data residency is an afterthought, and compliance means bolting on a separate product or a spreadsheet.

TENSORstarts from the other end. The service desk and CMDB are the product. EU hosting is the default. And the regulatory work — when it comes — is already in the platform, waiting to be switched on.

The shared record model

One graph — from the first alert to the last CI.

Link a change to the service it touches, see which assets a problem affects, and trace impact across the estate. The service desk and the CMDB aren’t two products stitched together — they read and write the same records.

Impact · outgoing dependencies7 CIs
BS-014CheckoutTier 1
SVC-021Payments APICritical function
CI-1043checkout-svcIn use
CI-0308srv-app-03In use2 CVE
CI-0311pg-primary-euIn use
SUP-004Stripe Payments EU
CI-0290api-gateway-euIn useEoL in 3 mo
Compliance you switch on

Turn it on. Not bolt it on.

Enable a regime and its controls appear on the record. Disable everything and you’re left with a clean ITSM — no compliance field an unregulated team will ever see.

Incident record3 controls
Summary
Priority
Assignee
Major-incident classificationDORA
ICT third-party registerDORA
Recovery time objectiveDORA
The audit chain

Evidence auditors trust, because the log can’t quietly change.

Every business-relevant change writes one record that commits the previous record’s hash. A verifier checks the chain daily and cold-exports it to object-locked EU storage. Tampering breaks the math, visibly.

Audit logChain verified · hourly
TimeEventHash
09:41:02Alert — p99 latency > 800 ms on api-gateway-eu9e2f…a7
09:43:10Acknowledged · raised to P1c4b1…3d
09:44:55CHG-118 approved · segregation-of-duties verified7f3a…9e
09:52:31CI pg-primary-eu modifieda1d8…02
10:00:00Chain re-verified · cold-exported to EU object-lockb2e0…5c
each record commits the previous record’s hash — altering one breaks the chain
How it works

Live in 3 steps

1

Pick your bundle

A short wizard asks what you're subject to — or whether you're subject to nothing — and provisions from one of four presets: Financial EU, Critical Infrastructure, EU SMB, or fully custom.

2

Bring in your estate

Import configuration items, connect your tools (Microsoft 365, Datadog, PagerDuty, Intune, and more), and route tickets to the right teams.

3

Run your operation

Work incidents and changes, watch SLAs, and produce regulatory reports on demand — if and when you need them.

Common questions

Answers before you ask

On EU infrastructure, with EU-resident sub-processors listed publicly. Data residency is a default, not an upgrade.
No. The regulatory capabilities are priced as something you add when you need them. An unregulated team runs on Core and never sees a compliance field.
Yes. The CMDB reconciles configuration items from multiple source systems — deduping and merging duplicates — and the integration framework, plus inbound email and webhook intake, connects the tools you already run.
Not yet. At this stage we run guided walkthroughs and a design-partner program rather than self-serve trials. Book a demo and we’ll show you the platform on a setup that matches your situation.

See TENSOR on your own estate.

Book a walkthrough and we'll show you the service desk, the CMDB, and — if it's relevant to you — the compliance toggles, mapped to the regulations you actually answer to.