JetEngine

JetEngine is Crocoblock’s dynamic-content plugin for WordPress. It is built for sites that need custom post types, custom content types, fields, relationships, listings and complex queries without turning every data-driven feature into custom PHP.

What JetEngine covers

JetEngine can create custom post types, taxonomies, custom fields and custom content types. It also provides relationship tools for connecting posts, users, terms and CCT items. This lets site builders model directories, listings, member areas, catalogs and other structured-content projects inside WordPress.

The plugin works with Elementor, Gutenberg, Bricks and Divi. That cross-builder support matters because the same data model can feed listing templates and dynamic elements even when the visual layer changes.

Listings and Query Builder are the main difference

Many field plugins stop after storing structured data. JetEngine also includes tools for querying and displaying that data. Query Builder can work with posts, users, terms, comments, SQL data and REST API sources, while listing templates turn results into reusable front-end cards or rows.

This reduces the need to combine a field plugin with separate query and listing extensions. The trade-off is that JetEngine has more moving parts to learn and maintain.

Content modeling options

Custom post types and taxonomies. You can register structured WordPress content without writing registration code.

Custom fields. JetEngine provides multiple field types for posts, users, terms and other supported objects.

Custom Content Types. CCTs can store structured records in dedicated database tables rather than placing every record in the standard posts table.

Relationships. One-to-one, one-to-many and many-to-many connections can link different content entities and feed listings or queries.

Options and glossaries. Reusable data sources can support settings pages, select fields and repeated structured values.

Dynamic output and account workflows

JetEngine includes dynamic visibility controls, listing components, profile-building tools and user-facing account structures. These features can support membership directories, front-end dashboards, user profile pages and role-based content experiences when configured carefully.

Tables, charts and map-related workflows are also part of the wider JetEngine feature set. Some advanced front-end experiences work best alongside other Crocoblock plugins such as JetSmartFilters or JetFormBuilder, so buyers should distinguish what JetEngine itself provides from what requires another JetPlugin.

Where JetEngine is more complex

The main cost is configuration depth. ACF, Meta Box or Pods can be easier when the requirement is simply to add fields to posts and render them in a theme. JetEngine becomes more valuable as relationships, listings, reusable queries and front-end dynamic systems become central to the project.

Because it can define core site data structures, switching away later needs planning. Export the field structure, identify queries and relations, map listing templates, and test any builder-specific dynamic tags before replacing the plugin.

For agency work, that breadth can reduce plugin sprawl when the same project needs structured data, reusable listings, user-facing records, and complex filters. The trade-off is architectural commitment: naming conventions, field keys, relations, and queries become part of the site model, so documenting them is important before handing the project to another developer or editor.

JetEngine can also be a practical middle ground for teams that want visual configuration but still need a structured data model that developers can reason about. The Query Builder and relationship system mean a site can grow from a simple directory into more connected workflows without immediately replacing its underlying content model. That makes early planning important: decide which data belongs in posts, custom content types, users, or taxonomies before building front-end listings around it.

Pricing

Pricing checked: September 26, 2026. Crocoblock lists JetEngine at $75 per year for a one-site custom subscription, with a current promotional price also displayed on the product page. The subscription includes the plugin, updates and support for the subscription period. Crocoblock also sells broader All-Inclusive plans containing JetEngine and other JetPlugins. A 30-day money-back guarantee is listed.

PluginSuggest verdict

JetEngine occupies a broader category than a traditional custom-fields plugin. Its value is strongest when data modeling and dynamic presentation are both required. For narrower structured-content projects, compare Advanced Custom Fields, Meta Box, Pods and Secure Custom Fields.

Architecture and migration planning

JetEngine can become part of the site architecture rather than just an editor add-on. Custom Content Types can move structured records into dedicated database tables, while relationships, Query Builder queries, Profile Builder pages, and listing templates can all depend on the same field keys and object IDs. Document those dependencies before a project grows beyond a simple directory or catalog.

For migrations, inventory each content type, taxonomy, meta field, relation, custom query, listing template, dynamic visibility rule, and builder-specific dynamic tag. Moving only the post data is not enough if the front end depends on JetEngine listings or custom SQL queries. A staging migration should prove that relationships, pagination, filters, user-facing dashboards, and any REST-powered records still return the expected objects.

JetEngine 3.8.14.1 is the latest release I could verify from Crocoblock’s August 2026 update history. That release also included security-related hardening for Timber Views, which is a reminder to keep dynamic-content plugins updated when they process user-controlled values or custom queries.

Frequently asked questions