BrainDesk MT
In productionIT service management and governance
One platform for the service desk and the governance work that hangs off it — ticket, asset, change and knowledge management today, regulatory reporting and security operations as it grows.
Why BrainDesk MT exists
Most organisations run their service desk in one tool, their asset inventory in a spreadsheet, and their compliance evidence in a folder someone assembles the week before an audit. BrainDesk MT is built on the premise that these are the same data seen from different angles: a ticket touches an asset, an asset sits under a control, a control needs evidence, and the evidence is the ticket.
The service management, asset and knowledge modules are in production and in daily use. The rest — procurement, regulatory reporting, security operations, and the governance modules around them — are being built on the same foundation. This page lists exactly which is which.
In operation
What is running today
The precise scope of its use right now — not what it could do.
- Service management, assets and CMDB, knowledge base and projects in production and in daily use
- Inventory agents enrolled and reporting from endpoints and servers
- Single sign-on, email-to-ticket and REST API integrations live
Modules
In production today
Built, deployed and in daily use — and what each one is there to do.
Service Management
In production- Service Catalog
- What people can ask IT for, and what to expect when they do — so a request is a defined thing rather than a favour.
- Tickets
- Where a request or an incident lands, gets an owner, and is tracked until it is actually closed.
- Changes
- Planned modifications with approval and a record, so anything that breaks is traceable to a decision someone made.
- Releases
- Groups the changes that ship together, so a deployment is one reviewed event instead of several unrelated ones.
- Problems
- The cause underneath repeated incidents — fixed once, rather than reopened every week under a new number.
Assets & CMDB
In production- Assets
- What you own, where it is, who holds it, and when it falls out of support — collected by the agents, not by a survey.
- CMDB
- How assets and services depend on each other: the map you want before a change, not during the outage after it.
- Licenses
- What you bought against what is actually installed. The gap is either money wasted or an audit finding waiting.
Knowledge Base
In productionAnswers written down once, so the second person with the same problem finds it instead of opening the same ticket.
Projects
In productionWork too big to be a ticket, tracked next to the tickets and assets it touches rather than in a separate tool.
Roadmap
Being built on the same foundation
What each one is for, so you can judge whether this is going where you need it to. No dates until we can stand behind them.
Procurement
In development- Purchase Requests
- Someone needs something bought, with the approval trail attached from the first click rather than reconstructed later.
- Purchase Orders
- The committed order, linked forward to what arrives and to the asset it becomes.
- Contracts Management
- What you signed, with whom, until when — with renewal and exit dates that surface before they pass, not after.
- Vendors Management
- Who supplies what, how they actually perform, and the third-party risk each one brings with them.
Compliance
In development- Control Library
- One definition of a control, reused across frameworks — because different regimes keep asking for the same evidence in different words.
- DORA
- Operational resilience for financial entities: ICT risk, incident reporting and third-party dependencies, mapped to controls.
- NIS2
- Obligations for essential and important entities under the EU directive, mapped to controls you can evidence.
- GDPR
- Processing records, lawful bases and data-subject obligations kept as a live register rather than a document someone refreshes annually.
- SOC 2
- The trust services criteria mapped to controls and the evidence behind each one.
Security Operations
In development- Command Center
- What is happening right now and what needs a person — one view instead of five consoles.
- Analyst Workbench
- Where an analyst works a case end to end, without switching tools to reconstruct what happened.
- Incidents
- Confirmed security events with an owner, a timeline and a resolution that survives the post-mortem.
- Event Search
- Free search across collected telemetry, for the question nobody wrote a rule for.
- Investigate
- Following one indicator across sources and time, to establish how far something actually reached.
- Cases
- The file that holds an investigation together: evidence, timeline and the decisions taken along the way.
- Vulnerabilities
- What is exposed and on which asset — prioritised against the CMDB, so the score reflects your estate rather than the average one.
- IOC Watchlist
- Indicators worth alerting on, whether from threat intelligence or from what you found last time.
- IP Lists
- Addresses to allow or block, maintained once instead of drifting apart on every device that enforces them.
- Threat Hunt
- Looking for what no rule has caught yet, starting from a hypothesis rather than from an alert.
Finance
In development- IT Budget
- What IT costs against what was planned, tied to the assets, contracts and licences generating the spend.
Enterprise Architecture
In development- Applications
- The portfolio of what actually runs the business, who owns each one, and what it depends on.
- Data Model
- Where data lives and how it moves — the prerequisite for answering a data-subject question honestly.
AI Governance
In development- AI Systems
- A register of the AI in use, what each system is for, and its risk classification — the inventory every AI obligation starts from.
- AI Dashboard
- Where AI is being used across the organisation, and by whom, before someone asks and nobody knows.
Capabilities
What it does
A service desk that knows what it is touching
Catalogue, tickets, changes, releases and problems in one flow, with configurable routing, service levels and a complete trail of who did what and when.
Inventory that collects itself
Lightweight agents on Windows and Linux enrol with a certificate and report over an encrypted tunnel they open outbound — nothing has to be exposed inbound, and no scanning credentials sit anywhere waiting to be stolen.
A CMDB you can actually read
An interactive topology graph of what depends on what, so impact analysis is a question you answer before a change rather than after an outage. Full history on every entity.
It fits the tools already in place
Single sign-on, mail turned into tickets automatically, a REST API for everything else, and chat integration where a team already lives.
Tenants that stay separate
Data isolated per tenant, role-based access on the principle of least privilege, sessions that expire, and an audit trail with no edit path.
Hosted in Romania, on our own infrastructure
Two data centres in the EU — the primary in Bucharest, disaster recovery in Cluj-Napoca. No third-party cloud, and your data does not leave the country.
Interested in BrainDesk MT?
Tell us about the problem you are trying to solve — an engineer answers, not a form.