Ultivo Toolkit is the toolkit you reach for on every build. Instead of installing a field plugin, a form plugin, an SEO plugin and a handful of one-trick utilities, you get them in a single plugin that shares one interface, one set of conventions and one place to switch things on and off.
Pro adds Blueprints, Flexible Content and the Clone field, and is available at wpultimate.org. Launch offer: 10% off your first year with code LAUNCH10, until 30 September 2026.
Every part is optional. Turn off what you do not need under Ultivo Toolkit Settings and it registers nothing at all: no menus, no screens, no hooks. Nothing you built disappears when you do: the data stays put and comes back the moment you switch the feature on again.
Nothing is sent to us, ever. Two features do reach an outside service: spam protection, if you turn it on, and the map preview in the admin. Both are described under External services below.
Custom fields
Build field groups in a visual builder and attach them to anything with location rules.
uploads/ultivo-json/ and also read from {theme}/ultivo-json/, so they can travel through version control, with a Sync button when a file is newer than the databaseForms
SEO
Enough to launch a site with, and nothing more. No traffic lights, no scores.
%title% and %sitename%, and a live preview of the Google resultSite enhancements
Seventeen switches for the things you set up on every site: cleanup of the <head>, disabling comments, the classic editor, maintenance mode, SVG and AVIF uploads, login branding, duplicating posts, a custom login URL, manual content ordering, disabling components you do not use, limiting login attempts, revisions and Heartbeat, redirects with a 404 log, admin columns, SMTP and a full admin menu organiser. All off by default.
For developers
ultivo_field( 'title' ) for one value (with an optional default), and ultivo_rows( 'blocks' ) to loop over a repeater or flexible content. A whole flexible field renders in one line: ultivo_rows( 'blocks' )->render( 'template-parts/blocks' )ultivo_get_field(), ultivo_the_field(), ultivo_have_rows(), ultivo_the_row(), ultivo_get_sub_field(), ultivo_get_row_layout(), ultivo_update_field(), ultivo_add_row(), ultivo_add_options_page()ultivo_add_local_field_group(), or exported as PHP from the Tools pagefield_name plus a hidden _field_name pointing at the field key; repeater rows as name_0_subname. Nothing is serialised into a blob, so WP_Query, get_post_meta() and SQL all keep working.ultivo_register_block_type() and render through a template or callback. Registering is code-only for now, and the block sidebar handles the simple field types (text, number, select, radio, true/false and colour), while the rest is best edited in a field group.Coming from ACF?
Ultivo Toolkit stores values in exactly the pattern ACF uses, and Tools Migrate from ACF converts your field groups from the database and from the theme’s acf-json folder. Field keys are preserved, so your existing content keeps working and your templates keep returning the same values. Migration is a feature here, not the point of the plugin. You are not buying a copy of something else.
This plugin connects to two kinds of outside service, and both are listed in full below. Spam protection runs only when you pick a provider and enter its keys; the map preview runs only in the admin, on posts where you use a Map field. Nothing else leaves your site, and nothing is sent to us.
Google reCAPTCHA (v2 and v3)
Used to tell human visitors from bots when you enable it for your forms. On any page that shows a form with reCAPTCHA enabled, the reCAPTCHA script is loaded from Google. When a visitor submits that form, their reCAPTCHA token and IP address are sent to Google for verification.
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy
Cloudflare Turnstile
An alternative to reCAPTCHA with the same purpose. On any page that shows a form with Turnstile enabled, the Turnstile script is loaded from Cloudflare. When a visitor submits that form, their Turnstile token and IP address are sent to Cloudflare for verification.
Terms: https://www.cloudflare.com/website-terms/
Privacy: https://www.cloudflare.com/privacypolicy/
OpenStreetMap
Used only by the Map field, and only in the WordPress admin. When you edit a post
that has a Map field, the plugin embeds a map preview from openstreetmap.org in an
iframe, with the coordinates you entered in its URL. Nothing is sent for visitors:
the Map field is not available in forms, so this never runs on your public pages.
Terms: https://osmfoundation.org/wiki/Terms_of_Use
Privacy: https://osmfoundation.org/wiki/Privacy_Policy