Appearance
Coming from Cockpit / v3
Already familiar with the AX NLG Cloud and the Cockpit? This guide explains what changed in axite and how the Content Engine simplifies your data processing.
axite vs Cockpit
Throughout the reference you'll find boxes like this noting differences between Cockpit and axite.
What's new in axite
axite introduces the Content Engine, which replaces projects as the organizing structure. It drastically reduces up-front data processing and the uploading of duplicate data: you no longer upload your data into different collections or projects just to get texts in different languages or for different use cases. Collections are gone — you upload your data once and generate many different texts from it.
Learn more in the Content Engine documentation.
Rulesets are unchanged
How you write rulesets hasn't changed. The Composer UI works exactly as before, and you can import existing Cockpit rulesets without changes. Rulesets keep their name — the only difference is you can now have several rulesets per Content Engine, instead of exactly one per project.
How Cockpit concepts map to axite
Team → Organization
Renamed to "organization", with the same role: organizing users and their access. Subscription and billing are bound to the organization.
Project → Content Engine
Content Engines replace projects as the organizational unit, but are much more powerful. (In the API and URLs they're still called pipeline.)
Ruleset → Ruleset (unchanged)
Same concept, same Composer UI and functionality — you can now have several per engine.
Collection → Data Pool
Collections are no longer needed to control which language a text is generated in. If you have several data types you don't want mixed, use separate data pools — but you'll need far fewer than you had collections. With only product data and no secondary data (like a brand list), one data pool is enough.
Document → Upload + Object + Result
In Cockpit, a document held both your uploaded data and the generated text. axite splits this into three: