Magnolia CMS in Australia

Our Magnolia practice is led out of Melbourne with engineers in Sydney and Wellington. All implementation and ongoing support runs in AEDT and AEST business hours, with on-call cover for production incidents. We work with Australian, New Zealand and APAC clients and have not offshored the practice.

We charge against our 2026 rate card (AUD 165 to AUD 275 per hour or AUD 1,320 to AUD 2,200 per day, ex GST), and most first Magnolia DX Core or Magnolia Cloud builds for Australian mid-market or enterprise clients land between AUD 180k and AUD 600k excluding GST. The range depends on template count, integrations, authoring patterns and migration scope. Magnolia licence fees are negotiated separately with Magnolia and are usually annual subscription based. We share an itemised range at the end of a one-hour scoping call.

Yes. We deliver onto Magnolia Cloud (PaaS), Magnolia on AWS in ap-southeast-2 (Sydney), and customer-managed Kubernetes. Magnolia Cloud is the default recommendation for new builds because the platform team handles patching, autoscaling and SLA-backed uptime. We retain customer choice on data residency and review the trade-off case by case for regulated workloads.

For a single-author, single-environment Magnolia instance the upgrade window is two to four weeks of engineering. Multi-region, multi-instance estates (Author plus public clusters plus DR) typically run six to ten weeks including regression testing and content freeze windows. Most of the work is bundle compatibility, custom module review and Java version alignment, not the core upgrade itself.

Yes. We use noice Migration Accelerator, our AI-assisted content migration tool, to move structured and unstructured content from Adobe Experience Manager, Sitecore, Drupal, WordPress VIP, Contentful and bespoke legacy systems into Magnolia. The accelerator handles snapshot capture, template mapping and bulk publish, while content authors keep final approval on every page.

Both. Magnolia supports a hybrid model where you can choose per page whether to render server-side from Magnolia or expose content through the Magnolia REST and GraphQL APIs to a downstream frontend such as Next.js, Nuxt or a native mobile app. We default to hybrid because it gives marketing teams visual editing without locking engineering out of headless when they need it.

Recent and current Magnolia engagements include Telstra Health (managed services and platform support), Victorian Council of Community Mental Health and Wellbeing (VCCMHW, full DX Core build), and MM Plastics and Dotmar (multi-brand, multi-region DXP). We can share named references and architecture summaries under NDA.

Yes. We run dedicated Magnolia support pods with response-time SLAs aligned to your business hours, including 24x7 P1 cover for clients on the enterprise tier. The same engineers who build your platform stay on it, so context does not get handed to a separate support team after go-live.

Magnolia Cloud offers an Australian region. For clients with stricter requirements (APRA CPS 234, IRAP, Defence) we deploy Magnolia on a customer-owned AWS account in ap-southeast-2 with logs, backups and replica instances kept in Australia. We document the residency boundary as part of the architecture pack so security teams can sign off without a separate review.