If you work on a data architecture team at a large company, there is a good chance one of two names sits on your desktop: erwin Data Modeler or ER/Studio. Both have been around for decades, both handle conceptual, logical and physical modeling, and both have spent the last few years adding cloud platform support, Git workflows and AI assistants. On paper they look similar. In practice the differences show up in how each product packages collaboration, how it connects to governance tools and how you pay for it.
erwin Data Modeler is owned by Quest Software, which acquired erwin, Inc. at the turn of 2021. ER/Studio is sold by Idera, which took over the product line when it acquired Embarcadero Technologies in 2015. This erwin vs ER/Studio comparison walks through editions, repository and collaboration features, supported platforms, governance integrations, AI features and licensing, using the vendors’ own documentation as the source for every product detail.
If you are still building a shortlist and want to see the wider market first, our roundup of the top data modeling tools covers lighter and cloud-native options as well.
| Area | erwin Data Modeler (Quest) | ER/Studio (Idera) |
|---|---|---|
| Editions | Standard, Workgroup, Navigator (viewer) | Data Architect, Data Architect Pro, Enterprise |
| Shared repository | Workgroup edition (erwin Mart) | Data Architect Pro and Enterprise |
| Web collaboration | erwin ER360 portal (add-on) | Team Server Core (Enterprise, additional cost) |
| Git version control | Yes | Yes (Git connectivity added in version 20.3) |
| Business glossary | Through erwin Data Intelligence integration | Enterprise edition |
| Third-party governance links | Built around Quest’s erwin Data Intelligence | Collibra and Microsoft Purview (Enterprise) |
| AI features | GenAI model generation, industry modeling frameworks (15.1) | ERbert AI Data Modeling Assistant in all editions |
| Desktop OS | Windows; macOS versions listed in system requirements | Windows |
| Published pricing | No public list price | Per-user subscription prices for two editions; Enterprise by quote |
erwin started life at Logic Works, passed through Platinum Technology and Computer Associates, became erwin, Inc. under private equity ownership in 2016, and then moved to Quest. erwin now sits in a Quest portfolio that includes erwin Data Intelligence for cataloging and lineage. The current major line is version 15, with 15.2 released in early 2026. In 2026 Quest also introduced a separate cloud product called Quest Data Modeler, which Quest positions as a companion to erwin Data Modeler for engineers and analysts who want to build and iterate quickly, not as a replacement.
ER/Studio was an Embarcadero product before Idera’s acquisition and is now sold directly by Idera. The desktop product, ER/Studio Data Architect, is on the 20.x release line, and recent releases have added Databricks data types, Git connectivity and Microsoft Purview enhancements. Idera markets three editions with a clear progression from individual modelers to governed enterprise teams.
Quest sells erwin Data Modeler in three editions. Standard is the full modeling client for an individual: conceptual, logical, physical, dimensional and NoSQL models, reverse engineering, schema generation, model and database compare, and file-based import and export. It does not include repository storage or multi-user collaboration.
Workgroup includes everything in Standard and adds the shared repository. Quest’s edition page lists repository-based model storage and metadata sharing, multi-user collaboration with conflict resolution, change management and version control, centralized storage of naming standards, user permissions and security, and web-based repository administration. It also lists bulk harvesting of models into the erwin Data Intelligence catalog and glossary.
Navigator is a read-only edition for people who need to look at models without changing them. It can display ERD and JSON structures, search and browse model metadata, and produce PDF, HTML and text reports.
Two add-ons sit beside the editions. erwin ER360 is a web-based platform for sharing models and metadata with stakeholders who do not run the desktop client. The erwin Safyr option handles metadata discovery and model creation for ERP systems, which is a narrow but valuable need for teams working with packaged applications.
Idera’s lineup is also three tiers, but they map to team size rather than to author versus viewer. ER/Studio Data Architect is described as modeling for individuals and includes a local Data Dictionary for standards and reuse. Data Architect Pro targets growing teams and adds a central repository with version history, check-in and check-out, model sharing, branching and merging, and an Enterprise Data Dictionary.
ER/Studio Enterprise builds on Pro with governance features: business glossaries and terms, business term harvesting, full metadata and lineage import and export, Git integration, and integrations with Collibra and Microsoft Purview. Enterprise also brings Team Server Core, a web platform where teams can view, search and collaborate on models. Idera’s edition comparison notes that features marked for Team Server Core are available at an additional cost, so budget for that separately.
Some capabilities are shared across all three ER/Studio editions: macros and automation, compare and merge, data flow (ETL lineage) modeling and the AI Data Modeling Assistant. Idera’s full edition comparison is the best place to check a specific feature before you buy.
Both products follow the same pattern: modelers work in a desktop client and check models in and out of a shared data model repository. The differences are in where the line falls between editions and in how non-modelers participate.
With erwin, the step up is from Standard to Workgroup. Workgroup’s Mart repository handles versioning, conflict resolution and permissions, and the erwin Mart Portal runs on Windows Server. Quest’s product page also lists erwin Mart cloud SaaS options for teams that would rather not host the repository themselves. For business users, ER360 provides a browser view of models and metadata, so stakeholders can review designs without a desktop license.
With ER/Studio, the repository arrives one tier earlier in naming terms: Data Architect Pro already includes the central repository, branching and merging. That makes Pro a reasonable fit for a small team that wants shared models without the full governance stack. The web layer, Team Server Core, belongs to Enterprise. Git has also become part of the workflow: since version 20.3, ER/Studio Data Architect can connect to Git, and Git output is available in the Generate Database wizard and the Compare and Merge utility.
erwin also lists Git version control among its governance and collaboration features. If your engineers already review DDL in pull requests, both tools can now meet them there.
Database coverage is broad on both sides, and both vendors have spent recent releases on cloud data platforms rather than only on traditional relational engines.
Quest lists Oracle, MySQL, Microsoft SQL Server, PostgreSQL, MongoDB, Snowflake, IBM Db2, Apache Cassandra, MariaDB, Apache Hive, Databricks, Google BigQuery, Neo4j, Teradata, Parquet and JSON among erwin’s supported targets, plus Azure Synapse and Couchbase. Version 15.1 added Microsoft Fabric Lakehouse as a target and extended NoSQL modeling with data sources and a link tab for NoSQL models.
Idera lists SQL Server, Oracle, Snowflake, Databricks, Microsoft Fabric, PostgreSQL, MongoDB, Google BigQuery and Amazon Redshift on the ER/Studio site, with the full list in its technical specifications. Databricks support arrived across the product in version 20.2, and version 20.6 added object class switching for Databricks and BigQuery.
On the client side, ER/Studio Data Architect installs on Windows. erwin Data Modeler 15 supports Windows 10 and 11, and Quest’s system requirements page also lists several macOS versions, while noting that the release is not certified for macOS Sequoia. The erwin Mart Portal must run on Windows Server. If a large share of your modelers use Macs, check erwin’s current requirements against your fleet before you assume either product will work.
This is where the two products differ most in philosophy.
erwin is designed to sit inside Quest’s own governance stack. Workgroup can bulk-harvest models into the erwin Data Intelligence catalog and glossary, and version 15.1 added DM Connect for syncing the business glossary between Data Modeler and Data Intelligence. If your company already runs erwin Data Intelligence, or is evaluating it, that tight loop between physical models and governed business terms is a strong argument for staying with erwin.
ER/Studio Enterprise takes a more open approach. Idera highlights integrations with Collibra and Microsoft Purview for compliance and lineage tracking, alongside its own business glossary and metadata import and export. Version 20.7 included Purview-related enhancements. For a company that has already standardized on Collibra or Purview as its catalog, ER/Studio Enterprise plugs into that choice instead of asking you to adopt a second catalog.
Our guide to data governance and metadata management tools covers the catalog side of that decision in more detail.
Both vendors now ship AI data modeling features that turn natural-language requirements into starter models. The details differ.
Quest’s product page says erwin’s GenAI features auto-generate data models and database designs and catch code inconsistencies. The erwin Data Modeler 15.1 release, announced in September 2025, introduced AI-powered data modeling with two headline pieces: industry-specific modeling frameworks for sectors such as financial services, healthcare, retail, manufacturing and telecommunications, and AI-assisted model generation that converts natural-language descriptions into starter models and validates scripts before production use. Quest claims starter models come together 25% to 30% faster, which is a vendor figure worth testing on your own requirements. Quest’s public material does not say which large language models sit behind these features or which editions include them, so ask your account team.
Idera’s assistant is called ERbert. It takes plain-language business requirements and generates a logical data model with entities, attributes, relationships and business terms, which you then edit. The edition comparison lists the AI Data Modeling Assistant in all three editions. Idera states that ERbert uses OpenAI’s private API rather than the public ChatGPT interface, that prompts are not stored, logged or used for training, and that data is encrypted in transit. That level of disclosure helps when your security team has to approve an AI feature. ER/Studio’s site also mentions an RDF Semantic Generator for producing semantic assets from models.
In both products, AI output is a draft. It speeds up the first pass on a new subject area, but naming standards, keys and domain rules still need a modeler’s review.
erwin Data Modeler editions are offered with node-locked (workstation) or concurrent licensing, according to Quest’s edition page. Quest does not publish list prices on its product pages, so expect to go through sales or a reseller. Concurrent licensing can lower cost when many people model occasionally but few at once.
ER/Studio is sold as a per-user subscription. At the time of writing, Idera’s pricing page shows online subscription prices for Data Architect and Data Architect Pro, with Enterprise available by quote and multi-year discounts through sales. Prices exclude applicable taxes and can change, so confirm current figures on the vendor’s pricing page. Both vendors offer trials or demos, and running a real project through each one is the most reliable way to compare them.
You already run erwin Data Intelligence or plan to. Choose erwin Data Modeler Workgroup. Glossary sync and model harvesting into the catalog are the main reasons to keep everything in one vendor’s stack.
Your governance team standardized on Collibra or Microsoft Purview. ER/Studio Enterprise is the more natural fit, since those integrations are part of the product rather than a separate project.
You are a solo modeler or a small team on a known budget. ER/Studio Data Architect or Data Architect Pro gives you published subscription pricing and, with Pro, a shared repository without stepping up to the enterprise tier.
Many people need to read models but few need to edit them. erwin’s Navigator edition and ER360 portal are built for that split. ER/Studio covers the same need through Team Server Core in Enterprise.
Your models lean heavily on NoSQL or graph databases. Check both vendors’ current platform lists against your stack, but erwin’s published list is broader on Cassandra, Couchbase and Neo4j.
Your team uses Macs. ER/Studio Data Architect is Windows only. erwin lists some macOS versions, so check the current certification list before committing.
Whichever you pick, your model is only as useful as the databases it describes. If you are modernizing the platforms underneath, our list of data warehouse automation tools covers the next step from model to pipeline.
Quest Software owns erwin Data Modeler after acquiring erwin, Inc. around the start of 2021. Idera sells ER/Studio, which it took over when it acquired Embarcadero Technologies in 2015.
Yes. Quest lists Git version control among erwin’s collaboration features, and ER/Studio Data Architect added Git connectivity in version 20.3, with Git output in the Generate Database wizard and Compare and Merge.
Idera lists the AI Data Modeling Assistant, ERbert, in Data Architect, Data Architect Pro and Enterprise.
erwin offers the Navigator edition and the ER360 web portal. ER/Studio provides web-based model viewing and search through Team Server Core in its Enterprise edition.
No. Quest describes Quest Data Modeler as a cloud-based companion to erwin Data Modeler aimed at faster, lighter modeling, not as a replacement for it.
erwin Data Modeler and ER/Studio are both mature, capable enterprise data modeling tools, and either will handle complex logical and physical models across modern cloud platforms. The real decision comes down to packaging and ecosystem. erwin fits best when you want concurrent licensing, a read-only edition for model consumers and a tight loop with erwin Data Intelligence. ER/Studio fits best when you want published per-user pricing, a repository at the Pro tier and ready-made links to Collibra or Purview. Shortlist on those factors, then run a real subject area through both trials before you sign.