Insight · Platform

Sparx EA Licensing Guide: User Types, Concurrent vs Named, Team Sizing

By Sparx Services · June 6, 2025

Getting Sparx EA licensing right is mostly a question of two decisions: which edition each architect needs, and whether they draw on a Named license or a shared Concurrent pool. Get those right and the rest of the bill of materials follows. Get them wrong and you either block people from working or pay for capacity that sits idle.

Licensing also decides who can work in the model, and that decides how much of your team’s work can be AI-augmented. The architect states what should be done and AI does the mechanics in the tool and the model, which needs a licensed EA client on the architect’s machine. The AI Power Tools for Sparx EA are free for every Sparx user and need Enterprise Architect 16.1 or later; the Claude or GitHub Copilot subscription and any LLM usage are separate from your Sparx licenses.

Sparx Systems sells every Sparx EA license directly. Sparx Services does not resell them and takes no margin on the sale. What we can do is work out what your deployment needs and hand you a bill of materials to purchase against, so our advice has no stake in over-licensing you. For prices, see Sparx Systems’ current pricing.

The four Sparx EA client editions

Each edition builds on the one below it, so the question is how far up the stack each architect needs to be. Check Sparx Systems’ current edition comparison for the exact feature split.

Professional

The entry point. Professional is a full UML modeling environment that also covers ArchiMate, BPMN, SysML, entity-relationship and database modeling, plus code engineering and standard report generation.

Who it suits: individual architects and small teams who need solid modeling without enterprise repository or framework features.

What it lacks: shared DBMS repositories, and the built-in enterprise frameworks and systems-engineering tooling that arrive in the higher editions.

Corporate

Corporate is the first edition built for teams. Its defining addition is the ability to host the shared model repository on a range of database management systems (SQL Server, MySQL, PostgreSQL, Oracle and others), alongside the security and collaboration features that come with multi-architect work.

Who it suits: EA teams running a shared repository and doing serious governance: review, baselining, and several architects working the same domain.

Unified

Unified builds on Corporate by adding built-in enterprise frameworks such as TOGAF, Zachman, UAF and UPDM, together with broader meta-model support and the model patterns that go with them. Many enterprise EA practices look at this edition first, because it pairs the shared repository with the framework scaffolding most programs run on.

Who it suits: enterprise architecture practices standardizing on a named framework who want the patterns and meta-model support out of the box.

Ultimate

Ultimate bundles everything in the other three editions and adds the fuller systems-engineering and simulation toolset, including executable models and advanced SysML.

Who it suits: practices working across EA and systems engineering, defense and complex-systems organizations, and teams doing formal model-based systems engineering (MBSE) alongside traditional EA.

A note on custom metamodels: if your practice plans to author its own MDG Technology profiles, check Sparx Systems’ edition comparison for what each edition supports before you buy.

Named vs Concurrent licenses

This is the choice that drives the most cost, and it comes down to a single trade-off: guaranteed availability for one person, or a smaller shared pool that flexes across many.

Named

A Named license is assigned to one specific person and is theirs alone. One license, one user, always available regardless of who else is connected.

Best for: architects who live in Sparx EA every working day and need it on demand.

The catch: ten Named licenses for ten architects consume all ten slots even when only three people are working. You pay for peak capacity all the time.

Concurrent

A Concurrent (floating) license comes from a shared pool. An architect draws one when they connect and returns it when they close the tool. The pool size is your maximum simultaneous users, not your headcount.

Best for: teams where not everyone is active at once, which describes many enterprise EA teams.

How it runs: Pro Cloud Server checks Concurrent licenses in and out, which is why floating deployments need PCS.

How many licenses do you need?

For Named licenses the math is simple: count the people who need guaranteed access. Concurrent pools take more thought, because you are sizing for the simultaneous peak and not for total headcount. Start from how your people work: who is in the tool every day, who contributes occasionally, which time zones overlap, and whether part-time contributors are in the count. Measure the simultaneous peak where you can, and size the pool with a buffer above it.

