TAOM PROCESS STUDIO
Licences compared
From free trial to enterprise licence. Every tier uses the same editor – they differ in the AI support that comes with it and how deeply processes are elaborated – up to the digital twin of your organisation with processes, roles and systems, digitally embedded in your existing system landscape.
Without an account
anonym
CHF 0
Try it without an account. Smallest language model, no permanent storage.
Demo
demo
CHF 0
Registered, with your own workspace. For getting to know the tool, not for productive use.
Process Studio Modeller
webuser_basic
The editor itself: draw, import, export without limits, full screen – deliberately without AI.
team-capableWebuser
webuser
Editor with AI agents: create models from text and have them elaborated.
Webuser Pro
webuser_pro
Full scope of functions, strongest model, all elaboration fields.
Enterprise
enterprise
on request
Like Webuser Pro – plus your own tenant, your own branding, free choice of models and integrations.
training requiredFeature matrix
All functions per licence tier – filterable by area and tier. ✓ included · with … add-on licence can be added · coming soon in preparation · – not included
Tier
No function found.
| Feature | No account | Demo | Modeller | Webuser | Webuser Pro | Enterprise |
|---|---|---|---|---|---|---|
| Editor | ||||||
| Draw and edit BPMN models | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Import existing BPMN and XML files including from SAP Signavio, Microsoft Visio, bpmn.io, Camunda and comparable tools – including the quirks other tools leave behind on export |
✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Export as a BPMN file open format, reusable in any BPMN tool |
– | up to 20 elements | ✓ | ✓ | ✓ | ✓ |
| Export as HTML and PDF process documentation to pass on, with origin seal |
– | up to 20 elements | ✓ | ✓ | ✓ | ✓ |
| Elaborated content included in the export attributes, roles and specifications on the elements |
– | – | – | ✓ | ✓ | ✓ |
| Full screen for meetings and shared screens canvas across the whole page, palette and attributes stay visible |
✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Full-text search in the diagram label, description, TAOM ID, ERP functions |
– | – | – | – | ✓ | ✓ |
| Your own workspaces | – | ✓ | ✓ | ✓ | ✓ | ✓ |
| Retention of workspaces | temporary | deleted regularly | permanent | permanent | permanent | permanent |
| AI support | ||||||
| AI agents (create models from text) | limited | ✓ | – | ✓ | ✓ | ✓ |
| Elaboration of content (enrichment) | – | – | – | ✓ | ✓ | ✓ |
| Language model | smallest | gpt-4o-mini | none | gpt-4o | gpt-5.6-sol | free choice by agreement |
| Elaborated fields | ||||||
| Category, origin, validation, security, compliance, description | – | – | – | ✓ | ✓ | ✓ |
| ERP component, issue type, WRICEF object | – | – | – | ✓ | ✓ | ✓ |
| ERP functions, functional & technical spec, component, labels | – | – | – | – | ✓ | ✓ |
| Enterprise model | ||||||
| View the process hierarchy L0 to L5 process landscape, categories, end-to-end processes, areas, business processes, procedures | – | example | example | ✓ | ✓ | ✓ |
| Create and maintain the hierarchy create, rename, move and remove levels | – | – | – | – | ✓ | ✓ |
| Framework from the organisation take over categories and end-to-end processes from the streams of the project organisation | – | – | – | – | ✓ | ✓ |
| Place models in the enterprise attach a BPMN model to a level – from the overview down to the individual procedure | – | – | – | – | ✓ | ✓ |
| IDs from the number range P2M.01.02.01-AC001 instead of a sequential number – the same ID in the model, Jira and Confluence | – | – | – | – | ✓ | ✓ |
| Save the structure as a table hierarchy with numbers and linked models as CSV | – | – | – | view | ✓ | ✓ |
| Status per level calculated across all models below – gaps are visible at the level | – | – | – | view | ✓ | ✓ |
| Check and transfer moves move pages instead of recreating them – history, comments and attachments are kept | – | – | – | – | ✓ | ✓ |
| Project organisation and responsibility | ||||||
| Link units to the enterprise model a stream carries an end-to-end process – without maintaining the abbreviations twice | – | – | – | – | ✓ | ✓ |
| Maintain the project organisation Levels, streams, teams, roles – as a model, not a drawing | – | – | – | – | ✓ | ✓ |
| Assign people and set RACI accountable · responsible · consulted · informed | – | – | – | – | ✓ | ✓ |
| Personal confirmation of a role E-mail to the named person, acceptance or objection | – | – | – | – | ✓ | ✓ |
| Download import template (Excel) Guide, examples and your project keys – viewable without an account | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Upload organisation from Excel Dry run shows new, changed and missing – written only on request | – | – | – | – | ✓ | ✓ |
| Audit trail and history who, since when, confirmed when, replaced by whom | – | – | – | – | ✓ | ✓ |
| Org chart generated automatically Levels, connections, people and roles computed from the model | – | – | – | – | ✓ | ✓ |
| Search for responsibility gaps no accountable, more than one, responsibility outside the company | – | – | – | – | ✓ | ✓ |
| AI staff in the organisation Agents as their own origin, deployment confirmed by their owner · What may an agent decide? | – | – | – | – | view only | ✓ |
| Transfer the org chart to Confluence one page per unit, with elaboration and quality view | – | – | – | – | one page | ✓ |
| Org chart as a presentation (PPTX) Overview, one slide per group, elaborations as follow-up slides – each box a movable group, not a picture | – | – | – | – | ✓ | ✓ |
| Digital twin of the organisation | ||||||
| BPMN processes, organisational charts, process maps | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| RACI matrices and system landscapes | – | limited | ✓ | ✓ | ✓ | ✓ |
| Roles and mapping to process levels (L3/L4) | – | – | ✓ | ✓ | ✓ | ✓ |
| Origin seal and AI labelling in exports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Agents by role | ||||||
| Process owner: full elaboration incl. quality and knowledge | – | – | – | ✓ | ✓ | ✓ |
| BPMN modeller: structure, shape elaboration, attached knowledge | – | – | – | ✓ | ✓ | ✓ |
| Quality manager: risks, controls, tests, approvals | – | – | – | limited | ✓ | ✓ |
| Delivery: epics and stories for issue tracking, functional & technical spec | – | – | – | – | ✓ | ✓ |
| Viewer: role-appropriate explanation without elaboration | – | ✓ | ✓ | ✓ | ✓ | ✓ |
| Governance · Field control and approvals | ||||||
| Model versions with approval draft → for approval → approved or rejected · the most recently approved version is valid | – | ✓ | ✓ | ✓ | ✓ | ✓ |
| Field control: who may edit and approve which field per role from the project organisation – down to field level | – | – | – | – | ✓ | ✓ |
| Four-eyes principle for process steps and model versions enforce or only log | – | – | – | – | ✓ | ✓ |
| Information protection per protection level what is transferred to which target system (e.g. Jira, Confluence) | – | – | – | – | ✓ | ✓ |
| Model classification Public to Strictly confidential · minimum level of all steps · signed in the provenance seal, visible in the editor, viewer and export · classified models remain protected in every licence | – | – | – | – | ✓ | ✓ |
| Clearance level per person and outputs per classification who may open which level · BPMN, PDF, HTML, manual, test evidence, viewer, Jira, Confluence, Cloud ALM, channels: allowed, only with the right, or blocked | – | – | – | – | ✓ | ✓ |
| AI agents with their own clearance level one line per agent, right “Use AI agents” per person · an agent never sees more than the person who triggers it · decided by the administrator | – | – | – | – | ✓ | ✓ |
| Export note and export log every output with classification, person, time and number · rejected attempts are logged too | – | – | ✓ | ✓ | ✓ | ✓ |
| Inheritance to tests, reporting, mining and project times models above the clearance level hidden · steps above it blacked out, model read-only | – | – | ✓ | ✓ | ✓ | ✓ |
| Guest access by classification the administrator sets the highest level and the rights of guests (default: at most Confidential, only with the right of the inviting person) | – | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Information protection report in reporting classification per step, outputs, export log, guests · with its own right | – | – | – | – | ✓ | ✓ |
| Integrations | ||||||
| Position in the enterprise model within the BPMN file node and number in the origin seal – traceable outside TAOM too | – | – | – | – | ✓ | ✓ |
| Digital integration into knowledge platforms e.g. Confluence, SharePoint or comparable systems |
– | – | diagram | diagram + content | ✓ | ✓ |
| Digital integration into issue tracking and development systems e.g. Jira or ServiceNow: epics, stories, tasks – or comparable systems |
– | – | – | – | ✓ | ✓ |
| TAOM BPMN Viewer (standalone display, e.g. in Confluence) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Connection to enterprise systems e.g. SAP, SAP Signavio, ServiceNow, Microsoft 365, n8n, Make, GitHub, Power BI |
– | – | – | – | project-specific | ✓ |
| Collaboration | ||||||
| Work on the same model together | – | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Team chat during the joint session can be switched on in the settings · only while working together – nothing is saved or logged | – | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Start teamwork: who is working where right now on the start screen and via “Team” in the sidebar – knock, invite colleagues | – | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Guest access for other companies and sites share individual models with people who have their own licence – they only see these models; own Team add-on licence on both sides | – | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Team add-on licence available | – | – | included | ✓ | ✓ | ✓ |
| Invite further users (company licence) | – | – | ✓ | ✓ | ✓ | ✓ |
| Channels: notifications to Microsoft Teams and Slack Cards from your own processes in your own channel – only notifications of your own organisation |
– | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Maintain target systems yourself Jira, Confluence and further systems in the customer account, each target with its own access |
– | – | included | with team add-on licence | with team add-on licence | with team add-on licence |
| Add-on licence · Testing and verification · Verification duty at the process step | ||||||
| Verification duty at the process step which steps must be verified – visible in the diagram and in the coverage |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Risks with controls – assessed according to GAMP 5, FMEA, ISO 31000 and others severity, probability and detectability determine the risk class and test depth · risk register with coverage |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Equipment & infrastructure, qualification IQ / OQ / PQ equipment per step with manufacturer, model, location · protocol stored access-protected at the step |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Marking in the diagram (colour and symbol freely selectable) | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Add-on licence · Testing and verification · Test cases and test runs | ||||||
| Test cases with test steps precondition, steps and expected results proposed from the diagram – without an AI agent |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Process tests (E2E) paths through the model from start to end, including across linked models |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Guided test runs with evidence result, test data and screenshot per test step · save and continue later |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Record and hand over defects as an issue in the target system (e.g. Jira), status in the customer account |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Test plans and cycles in the customer account e.g. SIT, UAT, regression – with period, release and progress |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Synchronisation with the target system e.g. Jira, Confluence – per person testing |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Worklist “Testing & verification” failed and blocked runs, test cases without a run, steps requiring testing without a test case, risks without a control – across all models, with a path to test management | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Add-on licence · Testing and verification · Approval, evidence and manual | ||||||
| Approval, versions and four-eyes principle every change after approval creates a new version · acceptance logged |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Test evidence as PDF stored unalterably, with ID and checksum (SHA-256); viewing and downloading only with a dedicated permission |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Digital signature for test evidence Signing round with roles from the project organisation, every signature confirmed with a password, then a signed version with its own seal · open signatures are reminded after a configurable number of days, a new run marks the version as outdated |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Automated data protection Mail addresses, names and identifiers in evidence, manuals, exports, mails and target systems only according to your settings · screenshots pre-checked automatically, confirmed by a human in the loop · placeholders instead of names for the AI agent |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| TAOM Screen Engine Capture and mark screenshots in the test run: click point, number, frame, line, arrow, double arrow, field · self-timer · obscure personal data right on the photo and confirm it as checked |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| TAOM Data Protection Screen Engine Screenshots pre-checked by a background job, progress saved · analysis by number of findings · human in the loop for samples and borderline cases |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| TAOM Datenschutz Design Protection Define protection patterns (e.g. drawings, plans, bills of materials, formulations) and blocked applications · detect photos in the test run automatically · save them blocked and log the attempt · lock image in PDF, manual and viewer · release only with «View originals» |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| TAOM Data Protection Content & Logs Logs in the customer’s hands: placeholder «Person n» instead of names as soon as written · matrix per log type (people, retention, target systems) · terms and keywords · follow-up run with tiles · rights «View logs» and «Reveal people» · as before without a setting |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Document seal and authenticity check every test record with document number and QR code, verifiable at taom.ai/beleg/ without access to TAOM |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Signatures in reporting which test records are signed and filed, and which role is still missing |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Generate user manual as Word and PDF in DE, EN, FR, ES – with screenshots from the test runs |
– | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Test add-on licence available | – | – | – | ✓ | ✓ | ✓ |
| Add-on licence · Testing and verification · Process re-engineering from test runs | ||||||
| Detect deviations between test run and model added steps, missing stations, order, missing path, skipped mandatory steps | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Decide: forgotten in the process, variant or test path only the step or branch enters the model dashed – as a new version for approval | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Consequences of changes as review tasks affected test cases, specifications and approvals – with the people responsible in Reporting “Tasks” | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| Download and upload test cases as Excel per model or test plan, with a dry run before applying; template with examples; button in the editor as well | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| New model from the test plan – rule-based (without AI) one step per test step, one lane per role – as a draft, approved by the process owner | – | – | – | with test add-on licence | with test add-on licence | with test add-on licence |
| New model from the test plan – with AI the agent builds the model from the test plan | – | – | – | coming soon with test add-on licence | coming soon with test add-on licence | coming soon with test add-on licence |
| Notification after approval issue in the target system (e.g. Jira) or card in Microsoft Teams | – | – | – | coming soon with test add-on licence | coming soon with test add-on licence | coming soon with test add-on licence |
| Add-on licence · Process Mining · and project times | ||||||
| Times at the process step processing, waiting and lead time · mean, median, 90th percentile · case count per period |
– | – | – | with Mining add-on licence | with Mining add-on licence | with Mining add-on licence |
| Compare actual times with the plan source per value: manual or interface |
– | – | – | with Mining add-on licence | with Mining add-on licence | with Mining add-on licence |
| Mapping to the event log activity and object type – basis for a later transfer via interface |
– | – | – | with Mining add-on licence | with Mining add-on licence | with Mining add-on licence |
| Process Mining add-on licence available | – | – | – | ✓ | ✓ | ✓ |
| Interfaces to external systems automatic transfer e.g. from an ERP system or target system – not included, available separately on request |
– | – | on request | on request | on request | on request |
| Project times at the process step plan and actual per activity, with role and service month, in hours or person-days – without an add-on licence |
– | – | ✓ | ✓ | ✓ | ✓ |
| Add-on licence · Reporting | ||||||
| Reporting on the enterprise model all models below one node: overview, Process Mining, project times, tests & risks |
– | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| From the report straight to the process step every KPI, every bar, every heatmap cell leads to the affected steps |
– | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Roles and approvals who has which role, at which status, in which process – and where responsibility is missing | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Tasks per person or role approvals, rework, open tests, review tasks – direct, via the role or for information · time spent and workload | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Period and trend Whole period, one month or a trend over 3, 6 or 12 months · all views follow the period, with comparison to the previous month | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Choose chart type and enlarge Ring, pie, bar, line, Pareto, area or stacked – switchable per chart, with a magnifier in its own window | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Reporting next to the model Move, dock or maximise the window · Reporting stays open when a model is opened | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Open documents and evidence directly Documents on the model and the step, attachments of test runs, test cases and risks – also from other models, protected by permission | – | – | – | – | with Reporting add-on licence | with Reporting add-on licence |
| Reporting add-on licence available | – | – | – | – | ✓ | ✓ |
| Add-on licence · Change Impact Management | ||||||
| Change management in the model file who/what/when recorded in the model (validation/GxP) · switched on by the customer’s administrator | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Impact score with contributions 0–100, every contribution visible · weights and thresholds adjustable · fixed rules for safety-critical changes | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Internal and external effort standard values, actual data from test runs, planned project times · consultant days with daily rate | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Three levels: score, effort, costs costs only with the right “View costs” · remuneration data of individual people only for the administrator | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Change as an object (change request) tasks with plan/actual · four-eyes approval · critical path in working days | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Notification and target system email and channel (e.g. Teams) depending on connection · tasks into the target system (e.g. Jira) | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Changes & impact in reporting per model; across all models with the Reporting add-on licence · filters, pie charts, learning from completed changes | – | – | – | – | with Change Impact add-on licence | with Change Impact add-on licence |
| Change Impact add-on licence available per customer – applies to all accounts of the company | – | – | – | – | ✓ | ✓ |
| Add-on licence · Process Studio Viewer · processes for the whole company | ||||||
| Public showcase models in the Viewer BPMN demos with flow, manual, test cases, process mining and project times – without an account |
✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Viewer seat per named person Read, favourites, manuals and test cases – without an editor licence |
– | – | with Viewer licence | with Viewer licence | with Viewer licence | with Viewer licence |
| Roles and personal areas from the project organisation · broad roles and exceptions per person |
– | – | with Viewer licence | with Viewer licence | with Viewer licence | with Viewer licence |
| Reports on the process step Error, missing variant or question → tickets in the editor · adopt a variant as a draft |
– | – | with Viewer licence | with Viewer licence | with Viewer licence | with Viewer licence |
| Content according to the company licence Test management, risks, reporting, process mining and project times – as in the editor |
– | – | with Viewer and add-on licence | with Viewer and add-on licence | with Viewer and add-on licence | with Viewer and add-on licence |
| From the Viewer into the editor People with an editor licence open the model directly in the editor – same or own domain |
– | – | ✓ | ✓ | ✓ | ✓ |
| Enterprise only | ||||||
| Your own tenant at a licensed TAOM partner of your choice | – | – | – | – | – | ✓ |
| Your own branding: logos, colours, labels | – | – | – | – | – | ✓ |
| Embedded in the customer’s existing infrastructure | – | – | – | – | – | ✓ |
| Free choice of language models by agreement including requirements on provider or data residency |
– | – | – | – | – | ✓ |
| Free choice of integrations (Copilot, n8n, make.com and others) | – | – | – | – | project-specific | ✓ |
| Zero Data Retention (ZDR) for AI processing optional by agreement · depends on model provider, endpoint and technical enablement |
– | – | – | – | – | ✓ optional |
| Administration in your hands (users, roles, content) | – | – | – | – | – | ✓ |
| Licence management at Traniva (admin rights or interface) | – | – | – | – | – | ✓ |
| Training as a prerequisite | – | – | – | – | – | infrastructure · agents · modeller |
| Commercial terms | ||||||
| Term | – | – | 1 – 36 months | 1 – 36 months | 1 – 36 months | by agreement |
| User seats | 1 | 1 | freely selectable | freely selectable | freely selectable | by agreement |
| Upgrade possible at any time | – | ✓ | ✓ | ✓ | Enterprise only | individual agreement |
Moving to a higher tier
You can move up at any time. What you paid for your current licence is not lost: the remaining value is credited against the price of the new licence, and you pay only the difference.
1. Sign in
Only when you are signed in does the Marketplace know your current licence – and can credit it.
2. Choose the new tier
The remaining value of your term appears as a deduction directly in the licence selection.
3. Confirm the seats
The number of user seats is carried over. More is always possible, fewer than occupied is not.
4. New key
All users move across automatically. The previous key ceases to be valid.
How the remaining value is calculated
To the day: the amount paid for the current licence is divided by its term and multiplied by the remaining days. At most the price of the new licence is credited – there is no payout or credit note. Training and project services are not included in the calculation, only licences.
Fewer seats than before? That is possible as long as nobody is locked out – but the difference lapses without refund. Before you submit the order you are shown how many seats will be available after the change.
What is not possible
Moving to a lower tier during the current term is not provided for. Once your licence expires you can purchase a different tier at any time.
Right of withdrawal and immediate start
Consumers in the EU, the EEA and the United Kingdom have a fourteen-day right of withdrawal. You decide at the point of purchase how to proceed:
Start immediately
You confirm immediate provision. The purchased tier is active straight away; the right of withdrawal lapses when use begins.
Keep the right of withdrawal
You immediately receive Process Studio Modeller (without AI) and the purchased tier once the fourteen days have passed – or earlier, as soon as you consent in your account.
Businesses have no right of withdrawal; their orders are binding.
Enterprise: your own tenant, in your own house
Enterprise is not a bigger licence but a different way of running the product. You get your own tenant on a dedicated hosting server, embedded in your existing infrastructure – with your logos, your colours and your wording.
Your own tenant
Separate environment, your own data storage, no shared operation with other customers – run by a licensed TAOM partner of your choice.
Your own look
Logos, colours and labels to your specification, in the editor and in exports alike.
Free choice of integrations
Copilot, n8n, make.com and others – you decide what is connected and how deeply.
Free choice of models
Which language models are used is agreed according to your requirements – for instance where data residency or provider are prescribed.
Zero Data Retention – optional for Enterprise
For Enterprise configurations, processing with zero data retention (ZDR) can be agreed. ZDR is not part of the standard licences; availability, conditions and documentation are described in the Trust Center.
What zero data retention means →
Enterprise privacy options
Zero data retention is one of several sovereignty options. Which of them apply is examined per undertaking and recorded in the Enterprise agreement. Further options: EU processing · customer model (BYOM) · private model hosting · custom data flow.
Details in the Trust Center →
You administer
You manage users, roles, workspaces and content yourself – without going through us.
We manage the licences
Traniva retains rights at licence level or an interface for reading them. Everything else is yours.
Training is a prerequisite
Before go-live, the future administrators complete three training courses. They are not an extra but the condition for the environment to hold up in daily use:
Infrastructure training
Setup, tenant separation, integration and operation.
Agent training
Understanding and applying agents – models, standards, automation.
Modeller training
Editor and process method: modelling BPMN properly and starting out safely.
Why the licence level stays with us: only this way can we assure which model versions and elaboration states run in your environment, and that licences, seats and terms match the contract. Operation takes place at a licensed TAOM partner, day-to-day administration is yours – the only exception is licence management.
Support and training
Support and training run on dedicated TAOM systems – the support portal (support.taom.ai) and the training platform (training.taom.ai). You sign in there with your TAOM account, without a new password; you can also reach tickets and courses directly from the editor. Support is available only for registered accounts.
Basic ◐
For registered accounts without a licence: report software errors (incidents), without a guaranteed response time.
Standard
Included in every licence. Response usually within two working days, without a firm commitment.
Business
In addition, questions about operation, prioritised handling and extended response times – surcharge on the licences.
Enterprise
Individual SLA and personal support; on request, your own support for your employees with escalation to TAOM.
Training: courses, e-learnings and certifications on the training platform, in the Standard, Business and Enterprise levels; depending on the course, an active licence is a prerequisite. Details to follow.
Digital integration and third-party licences
The digital twin does not stay in the editor. Processes, roles and elaborations flow into the systems your company already works with – knowledge platforms, issue tracking, ERP, automation. The products named are examples: Confluence, Jira, ServiceNow, SharePoint, SAP, SAP Signavio, Microsoft 365, n8n, Make, GitHub and Power BI stand for comparable systems that can be connected in the same context. Existing models from SAP Signavio, Microsoft Visio, Camunda or bpmn.io can be imported and reused – including the quirks other tools leave behind on export, such as separately stored labels. You do not start from scratch.
Such connections generally require the providers’ own licences. They are not part of the TAOM licence and are procured separately. During Enterprise roll-outs we determine together which environments and interfaces your digital-twin use case actually needs.
Prices in Swiss francs, plus VAT where applicable. For deliveries abroad no VAT is charged; the amount payable in local currency is shown in the licence selection and on the invoice. The general terms and conditions apply.
Related
What the licence key itself contains and how seats are counted is on the packages page. What an organisation’s belonging rests on, and how it is checked on every access, is in the Trust Center.
Prices and packages → · Trust Center → · Working as a team →
Add-on licences
Alongside the tier there are five separate add-on licences, each with its own key and its own term, cancellable separately and without any effect on the purchased tier: Team (working on the same model, channels, target systems), Testing and verification (risks, qualification, test cases, E2E, evidence and user manuals – per person testing, regardless of their tier), Process Mining (times, key figures and plan/actual at the process step), Reporting (analysis across all models on the enterprise model, from Webuser Pro) and Change Impact Management (assessment of changes with score, effort, costs, tasks and approval – per customer, from Webuser Pro). Interfaces to external systems are not included in any add-on licence and are offered separately on request.
Team → · Testing and verification → · Process Mining → · Reporting → · Terms in the glossary →
Across all models
Search for what no single model contains
Role, system, transaction, verification duty, risk, test case – all of this sits at the process step and can therefore be searched across the whole enterprise. Where is this role used? Which steps require verification but have no test case?