Bright, airy photograph of a sunlit office corridor with pale blue walls and soft natural light

IT services, applications & training for French businesses

Aricie is the business portal for @RICIE.NET — DotNetNuke solutions, custom software, and professional training delivered from offices across France.

Explore the Portal

Browse the four main areas of the Aricie business portal.

Featured Applications & Services

Software products developed and supported by Aricie.

Soft cyan square tile with gentle gradient light, neutral and clean
Application

Acoléa

Specialized software application in the Aricie catalog.

Pale blue square tile with diffused daylight glow
Application

Adylic

Specialized software application in the Aricie catalog.

Minimal green square tile with airy white space
Application

AricieGrid

Specialized software application in the Aricie catalog.

Bright neutral square tile with subtle texture
Application

Budg-Immos

Specialized software application in the Aricie catalog.

Our French Offices

Headquarters in Mureils with branches in Paris, Lyon, and Grenoble.

DNN community support vs. commercial support: which do you need?

Choosing between DNN community support and a paid support partner depends on the importance of your portal, the skills available internally, and the consequences of downtime. A small association site may manage well with user forums and internal troubleshooting, while a customer-facing platform may need guaranteed response times and specialist intervention.

DNN, formerly known as DotNetNuke, remains a practical foundation for content management, intranets, partner portals and business applications. Its community offers valuable knowledge, documentation and shared experience. Commercial support adds structured maintenance, architectural advice, security planning and accountability when a problem affects daily operations.

For Australian organisations, distance and operating hours can influence the decision. A business in Perth working with a European provider may need clear escalation arrangements, while teams in Sydney, Melbourne or Brisbane may prefer support that overlaps with Australian business hours. The right model should fit operational risk rather than simply the size of the website.

Aricie combines DNN expertise with custom software development and professional training. That broader capability matters when a portal connects to internal systems, manages business processes or supports professional partners across multiple locations.

What community support provides

DNN community support is usually built around forums, documentation, shared modules, developer discussions and advice from experienced users. It can be highly effective for familiar tasks such as configuring content permissions, diagnosing a simple module issue or understanding a standard upgrade path.

This route suits technically confident teams with time to investigate problems. It can also be appropriate for a low-risk information site where an issue can wait until the next working day. The main cost is staff time: finding a reliable answer, testing it safely and documenting the fix may take longer than expected.

Community resources are especially useful during early evaluation and routine administration. They help internal teams learn the platform and avoid unnecessary dependence on an external provider. However, community guidance generally does not create a service-level agreement, guarantee a fix or assume responsibility for the result.

Where commercial support earns its cost

Commercial DNN support gives an organisation a defined point of accountability. Depending on the agreement, this may include monitoring, incident response, patch management, backups, performance reviews, upgrade planning and assistance with integrations. A provider can also examine the wider application rather than treating each error as an isolated ticket.

The value becomes clearer when a portal supports sales, member services, customer records or time-sensitive workflows. A failed authentication service on a Monday morning in Melbourne can affect staff across Australia, and an unavailable partner portal may delay work for many businesses. Fast diagnosis and controlled recovery can cost less than prolonged internal troubleshooting.

Paid support can also reduce technical debt. Specialists may identify unsupported extensions, insecure configurations, inefficient database queries or custom code that will complicate a future DNN upgrade. This is different from purchasing a generic help desk service: the provider should understand the site’s architecture and business purpose.

Australian factors to consider

Australian businesses often operate across wide time zones, from Perth to Sydney and Melbourne, with teams in Brisbane, Adelaide or regional centres. Confirm whether support is available during Australian working hours, how after-hours incidents are handled and where escalation occurs. A European partner can still be suitable, but response windows must be explicit.

Privacy and data handling deserve careful review. If the portal stores personal information, customer documents or employee records, ask how backups, logs and remote access are managed. Australian Privacy Act obligations, contractual requirements and sector-specific rules may affect where data is hosted and who can access production systems.

Local working practices matter as well. A retailer preparing for Boxing Day, a university managing enrolments, or a professional services firm approaching the end of the financial year may have periods when even a short outage is unacceptable. Support planning should reflect these peaks, along with Australian public holidays and planned maintenance windows.

Matching support to your portal

Start by classifying the portal’s business impact. A public brochure site may need occasional advice, while an authenticated intranet or customer platform may require proactive monitoring and a tested recovery plan. Consider the number of integrations, the complexity of custom modules and the availability of internal DNN knowledge.

Review the support provider’s technical scope rather than relying on broad promises. Ask whether the team handles DNN upgrades, .NET dependencies, database performance, security hardening, content permissions and third-party extensions. If the portal includes document publishing or format conversion, establish how files are validated before entering automated workflows; document conversion guidance can help teams understand why source preparation matters.

Training may be a better first investment than a full managed service for some organisations. A short programme can give administrators confidence with publishing, roles, workflows and basic diagnosis, while a commercial partner remains available for complex incidents and major changes.

Questions to ask before signing

A useful evaluation focuses on evidence. Request examples of comparable DNN portals, explanations of the escalation process and details of what is included in the monthly fee. Clarify whether development work, emergency fixes, cloud infrastructure and third-party licence costs are billed separately.

Check how the provider approaches change management. Production updates should be tested, backed up and scheduled around business activity. You should also know who approves changes, how rollback works and whether the provider records configuration decisions for future administrators.

The support relationship should be understandable to non-technical managers as well as developers. Reports should explain incidents in terms of business effect, response time, root cause and preventive action. This creates a useful record when budgets, compliance reviews or renewal decisions arise.

A practical support checklist

Use the following points to compare community-led and commercial arrangements:

  • Define the maximum acceptable downtime for each DNN site.
  • List the integrations, custom modules and external services that need specialist knowledge.
  • Confirm Australian-hours coverage, after-hours escalation and public holiday arrangements.
  • Check backup frequency, restoration testing and access controls.
  • Ask for clear service levels covering response, resolution and communication.
  • Separate routine administration, development projects and emergency work in the contract.
  • Include administrator training and documentation in the support plan.

Making the decision with confidence

Community support is a sensible option when the portal is low risk, the team has relevant skills and the organisation can tolerate slower resolution. It keeps costs controlled and encourages internal capability, especially when administrators use the DNN ecosystem regularly.

Commercial support is more appropriate when the portal is operationally important, highly customised or connected to sensitive data. A blended model often works well: internal staff manage content and straightforward configuration, while a specialist partner handles upgrades, security, integrations and urgent incidents.

Assess your DNN environment against business impact, internal capability and Australian operating requirements. Aricie can bring together platform expertise, custom development and professional training to help establish a support model that is proportionate, documented and ready for the next stage of your portal’s growth.