Magnolia CMS

Yes. Noice is a Magnolia Platinum Partner. Platinum is Magnolia's highest partner tier.

Our Magnolia practice is based in Melbourne, and implementation and support run in AEDT and AEST business hours.

Costs vary widely with the scope and complexity of the project. In the Australian market in 2026, first Magnolia builds for mid-market and enterprise organisations typically land between AUD 180k and AUD 600k excluding GST. The main drivers are 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, and discovery produces a fixed budget envelope before you commit to a build.

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 and autoscaling. 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 our own AI-assisted content migration tooling to move structured and unstructured content from Adobe Experience Manager, Sitecore, Drupal, WordPress VIP, Contentful and bespoke legacy systems into Magnolia. It 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.

The Victorian Collaborative Centre for Mental Health and Wellbeing: ongoing platform support and a zero-downtime 6.4 upgrade. Further references are available under NDA.

Yes. Support runs in Australian business hours with agreed response times by severity. After-hours cover for critical incidents can be added to an agreement.

Magnolia Cloud offers an Australian region. Where requirements are stricter, we deploy Magnolia on a customer-owned AWS account in ap-southeast-2, with logs, backups and replicas kept in Australia. We document the residency boundary in the architecture pack.