CloudCore Neutronix.

When a business commissions a system built on Neutronix, it does not receive a blank canvas. It receives an engineered foundation: a platform that already understands how to manage users, enforce access rules, move work through multi-step processes, store and retrieve documents securely, render live performance dashboards, send emails and SMS messages, and push real-time notifications to browsers and mobile devices. The development team builds only the domain-specific features — the booking screens, the procurement workflows, the approval chains — on top of a framework that has already solved the hard infrastructure problems.

A workflow engine that runs your operations

At the centre of Neutronix sits a full workflow engine. Business processes are defined as structured flows — a sequence of activities, decision points and parallel branches that model how real work moves through an organisation. Each activity in a workflow can be assigned to a person, a team or an automated worker, and the engine tracks who is responsible, what has been completed and what is overdue. When one step finishes, the system automatically advances the work to the next activity, routes it to the correct person or group, and records every transition for audit and compliance purposes.

Workflows are not limited to human tasks. Neutronix includes virtual workers — automated agents that execute background activities on a schedule or in response to triggers. A food services operation might use a virtual worker to generate weekly purchase orders from consolidated menu plans overnight, while a coworking space might use one to process booking confirmations and send calendar invitations without any staff involvement. The engine manages these workers alongside human tasks, scaling them up or pausing them through an administrative interface, and logging every execution so that failures can be diagnosed and restarted without data loss.

Every user has an inbox — a personal task list that shows what requires their attention. Tasks arrive automatically as workflows progress, carrying context about the process, the customer or transaction they relate to, and their priority. Staff do not need to check separate systems or wait for email instructions; their work finds them. Managers can view worklists across teams, reassign tasks, adjust priorities or cancel work items when circumstances change. The result is an operation where nothing falls through the cracks and every piece of work has a clear owner.

Live dashboards and performance measurement

Neutronix includes a KPI and dashboard framework that turns operational data into visual intelligence. Data sources are defined once and connected to dashboard views that render as charts, gauges, tables or summary tiles. The framework handles data retrieval, caching, scheduled refreshes and user-level access control, so that each person sees the metrics relevant to their role and business unit without additional development work.

Dashboards update automatically. The framework maintains a cache layer that refreshes data at defined intervals, so users always see current figures without placing unnecessary load on the database. When a manager needs a figure right now rather than at the next refresh cycle, a force-refresh option pulls live data on demand. The platform also supports automated period-based reporting, generating PDF reports on financial schedules — daily, weekly, monthly or yearly — and storing them as documents within the system for future reference.

In practice, this means a procurement team can watch supplier spend across regions in real time, while a workspace operations manager can track occupancy rates and booking revenue against targets, all from a dashboard that required no custom front-end development — only a data source definition and a choice of visualisation.

Document management built into every process

Documents are first-class citizens in Neutronix. The platform provides a complete document management layer backed by cloud blob storage, so that files uploaded to any part of the system — invoices attached to a purchase order, compliance certificates linked to a supplier, signed contracts stored against a customer record — are handled consistently, securely and at scale.

Uploading a document records its metadata, assigns a storage path, tracks file size and content type, and generates a secure download link that respects the user's access permissions. Documents can be moved, copied and versioned programmatically, and the system maintains a full audit trail of who uploaded what and when. Because storage is cloud-based, there is no practical limit on volume, and documents are available from anywhere the system is accessible.

This matters operationally because document handling is not bolted on after the fact. A workflow activity can require a document upload before it can be completed. An automated report can be generated as a PDF and stored as a system document in a single step. A food services company managing compliance certificates across hundreds of sites can attach documents directly to the records they relate to, with access controlled by the same security model that governs every other part of the system.

Security, access control and compliance

Neutronix provides a layered security model built around users, access pools, business units and permission sets. Every person in the system has an identity with defined roles and group memberships, and every action — viewing a page, executing a workflow task, accessing a report, downloading a document — is governed by permissions that are evaluated in real time.

Access pools are the core organising concept. An access pool groups together users, pages, workflow tasks and system actions into a named security boundary. Administrators can add or remove users from pools, assign workflow activities to specific pools, and restrict page access to authorised groups — all through a built-in administration interface rather than code changes. When permissions are modified, they take effect immediately across the system.

Business units add an organisational dimension to security. A company with regional offices, branches or departments can segment data and access by business unit, so that a branch manager sees only their own data while head office sees the full picture. This is particularly valuable in operations that span multiple locations — a coworking group with several venues, for example, can ensure each venue manager administers only their own bookings, members and resources, while the group's leadership team has visibility across all sites.

