01 / CONTEXT
What the platform does
iAureo Platform provides reusable services that external business applications can consume without implementing those capabilities themselves. Its main areas are reporting and document editing, transactional email and a separate user identity service.
An application sends data and a report definition to the API, receives the addresses needed to open the viewer or editor, and uses the same service boundary to load or save the document. Email follows another reusable workflow: the application queues a message and a background service handles delivery using the client's configured sending account.
These services are in production and continue to evolve. iAureo Platform is distinct from iAureo Agents Platform: this project focuses on shared application services, while the agents platform addresses AI execution, tools and workflow supervision.
02 / THE CHALLENGE
The problem to solve
Business applications repeatedly need document generation, editable reports and transactional messages. Rebuilding those capabilities inside each product creates separate integrations, separate deployment concerns and several places to maintain the same behaviour.
The platform's challenge was to expose reusable services through a consistent boundary while also supporting existing .NET Framework applications. Modernisation therefore had to accommodate different runtime generations and distinguish an application's service credentials from a person's user session.
03 / THE SOLUTION
How it works
Reporting as a service
The client application submits a report and its data through the API. The service stores its definition, branding and data sources, then returns links for viewing or editing. The reporting module retrieves and saves those definitions through the same API, keeping report storage out of the application's user interface.
Several document workflows
DevExpress-based modules provide a report viewer and designer alongside Word and Excel editing. Document export supports PDF and spreadsheet formats through the reporting engine. Updates made in the document editors are saved back through the service, so an application can integrate the document lifecycle rather than merely request a one-off file.
Transactional email with client-specific accounts
The email API writes messages and attachments into a database queue. A background worker checks scheduled delivery times, resolves the client's sending account and submits messages through SMTP. Delivery state and operational traces let the platform distinguish messages waiting to be processed from those marked as sent.
Integration across generations of software
The solution includes .NET SDKs for current applications and a .NET Framework client for established systems. They expose operations for authorising the application, submitting email and viewing, loading or saving reports. Client applications use these contracts without depending on the platform's internal database layout.
Identity and internal documentation
A separate identity service contains tenant-aware user accounts, profile management, revocable sessions and multi-factor authentication components. A Markdown documentation portal supports navigation and search for developers maintaining the platform. These areas evolve alongside the document and communication services.
Production services with ongoing consolidation
Independent hosts allow the API, reporting module and email worker to run as separate services. The solution currently spans .NET 9 and .NET 10, retaining .NET Framework compatibility in its client SDK. The shared user interface and identity integration continue to be consolidated as part of that modernisation.
See how we integrate business applications, or explore the separate iAureo Agents Platform.
Key capabilities
- Report viewer and designer
- Word and Excel document editing
- PDF and spreadsheet export
- Queued transactional email and attachments
- Client-specific sending accounts
- API and SDK integration for current and legacy .NET applications
