Konstrukt vs UI-O-Matic

Differences between Konstrukt and UI-O-Matic, the back office UI builders for Umbraco.

For anyone familiar with Umbraco you may already know of the open source back office UI builder, UI-O-Matic and be wondering why you should choose Kostrukt instead. To help with that decision, we've put together the following feature matrix to compare some of their major differences.
API
Feature
Konstrukt
UI-O-Matic
Style
Fluent API
Attribute based API
Strongly Typed
Yes
No
Seperation of Concerns
Yes - Config is seperate to poco models
No - Config is combined with the poco models
Manage 3rd Party Models
Yes - As config is seperate to poco models, Konstrukt can manage any poco models
No - As config is attribute based, you need to have full control of poco models to add attributes to
Configuration Context
Config is always in the context of the poco model with Konstrukt automatically converting between properties and DB columns
Config switches between poco model properties and DB columns so can be confusing if you aren't aware of the context
Supports Dependency Injection
Yes - Where types are passed to the API, the service provider is used to resolve those types allowing for dependency injection of depdendencies
No
Features
Feature
Konstrukt
UI-O-Matic
Dashboards
Yes
No
Context Apps
Yes
Ish - There is an API to define context apps, but it's just a shortcut for Umbraco's Content Apps API, so doesn't support associating a collection with the context app
Sections
Yes
Yes - Requies custom tree controller
Section Dashboard
Yes
Yes
Cards
Yes
No
List View Filters
Yes - Data Views and Property Filters
Yes - Dropdown filter only
List View Field Views
Yes
Yes
Field Editors
Konstrukt re-uses Umbraco property editors and so can use the full suite of core and community property editors
Limited to a set of UI-O-Matic provided editors
Editor Organisation Structures
Tabs + Fieldsets
Tabs
Editor Validation
Yes
Yes
Menu Actions
Yes - C# based
Yes - JS based
Bulk Actions
Yes - C# based
No
Row Actions
Yes - C# based
No
Virtual Sub Trees
Yes
No
Custom Trees in Existing Sections
Yes
No
Encrypted Properties
Yes
No
Value Mappers
Yes
No
Child Collections
Yes
Yes - Requires a convoluted config of hidden collections + list view properties on the parent poco model
Custom Repositories
Yes
Yes
Events
CRUD + Query + Startup events
CRUD + Query events
Data Export
Export Bulk/Row action available OOTB
Via 3rd party add-on
Property Editors
Entity Picker
Dropdown + Multi Picker
Localized
No
Yes
Supported Umbraco Versions
v10+
v7+
License
Feature
Konstrukt
UI-O-Matic
Open Source
No
Yes
Can be used on Umbraco Cloud
Yes
No
Fee
Free for one collection, then £450 exc VAT per install
Free unless you are a paid Umbraco Partner then you are required to negotiate a fee or face a $15,000+ penalty
Support
Feature
Konstrukt
UI-O-Matic
Supported by
Outfield Digital Ltd + Community
Community
Our Umbraco Forum
Yes
No
Email Support
Yes - Commercial
Yes - Personal
Issue Tracker
Yes
Yes
Documentation
Yes
Yes

Feature	Konstrukt	UI-O-Matic
Style	Fluent API	Attribute based API
Strongly Typed	Yes	No
Seperation of Concerns	Yes - Config is seperate to poco models	No - Config is combined with the poco models
Manage 3rd Party Models	Yes - As config is seperate to poco models, Konstrukt can manage any poco models	No - As config is attribute based, you need to have full control of poco models to add attributes to
Configuration Context	Config is always in the context of the poco model with Konstrukt automatically converting between properties and DB columns	Config switches between poco model properties and DB columns so can be confusing if you aren't aware of the context
Supports Dependency Injection	Yes - Where types are passed to the API, the service provider is used to resolve those types allowing for dependency injection of depdendencies	No

Feature	Konstrukt	UI-O-Matic
Dashboards	Yes	No
Context Apps	Yes	Ish - There is an API to define context apps, but it's just a shortcut for Umbraco's Content Apps API, so doesn't support associating a collection with the context app
Sections	Yes	Yes - Requies custom tree controller
Section Dashboard	Yes	Yes
Cards	Yes	No
List View Filters	Yes - Data Views and Property Filters	Yes - Dropdown filter only
List View Field Views	Yes	Yes
Field Editors	Konstrukt re-uses Umbraco property editors and so can use the full suite of core and community property editors	Limited to a set of UI-O-Matic provided editors
Editor Organisation Structures	Tabs + Fieldsets	Tabs
Editor Validation	Yes	Yes
Menu Actions	Yes - C# based	Yes - JS based
Bulk Actions	Yes - C# based	No
Row Actions	Yes - C# based	No
Virtual Sub Trees	Yes	No
Custom Trees in Existing Sections	Yes	No
Encrypted Properties	Yes	No
Value Mappers	Yes	No
Child Collections	Yes	Yes - Requires a convoluted config of hidden collections + list view properties on the parent poco model
Custom Repositories	Yes	Yes
Events	CRUD + Query + Startup events	CRUD + Query events
Data Export	Export Bulk/Row action available OOTB	Via 3rd party add-on
Property Editors	Entity Picker	Dropdown + Multi Picker
Localized	No	Yes
Supported Umbraco Versions	v10+	v7+

Feature	Konstrukt	UI-O-Matic
Open Source	No	Yes
Can be used on Umbraco Cloud	Yes	No
Fee	Free for one collection, then £450 exc VAT per install	Free unless you are a paid Umbraco Partner then you are required to negotiate a fee or face a $15,000+ penalty

Feature	Konstrukt	UI-O-Matic
Supported by	Outfield Digital Ltd + Community	Community
Our Umbraco Forum	Yes	No
Email Support	Yes - Commercial	Yes - Personal
Issue Tracker	Yes	Yes
Documentation	Yes	Yes

Last modified 10mo ago