AI Custom Fields Builder
Public Roadmap — Field Forge
We publish our roadmap so you know what you’re buying into. Below is what we’re actively building, what’s queued next, what we’re considering, and what we’ve recently shipped. Vote on features you want prioritized.
In progress (shipping within 4–8 weeks)
Migration tools
- Pods importer improvementshandle Pods’ custom database tables feature properly
- Toolset Types importerconvert Toolset Types field groups to Field Forge
- Enhanced CMB2 importerbetter handling of complex CMB2 container types
AI features
- AI field type suggestionsas you type a field label, AI suggests the appropriate field type (“date of birth” → date picker)
- AI field group optimizationanalyze an existing field group and suggest improvements
- Multi-language AI generationgenerate field groups in other languages (for Lang Forge users)
Performance
- Query builder for archives — optimize how repeater fields are loaded for archive pages
- Async field loading — lazy load field values for fields not needed on initial render
Developer tooling
- WP-CLI expansionmore commands for bulk operations on field groups
- CI/CD recipesdocumented GitHub Actions and GitLab CI templates for deploying field groups
- Schema diff visualizerbetter UI for comparing field group revisions
Queued (3–6 months)
New features
- Multi-site field group sharingdefine field groups once, use across a WordPress multisite network
- Role-based field accesshide specific fields from specific user roles
- Field-level validation APIcustom validation logic per field via PHP hooks
- Frontend field rendering helperspre-built templates for common field display patterns
- Import/export via REST APImigrate field groups between sites via API calls
Integrations
- Headless WordPress SDKnpm package with Field Forge types and utilities
- Gatsby source pluginofficial Field Forge data source for Gatsby sites
- Next.js WordPress templateNext.js starter template with Field Forge pre-configured
- Astro integrationofficial Astro integration for Field Forge
Enterprise
- White-label modehide Field Forge branding from clients (Agency plan)
- Audit logwho changed what, when (for compliance-heavy environments)
- Bulk user permissionsrole-based permissions across field groups
- Custom post type managervisual CPT registration alongside field groups
Under consideration
Features we’re thinking about but haven’t committed to. User interest affects prioritization.
AI expansions
- AI content generationgenerate sample content for custom fields during development
- AI schema documentationauto-generate markdown docs for field groups
- AI migration assistanceinterpret complex custom code and suggest Field Forge equivalents
Advanced field types
- Polygon fielddraw polygons on a map
- Signature fieldtouch/mouse signature capture
- Rich media fieldsvideo, audio, 3D model support
- Ranking fielddrag-to-sort ordered lists
- Matrix fieldtable of values with custom column types
Content workflows
- Draft versions of field datasave field values as drafts before publishing
- Approval workflowsrequire editor approval before field changes go live
- Scheduled field updateschange field values on a schedule
- Field lockingprevent editing of specific fields after first save
Headless enhancements
- Real-time syncWebSocket updates when WordPress content changes (for live frontends)
- Delta APIreturn only fields that changed since last fetch (efficient polling)
- GraphQL subscriptionsreal-time GraphQL updates
Recently shipped
Version 2.3.0 (April 2026) [Major]
- SCF import tool (WordPress.org ACF fork)
- Beta/manual migration planning paths for CMB2 and Carbon Fields
- 12 built-in AI schema templates
Version 2.2.0 (March 2026)
- AI schema generation
- Schema versioning with rollback
- Auto-preload on archive pages
Version 2.1.0 (February 2026)
- TypeScript generation
- GraphQL SDL and WPGraphQL auto-registration
- Local JSON Sync bidirectional mode
Version 2.0.0 (January 2026)
- Initial public release
- 32 field types
- Custom table storage
- ACF compatibility layer
How we prioritize
Our roadmap is driven by three inputs:
- What customers request most — we track feature requests from support tickets and the contact form. Popular requests move up.
- What differentiates Field Forge — features that set us apart from ACF, SCF, and other alternatives (AI, headless, custom table, schema versioning).
- What the team can ship well — we’d rather ship a polished feature later than a rushed feature now.
If something isn’t on the roadmap but is important to you, tell us. Aligned ideas often move quickly.
Vote on features
Tell us which roadmap items matter most for your project. High-demand items get prioritized.