ECUDeck for teams

The Team plan is $199 per seat per year. It includes everything in Pro and adds what a diagnostics team, a test lab or a supplier working on several customer projects needs to share one set of bus profiles without anyone weakening its safety settings. Team is planned for the first paid release; nothing is on sale yet.

Shared profiles

Keep adapters and channels, bitrates and FD settings, the DBC files to attach, UDS tester addresses and DoIP gateways in a JSON file on a shared drive, as a folder of files in a git checkout (every .json file in it is read), or at an https URL, and point ECUDeck at it in Settings → Team. Everyone on the team sees the same connections with a Team badge; they are read-only in the editor. ECUDeck re-reads the source every 15 minutes and keeps the last good copy, so it also works in a workshop without internet. AI agents (ecudeck-mcp) see the same connections, as far as the policy allows.

The file never contains secrets: no SecurityAccess seeds or keys, no TLS private keys. ECUDeck refuses a file that does. Security-access algorithms stay on each engineer's computer.

Team policy

The policy block of the file decides, on every member's computer:

• vehicleListenOnly: every connection with the vehicle role is listen-only, whatever its own setting says. ECUDeck's backend refuses to transmit on it, including UDS requests.
• Always, without a setting: a personal connection that points at the same adapter channel or DoIP gateway as a team connection gets at least the team connection's role and listen-only switch. A personal copy does not turn a customer's car into a lab bus.
• agents: all (default), non-vehicle or none. What AI agents may read through ecudeck-mcp; hidden connections are not listed to agents and are refused by name.
• noAgentSends: AI agents may read but never ask to send frames or UDS requests on the team's connections, whatever a connection's own setting says.
• noPersonalCopies: no personal connections to the team's adapters and gateways at all.

The policy guards against mistakes, not against the owner of the computer: someone who can edit ECUDeck's files can remove the shared project. An administrator can pin the source so it cannot be changed in Settings (below).

{
  "version": 2,
  "team": { "name": "Acme Diagnostics", "contact": "tools@acme.example" },
  "policy": {
    "vehicleListenOnly": true,
    "agents": "non-vehicle",
    "noAgentSends": true
  },
  "profiles": [
    {
      "id": "bench-powertrain",
      "name": "Bench · powertrain",
      "group": "Lab 2",
      "protocol": "can",
      "role": "bench",
      "can": {
        "adapter": "pcan",
        "channel": "PCAN_USBBUS1",
        "bitrate": 500000,
        "fd": false,
        "listenOnly": false,
        "dbc": ["powertrain.dbc"],
        "uds": { "request": "0x7E0", "response": "0x7E8" }
      }
    },
    {
      "id": "car-gateway",
      "name": "Car · DoIP gateway",
      "protocol": "doip",
      "role": "vehicle",
      "doip": { "host": "192.168.0.12", "port": 13400, "testerAddress": "0x0E80" }
    }
  ]
}

Rules: version is 1 or 2 (team and policy need 2); every connection needs a unique id (letters, digits, ., _, -), a name and a protocol; unknown fields are refused; at most 500 connections and 1 MB per file, 64 files in a folder. In a folder, ids must be unique across files and the strictest policy wins.

Making the team file

Set the connections up in ECUDeck, then Settings → Team → Export for team…: choose connections, the team's name and who maintains the file, and the policy. ECUDeck writes a version 2 file without any secret. To extend a shared project, export again with "the connections of the shared project in use" ticked: their ids stay the same.

Seats

One Team subscription has as many seats as you buy. Whoever pays is the billing manager: in the Polar customer portal they assign each seat to a teammate's email. Each teammate gets their own ECUDECK- key for up to 3 of their computers. A seat can be taken back and given to someone else; the old key stops working at its next weekly check (or within 30 days on a computer that stays offline). ECUDeck never sends names or emails of your team anywhere.

Managed deployment

To roll ECUDeck out on engineering laptops or test-rig PCs, provide on the machine:

• the key: the environment variable ECUDECK_LICENSE_KEY, or a file with the key on its first line (%ProgramData%\ECUDeck\license.key on Windows, /etc/ecudeck/license.key on Linux, /Library/Application Support/ECUDeck/license.key on macOS);
• the shared project: ECUDECK_TEAM_SOURCE, or a team-source file next to license.key with the path, folder or https URL on its first line. Settings then shows it as set by the administrator and cannot change it.

Machines without internet activate offline: ECUDeck writes a request file, someone uploads it at ecudeck.com/activate from any online computer, and the response file is imported back.

Write log

Every frame and UDS request ECUDeck sends, every replay, and every one its guard refuses, is appended to a local log (one JSON line each: time, user, connection, role, adapter, frame or service, result, and for agent requests the agent and its reason). Each line carries a hash of the line before it, so an edited or removed line is reported. Settings → Write log exports it for your records. The log is on every plan and never leaves the computer.

Support

Team customers get priority email support at support@ecudeck.com. For more than 200 seats or an invoice, write to the same address.