Plans that grow with your data landscape

All three plans — Community, Standard and Enterprise — are available through the Microsoft commercial marketplace, so billing goes through your existing Azure agreement.

Yes. The Community plan is free of license cost and gives you one project with up to twenty entities, which is enough to evaluate the full modeling stack.

A project is a logical container for one modeling effort. It holds its own logical model, dictionary, flows, physical models, tasks and version history, so separate initiatives, clients or products stay cleanly apart. Projects are isolated from one another: objects in one project cannot directly reference or interact with objects in another, and content moves between projects only through explicit import and export. Access is granted per project, so members only see the projects they have been assigned to.

Community allows one project with a maximum of twenty entities. Standard allows two projects with a maximum of two hundred entities each. Enterprise allows six projects with an unlimited number of entities.

Enterprise includes half an hour of optional support work per month. Beyond that, and on the Standard plan, additional support work is available at 60 USD per half hour.

Yes. You can import existing schemas and spreadsheets as a starting point, then refine the model from there.

Yes. Model One imports ER/Studio DM1 files directly, bringing over entities, attributes, primary and alternate keys, relationships, definitions, submodels, physical table and column names and types, data sources, and Data Lineage diagrams as Flows. If you work in another tool, you can also import SQL DDL scripts, including SQL Server Management Studio output, as well as DBML files from dbdiagram.io and similar tools. Complete Model One projects move between environments as a full JSON export and import.