Kentico CMS in Australia: publishing in 2026
Considering Kentico for retail content? Compare current and legacy editions, then check publishing, headless delivery, hosting and security updates.
- Published
- Last updated
For an Australian retailer, Kentico CMS assessment starts with the installed product and version. Xperience by Kentico supports managed website content and headless delivery, but older Kentico installations have different features and support limits. Australian hosting availability also leaves your team with application-update responsibilities.
Identify the Kentico product and edition
Xperience by Kentico is Kentico’s current digital experience platform, combining content management with marketing capabilities. Identify it separately from Kentico Xperience 13 and older products labelled Kentico CMS or Kentico EMS. A familiar brand name doesn’t establish which documentation applies to an inherited website.
Record the product name and installed version from the administration interface, along with the licence tier and hosting arrangement. Ask the implementation provider to match those details to the running application. A sales proposal for a newer product doesn’t describe the software already serving your store.
Kontent.ai is a separate product and company. Kentico’s brand history explains the separation. A reference to “Kentico headless CMS” in old material can therefore describe a different product from a headless channel in Xperience by Kentico.
For the current product, the business-user documentation separates reusable content in Content hub from website pages and headless items. Website authors work with pages in a website channel. Headless delivery sends structured content to a separately built presentation, such as a storefront or mobile application.
Kentico’s headless-content guide identifies that functionality as requiring the Advanced licence tier. Editors create typed headless items and publish them for delivery. Its preview opens a configured target environment, where the consuming application renders the content. Budget for that preview implementation when choosing headless delivery.
Permissions also need configuration for the chosen edition. Current role management controls access to administration applications. Permissions from several roles combine, so a narrowly named editor role doesn’t restrict someone who also holds an Administrator role. Inspect each account’s effective access.
Publish retail guidance through controlled access
Keep retail rules in the CMS and changing product attributes in their authoritative catalogue. That prevents an edited guide from becoming a second price or availability record. Your publication flow must also distinguish approved content from a draft that an editor is still changing.
Consider a fictional retailer using Xperience by Kentico to publish a delivery guide for bulky furniture. The guide contains a stable identifier, delivery-area wording and an advice revision. It references catalogue product identifiers for eligible items. Product dimensions and current availability remain in the catalogue.
The retailer configures a review step between editing and publication. Kentico’s workflow documentation describes custom steps between Draft and Published, with roles assigned to each step. Give editors permission to prepare the wording and reviewers permission for the final approval. Reserve workflow-wide control for accounts that need it.
Trace the proposed flow through a test environment:
- An editor changes the guide from “doorstep delivery” to “delivery to the nominated ground-floor room”. Save the change for review.
- The reviewer opens the preview and checks the wording against the retailer’s actual delivery service. Public delivery must still show the previously approved revision.
- A permitted publisher approves the new guide. The storefront’s delivery service retrieves the published content and refreshes its cached copy.
- Reload a product page and ask the connected answer service the same delivery question. Confirm both use the new advice revision and the matching product identifier.
- Try the publication action with an account restricted to editing. Confirm it cannot bypass the configured review step.
For headless delivery, Kentico’s retrieval documentation requires an enabled API key for the channel. Keep that credential behind a server-side delivery layer. A key embedded in public browser code is visible to visitors.
Expose only the approved guidance the customer needs. Staff notes and customer records don’t belong in the public answer source. If a guide references other content, check that the published response contains the intended versions of those items too. A successful page publication doesn’t prove that a downstream cache or answer service has refreshed.
Check hosting, updates and vulnerabilities
Xperience by Kentico supports managed software as a service (SaaS) and private-cloud deployment. For Australian teams, Kentico’s SaaS overview lists Australia East and Australia Southeast among the available regions. Region selection doesn’t establish that every operational record stays in Australia: the same document describes portal data and some logs stored in Europe.
Under SaaS, Kentico maintains the hosting environment and its supporting services. Your team or provider still develops and deploys the project, including its application hotfixes and refresh updates. Assign that work explicitly in the support agreement. “Managed hosting” must never leave the application itself without an update owner.
With private-cloud hosting, assign infrastructure operation and recovery as well as application maintenance. Include the database and uploaded assets in the recovery plan. Kentico’s deployment options describe the hosting choices, but the retailer’s contract must say who responds when the storefront or content delivery fails.
Use the correct official security path for the identified product. Xperience by Kentico has a security-advisory register. Kentico Xperience 13 has its own hotfix listings. Compare the installed version and configuration with each applicable advisory’s affected scope and remedy.
A published advisory describes a reported issue and its affected conditions. It isn’t a scan of your retailer’s deployment. Likewise, finding no matching advisory doesn’t prove that custom code, permissions or the hosting configuration are secure. Commission any deployment assessment against an agreed scope and retain its actual findings separately from the vendor’s notices.
Follow the project-update procedure with a restorable backup of the database, application and assets. Apply and test updates in an isolated environment first. Recheck editorial permissions and the delivery-guide flow before the production release, with an agreed recovery path if the update fails.
Choose the implementation and support route
Choose a provider that can own your actual Kentico edition and its content-delivery path. The implementation scope must cover content modelling, catalogue references and preview behaviour. The support scope must also name who handles account access, failed deliveries and application updates after launch.
For a current-edition tutorial, start with Kentico’s administration-interface guide in a disposable learning project. Open your project’s authorised administration address, identify its product version and find the channel applications. Then create a sample delivery guide and run the controlled publication flow. This checks the workflow your team needs instead of copying instructions for an older interface.
For a forgotten password, use the project’s own sign-in page and its Forgotten password action. Kentico’s user-management instructions require access to the account’s email address, with email delivery and the system service domain configured. If the recovery email doesn’t arrive, an authorised administrator must inspect those settings and the event log. An unrelated Kentico portal login won’t recover a retailer’s project account.
Kentico’s buying guide bases licensing on channels and licence tier, with SaaS and optional AI packages affecting the configuration. Standard targets single-channel web projects, while Advanced supports the broader multichannel scope. Obtain a quote for the exact channel mix and deployment, with the currency, billing period and tax treatment stated.
Compare that quote with implementation and continuing maintenance costs. A private-cloud option adds hosting operations to the retailer’s responsibilities. SaaS reduces infrastructure work, while application updates and integration support still need funding. Include preview development and recovery testing in the provider’s scope so those tasks don’t emerge after the licence purchase.
For an inherited installation, use Kentico’s support-lifecycle policy to trigger an upgrade assessment. The policy limits Xperience 13 releases to security hotfixes during 2026 and ends its support as 2027 begins. Earlier versions have separate expired support windows. Assess custom modules and content migration before committing to more work on an unsupported edition.
Approve the implementation once your team can identify the running edition, assign its update owner and trace an approved guide to the customer’s answer. Retain the rejected-draft and restricted-editor checks as part of that acceptance, alongside the recovery procedure.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.