Occasional and read-only access

Stakeholders, program managers, and reviewers who only need to read the repository can use WebEA, the browser interface served by Pro Cloud Server, instead of an EA client. Check Sparx Systems for the current terms on viewer access.

Pro Cloud Server licenses

PCS is licensed separately from EA client licenses, and one does not replace the other. EA client licenses are what architects use to model; the PCS license entitles you to run the server that brokers connections, manages the Concurrent pool, and serves WebEA. PCS has its own tiering, and the right tier depends on your concurrent user count and how many repositories it hosts.

We can size the PCS requirement from your planned concurrent load and repository layout. For a fuller picture of what PCS does and when a deployment needs it, see What is Sparx EA Pro Cloud Server.

AI options and licensing

If your plan includes AI-augmented work, the pieces are licensed differently. The AI Power Tools for Sparx EA are free for every Sparx user, published by NovoCircle. Kernaro Assist (in the EA client) and Kernaro AI Hub (web) are Sparx Systems products, licensed through Sparx Systems and bring-your-own LLM, so you supply the keys and pay the usage. Prolaborate 6 with AI needs a Kernaro AI Hub license and your own LLM. We include these in the bill of materials only where they are in scope for your deployment. AI tools for Sparx EA sets the options side by side by the job each one helps with.

Building the full bill of materials

A complete license bill of materials for a typical enterprise deployment comes down to a short, ordered list:

Sparx EA client licenses: edition (Professional / Corporate / Unified / Ultimate) and count (Named, or Concurrent pool size).
Pro Cloud Server license: tier and concurrent-connection capacity.
AI and connectivity options: only where they are in scope.

We can produce this bill of materials as a recommendation document, and your organization buys directly from Sparx Systems against it. Because we take no commission or margin on license sales, our interest is a correctly licensed deployment: not under-licensed, which blocks people from working, and not over-licensed, which wastes budget.

Frequently asked questions

What is the difference between Sparx EA Corporate, Unified, and Ultimate editions?

Corporate adds shared DBMS repositories and team features over Professional. Unified adds the built-in enterprise frameworks (TOGAF, Zachman, UPDM, UAF) and meta-model support. Ultimate bundles everything, including the full systems-engineering and simulation toolset. For ArchiMate-based architecture governance, Corporate or Unified usually fits; Ultimate suits practices that also do formal MBSE. Check Sparx Systems' current edition comparison before you decide.

Can we mix Named and Concurrent licenses in the same deployment?

Yes. A common pattern is Named licenses for lead architects who need guaranteed availability, plus a Concurrent pool for a wider group of occasional contributors. Pro Cloud Server manages the floating pool. We can advise on the right mix for your usage patterns.

What happens when the Concurrent license pool is full?

When every Concurrent license is checked out, the next architect who tries to connect gets a no-license-available error and can retry once one is returned. That is why you size the pool with a buffer above your typical simultaneous peak rather than at the average.

Does everyone who views architecture in WebEA need an EA client license?

Generally no. WebEA gives browser access to the repository through Pro Cloud Server, so stakeholders, reviewers, and program managers who only view diagrams and read documentation do not need an EA client. People who create, edit, or manage content in the Sparx EA client do need a license. Check Sparx Systems for the current terms.

How does Sparx Services help with licensing if you don't sell licenses?

Our role is to calculate what you need and leave the transaction to you. We document the bill of materials (EA client licenses, PCS, and any AI or connectivity options), with the edition, quantity, and license type for each, and you take it to Sparx Systems to purchase. That reduces the risk of under-licensing, which causes access problems, and over-licensing, which wastes budget.

Not sure how many licenses your team needs?

We can teach your architects to work in a licensed, shared Sparx EA repository this way and mentor them until it sticks, or set up and build the model for you and hand it over. We can also put together the bill of materials, with no margin in it for us.

Book a call

Keep reading