The ARXML License Trap: Why Reading a Colleague's File Shouldn't Cost a Seat

Drop an ARXML file into EasyARXML and see its components, ports and connectors instantly — free, in the browser, with nothing uploaded.

In the last post I walked through what ARXML actually is: the standardized, precise, and — in raw form — nearly unreadable XML that describes AUTOSAR software architecture. I ended on a question, and this post is the answer to it. Given that reading these files is a constant, unavoidable part of automotive software work, why is opening one so often gated behind a license you have to fight for?

Welcome to MBSE Explained. This one is personal, because it's the exact annoyance that made me build a tool to fix it. Let me lay out the problem first, because if you've lived it you'll recognize every step.

The Everyday Absurdity

Here's the scene. A supplier sends over an ECU extract for review. Or a colleague on another team asks you to sanity-check the component structure in an ARXML they've been working on. You don't need to edit anything. You don't need to generate an RTE. You just need to look — to see which components are there, how the ports connect, whether the architecture matches what was agreed.

So you go to open it, and one of a few things happens. You fire up a heavyweight AUTOSAR authoring or configuration tool — the kind that takes real time just to load — to perform what amounts to a five-minute read. Or you go to check out a license from the shared pool and find every seat is taken, so you wait, or you ping the person hoarding one. Or you don't have a license assigned to you at all, because you're an integrator, a reviewer, or a manager who only occasionally needs to see an ARXML, and nobody budgeted a full authoring seat for that.

Either way, a read-only task just consumed a scarce, expensive resource — or stalled entirely waiting for one.

Why This Happens

None of this is anyone being unreasonable. It's structural. The tools that author and configure ARXML — the DaVinci-style developer and configurator tools, the tresos-style configuration environments, and their peers — are genuinely powerful, genuinely necessary for the work they're built for, and priced accordingly. Organizations buy a limited number of floating licenses and share them across a team, because per-seat licensing at those prices doesn't scale to "everyone who might ever need to look."

The result is a license pool sized for the people doing authoring work — and everyone else who merely needs to read an ARXML is quietly drawing from that same small pool. Reviewers, integrators, test engineers, architects doing a quick cross-check, managers verifying a deliverable: all of them, to answer a simple "what's in this file," are told to occupy a seat built for someone doing eight hours of configuration.

It's a mismatch between the tool's cost model and the most common actual use case. Reading is frequent, quick, and low-stakes. Authoring is rarer, longer, and expensive. Charging both at the authoring rate is where the friction lives.

And You Can't Just Use a Web Tool

The obvious modern instinct is "surely there's a website where I can just drop the file in." And for most file formats, there would be. For ARXML, there's a hard blocker: confidentiality.

An ARXML file describes real vehicle software architecture. It's covered by NDAs, it's competitively sensitive, and in many organizations it is flatly against policy to upload it to some random online converter that ships your file off to a server you know nothing about. So the one thing that would make quick reads easy — a browser tool — is exactly the thing security and legal won't let you touch, because the typical web tool means handing your confidential file to someone else's backend. That concern is completely valid, and it's why "just use an online viewer" has historically been a non-starter in automotive.

What I Built Instead: EasyARXML

This is the problem EasyARXML exists to solve, and I built it around that confidentiality constraint rather than ignoring it.

EasyARXML is a free, in-browser viewer for AUTOSAR ARXML files. You open easyarxml.com, drop in a .arxml, and it renders the architecture — software components, their P-Ports and R-Ports, compositions, and the assembly and delegation connectors between them — as an interactive diagram you can pan, auto-arrange, and read at a glance. The banner on this post is that output on a real file.

The part that makes it usable in automotive specifically: the file never leaves your machine. EasyARXML parses the ARXML entirely in your browser with JavaScript — there's no upload, no server round-trip, no storage, no telemetry on your file. You don't have to take my word for it, either: open your browser's Network tab while you load a file and watch for yourself. Nothing goes out. That's the whole point — it answers the NDA objection at the architecture level, not with a promise but with the absence of an upload.

Beyond that, it's deliberately simple:

• Free — no sign-up, no account, no trial wall. Open a file and go.
• Nothing to install — runs in any modern browser on Windows, macOS, or Linux, and works offline once the page has loaded.
• Fast — you skip loading a heavyweight toolchain just to understand a file someone sent you.
• Export to PDF — auto-arrange the diagram and download a clean report to share or archive.

It reads Classic AUTOSAR 4.x files, and it is honestly scoped: EasyARXML is a viewer, not an authoring tool. It doesn't replace your configurator for the work that genuinely needs one — it removes that tool from the huge number of moments when all you needed was to look. Free up the expensive seats for the people actually authoring, and let everyone else read for free.

Pulling It Together

The ARXML license trap is a mismatch: reading these files is constant and cheap in effort, but the tools that open them are priced and licensed for authoring. Add a legitimate confidentiality constraint that rules out ordinary web tools, and you get a genuinely annoying gap — one where people burn expensive seats, or wait on a pool, to do something that should take fifteen seconds.

EasyARXML is my answer to that gap: open any ARXML as a diagram, free, in your browser, with your file never leaving your computer. If you've ever queued for a license just to review someone's work, try it with one of your own files and tell me how it goes.

That's the mission here at MBSE Explained — simplifying systems for smarter EVs. How does your team handle ARXML reviews today — shared license pool, or something better? I'd genuinely like to know in the comments.