Skip to main content

The technology behind iCura

Microsoft Azure provides the technology foundation for iCura. Our architecture decisions focus on the needs of operational software: controlled access, maintainability and dependable information flows.

Platform

Microsoft Azure as the foundation

iCura is built on Microsoft Azure, Microsoft’s cloud platform. Azure supplies the infrastructure and platform services that iCura’s architecture is designed around.

Azure is a supplier relationship. It does not make Microsoft a parent company, partner or endorser of RIAConsult or iCura, and Azure’s own platform capabilities are not automatically controls implemented in iCura.

Which Azure services a deployment uses, and where it is hosted, depend on the deployment. We discuss these details directly with technical and procurement reviewers.

Information on this page reviewed 15 October 2026.

Architecture

Architecture at a glance

Our architecture goals are separation of concerns, controlled access and observability.

  1. 1. People and interfaces

    Authorised users reach iCura through web interfaces.

  2. 2. Application and API layer

    Applies business rules, workflows and access checks.

  3. 3. Authorised data services

    Hold operational information for the organisation it belongs to.

  • AI processing boundary

    AI-assisted features are kept separate, with defined inputs and human review of outputs.

  • Operational monitoring

    Health and error monitoring across the layers.

Simplified, conceptual view using generic service categories. It describes design intent and is not a deployment specification.

Engineering

Engineering stack

We keep the stack for this corporate website separate from the iCura product. Details of the iCura product stack are available for technical review on request.

This website

Next.js and React
Server-rendered pages and the enquiry form
TypeScript
Type-checked application code
Tailwind CSS
Styling and design tokens
Resend
Delivery of website enquiries by email

Integration

Integration approach

We do not promise that iCura connects to every system. Each integration starts with a structured assessment of the following.

  1. Step 1: Interfaces

    Identify the systems involved and how each one can share information.

  2. Step 2: Authentication

    Agree how systems prove their identity and what each is allowed to access.

  3. Step 3: Data mapping

    Match fields and meanings between systems, and agree what is in scope.

  4. Step 4: Error handling

    Decide what happens when information is missing, late or rejected.

  5. Step 5: Support responsibility

    Agree who monitors each connection and who fixes what.

Security

Security and operations

Security, access control and operational monitoring are designed in from the start. For our approach to AI accountability, data, access and assurance information, see Responsible AI and security.

Technical conversations

We are happy to discuss architecture, hosting and integration with your technical team, under appropriate confidentiality.