Authentication supports multi-factor verification including one-time passwords delivered by email or SMS, device management for tracking where users have logged in, and password reset flows that follow security best practices. Every authentication event, permission change and administrative action is logged, providing the audit trail that regulatory compliance demands.

Integrations that connect your system to the outside world

Business systems do not operate in isolation, and Neutronix is designed to connect. The framework includes built-in services for sending email and SMS messages, so that workflow activities can notify customers, send confirmations or escalate issues through the channels people actually use. Email delivery integrates with Microsoft Graph API using OAuth delegated permissions, meaning the system sends mail through the organisation's own Microsoft 365 mailbox rather than a generic SMTP relay — messages arrive from a recognised sender, improving deliverability and trust.

Push notifications bring real-time awareness to users wherever they are. Neutronix integrates with Firebase Cloud Messaging to deliver browser and mobile notifications when tasks arrive, deadlines approach or system events require attention. This is a capability built directly into the platform — notifications can be sent to individual users, groups, access pools or the entire user base, and the system manages device registration, token lifecycle and delivery tracking behind the scenes. A coworking space can notify a member the moment their meeting room is ready; a procurement team can receive an alert the instant an approval threshold is breached. The notification reaches the user's device without them needing to be logged into the system.

For organisations that use Microsoft Entra ID (Azure Active Directory), Neutronix supports external single sign-on authentication. Users authenticate through their corporate identity provider, and the platform maps the external identity to a CloudCore user with all the access pool and business unit permissions already configured. This eliminates the need for separate credentials and integrates the business system into the organisation's existing identity infrastructure.

For financial operations, systems built on Neutronix can integrate with accounting platforms and external APIs. The framework provides the service infrastructure — authentication, retry logic, error handling and logging — that makes external integrations reliable in production. A procurement system can push approved invoices to an accounting package, while a booking system can synchronise revenue data with financial reporting tools, all using integration patterns that are tested and maintained as part of the platform.

A module architecture designed for growth

Neutronix is built on a module architecture that keeps systems organised as they grow. The framework itself is composed of core modules — one for the user interface, one for workflow processing, one for administration, one for shared services — and every system built on Neutronix registers its own modules alongside these. Each module encapsulates its own pages, data access, workflow activities, assets and service registrations, so that a booking module and a billing module can be developed, tested and deployed independently.

Neutronix modules follow a structured registration pattern built around dependency injection. Every module implements a typed interface and registers its services asynchronously at startup, which means the platform can initialise complex service graphs — including those that depend on database connections or external APIs — in the correct order without manual wiring. This architecture extends to Azure Functions: systems built on Neutronix can deploy serverless function apps that share the same service infrastructure, security model and data access as the main web application, enabling event-driven processing alongside the core workflow engine.

Adding a new capability to a running system does not require restructuring what already exists. A business that starts with a core booking system can later add a membership module, a reporting module or an integration module, each plugging into the same framework services — the same security model, the same workflow engine, the same document management and the same dashboard framework. The new module inherits everything the platform provides and focuses only on its own domain logic.

Modules also manage their own static resources — stylesheets, scripts, images — through a virtual file system that serves them without conflicts. This separation is what allows multiple development teams to work on different parts of a large system simultaneously, each within their own module boundary, without stepping on each other's work.

Deployment and operations on Microsoft Azure

Every system built on Neutronix runs on Microsoft Azure. The platform uses a single-database architecture where the Neutronix core tables and the system's domain-specific tables coexist in one database, each in their own schema. This means that workflow state, user records, documents and business data all live in one transactional boundary — no fragile cross-database joins, no synchronisation problems, no eventual-consistency surprises.

The framework is consumed as packages, not as source code that must be merged and maintained. When Neutronix releases an update — a security patch, a performance improvement, a new dashboard capability — the system team updates a package reference and redeploys. The system's own code is unaffected. This separation between platform and system is what makes long-term maintenance sustainable: the platform evolves independently, and the system benefits from every improvement without migration risk.

Administration is handled through a built-in interface that covers user management, access pool configuration, workflow process deployment, virtual worker monitoring, dashboard setup, financial period management, system notifications, device management and error logging. Operational staff can manage the day-to-day running of the system — creating users, adjusting permissions, restarting failed workflow items, reviewing error logs — without requiring developer involvement.

The result is a system that is not just built quickly but built to last. The operational tooling, the security model, the workflow engine and the integration infrastructure are already proven in production across industries. What the development team builds on top of Neutronix is the part that matters most to the business — and that is exactly where all the effort goes.