Enterprise architecture. Nothing hidden.
Pulse is built end to end on enterprise platforms - Microsoft Azure, Entra ID and Dynamics 365, with Cloudflare at the edge. Every decision is versioned, every hand-off is durable, and every change is tested before it ships.
We believe in transparency. We publish our architecture below. The platforms, the pipelines, the safeguards - and what's still on our roadmap.
- automated backend tests on every change
- 540+
- automated backend tests on every change
- automated quality and security gates in CI
- 5
- automated quality and security gates in CI
- Power Automate workflows in Dynamics 365
- 16
- Power Automate workflows in Dynamics 365
- database passwords - identity-based access only
- 0
- database passwords - identity-based access only
Azure SQL Database Azure Service Bus Microsoft Entra Managed Identities Microsoft Power Platform Cloudflare .NET React TypeScript Azure Application Insights Terraform GitHub Actions Snyk
Enterprise platforms, layer by layer
Every layer of Pulse runs on a platform built for regulated, high-stakes work - the same ecosystem much of UK public sector IT already runs on.
Edge
The public assessment, served close to every young person.
- Cloudflare Workers
- Cloudflare Turnstile
Experience
Accessible, responsive interfaces for young people and staff.
- React 19
- TypeScript
- Vite
- Tailwind CSS
Platform
The decision engine and API at the heart of Pulse.
- C# on .NET 10
- ASP.NET Core
- Entity Framework Core 10
- Wolverine messaging
Data and messaging
The decision record, with durable hand-offs.
- Azure SQL Database
- Azure Service Bus
- Transactional outbox
Identity and secrets
Enterprise identity, with no passwords in the data path.
- Microsoft Entra ID
- Managed identities
- Azure Key Vault
- Azure App Configuration
CRM and workflow
Where Support Navigators manage every referral.
- Microsoft Dynamics 365
- Microsoft Power Platform
- Dataverse
- Power Automate
Operations
Every environment defined in code, and watched around the clock.
- Terraform
- Azure Application Insights
- Azure Log Analytics
- Automated alerting
Engineering
How every change is built, tested and secured.
- GitHub Actions
- xUnit and Vitest
- SQL Server in Testcontainers
- Snyk
Built like critical infrastructure
Every part of Pulse is engineered so that nothing fails quietly. Here's what that means, area by area.
Area
How Pulse does it
- Identity
- Microsoft Entra ID, with managed identities between services
- Data
- Azure SQL Database as the transactional decision record, with Dynamics 365 as the operational record
- Integration
- Durable messaging over Azure Service Bus with a transactional outbox
- When something fails
- Automatic staged retries, then an error queue - nothing is silently lost
- Change control
- Every change built, tested and safeguarding-gated, then deployed automatically through approval gates
- Infrastructure
- Every environment defined as code in Terraform - repeatable, reviewable and versioned
- Monitoring
- Azure Application Insights and Log Analytics, with alerting when something needs attention
- Security scanning
- Snyk scans every dependency on every change, and weekly
- Case management
- Microsoft Dynamics 365 with a purpose-built navigator app
- Audit
- Versioned, replayable decisions and audited CRM changes
How it all fits together
From a young person's first tap to a provider's inbox, every step runs on a platform designed for it - and every hand-off is durable.
Edge
Cloudflare
Young person
Any device, no account needed
Cloudflare Workers
Serves the public assessment
Turnstile
Bot protection on every session
Platform
Microsoft Azure
Pulse decision engine
.NET 10 - scoring, safeguarding and matching
Azure App Configuration
Central configuration
Azure Key Vault
Secrets, never in code
Data and messaging
Microsoft Azure
Azure SQL Database
The decision record
Azure Service Bus
Durable, ordered hand-offs
Microsoft Entra Managed Identities
Passwordless access between services
Case management
Microsoft Dynamics 365
Microsoft Power Platform
Dataverse and 16 Power Automate flows
Pulse Navigator
The operational record for Support Navigators
Service providers
Referral emails, tracked to outcome
Pulse keeps the decision record. Dynamics 365 keeps the operational record. Each system does what it's best at, connected by durable events over Azure Service Bus.
Microsoft Azure
Pulse runs on managed Microsoft Azure services in the UK South region - enterprise infrastructure, end to end.
Azure SQL Database
The transactional decision record for assessments, decisions and referrals, reached over encrypted connections.
Azure Service Bus
An enterprise message broker carrying every hand-off between Pulse and Dynamics 365.
Azure App Configuration and Key Vault
Configuration is managed centrally, and secrets are held in Key Vault - never in source code. Pulse refuses to start without them.
Monitoring and infrastructure as code
Application Insights and Log Analytics watch every environment and raise alerts, and each environment is defined in Terraform so it can be rebuilt exactly.
UK data residency
Platform resources are provisioned in Azure UK South.
Managed Azure services
Azure SQL Database Azure Service Bus Azure App Configuration Azure Key Vault Microsoft Entra Managed Identities Azure Application Insights Azure Log Analytics - UK SouthAzure region
Microsoft Entra ID
Enterprise identity from the platform your organisation already trusts - for the people who use Pulse, and for the services that power it.
Organisation sign-in for Support Navigators
Navigators work in Dynamics 365 with their Microsoft Entra accounts, and what they can see and do is governed by security roles.
Managed identities, not passwords
Pulse reaches Azure SQL Database, Service Bus and App Configuration with Entra-issued tokens. There are no database passwords to leak, share or rotate.
Least privilege by default
Each identity gets only the rights it needs. Pulse's messaging identity can send to its queues, and nothing more.
No passwords in the data path
Pulse decision engine
Microsoft Entra Managed Identities
Short-lived tokens, issued on demand
No stored database passwords or connection secrets.
Cloudflare
The public assessment is served from Cloudflare's global network, close to every young person who opens it and separated from the core platform.
Cloudflare Workers
The assessment experience is delivered from the edge - fast to load, resilient, and isolated from the systems behind it.
Turnstile bot protection
Every new assessment session passes a Cloudflare Turnstile challenge, verified server-side by Pulse before the session is created.
Embed protections
Each organisation's approved websites are allow-listed, and framing is locked down with a Content Security Policy.
Every session, verified
A young person opens the assessment
Cloudflare Workers and Turnstile
Served from the edge, bots challenged
Verified server-side by Pulse
Only then is a session created
Microsoft Dynamics 365
Support Navigators manage referrals in a purpose-built Dynamics 365 app, connected to Pulse by durable events over Azure Service Bus.
Pulse Navigator
A model-driven app with a guided Referral Navigation process, follow-up task automation and a dedicated Support Navigator security role.
Event-driven integration
Referrals, services and organisations flow into Dataverse over Azure Service Bus. Navigator decisions and outcomes flow back the same way.
Provider communication
Referral emails to providers are sent, resent and tracked from Dynamics 365, with delivery outcomes reported back to Pulse.
Audited and version-controlled
A Dataverse plug-in audits changes to referrals, and the complete Dynamics solution is held in source control.
Inside Pulse Navigator
- Dataverse tables
- 12
- Dataverse tables
- Power Automate flows
- 16
- Power Automate flows
- guided business process
- 1
- guided business process
- audit plug-in
- 1
- audit plug-in
Built on Microsoft Power Platform: Pulse sends events to Dataverse navigators act outcomes flow back to Pulse.
A slow partner never loses a referral
Every hand-off between systems is committed, delivered and retried by design. If something downstream is down, Pulse waits and tries again - the young person's journey never depends on it.
Step 1
Saved with the record
Each outgoing message is written in the same database transaction as the change it describes.
Step 2
Delivered over Service Bus
Messages leave through Azure Service Bus, in order, to the systems that need them.
Step 3
Retried automatically
If a partner is slow or offline, Pulse tries again on a staged schedule.
- 30 sec
- 2 min
- 10 min
Step 4
Held for review
Anything still failing moves to an error queue - visible and recoverable, never silently lost.
Built for when things go wrong
Duplicates can't double up
Every hand-off is idempotent. A repeated or replayed message never creates a second referral, a second delivery or a second email to a provider.
Unanswered referrals don't go quiet
A sent referral is tracked as awaiting a response. If a service hasn't replied within three working days, Dynamics 365 raises a chase task for a Support Navigator; if it declines, a task to find an alternative follows the next working day.
Failure paths are tested
Automated tests against a real database prove that replayed messages, failed transactions and repeated outcomes all behave correctly.
Every decision can be reproduced
When someone asks why a young person was offered a service, Pulse can show the exact rules that applied at that moment - and prove the same answer comes out again.
Versioned
Scoring, matching and every provider's referral policy carry an explicit version.
Fingerprinted
Each decision records a content digest of the exact policies that produced it.
Replayable
Historical decisions can be re-run and compared, so any outcome can be explained after the fact.
Immutable once approved
An approved policy can't be edited. Changing it means publishing a new version.
- scoring_model
- v4.2.0
- matching_model
- v3.1.0
- provider_policies
- 12 approved
- policy_digest
- sha256:9f2c...e41a
- replay
- identical outcome
Nothing ships without passing every gate
Every change to Pulse runs through an automated GitHub Actions pipeline. It's built, tested against a real database, checked against safeguarding baselines and scanned for vulnerabilities before it can merge - then deployed through approval gates.
GitHub Actions - from pull request to production
Pull request
Every change runs the full pipeline before it can merge.
Build and test
540+ backend tests, run against real SQL Server in containers.
Locked validation corpus
Held-out safeguarding and matching scenarios, reported on their own.
Safeguarding gate
Fails the build if a change weakens any approved safeguarding protection.
Dependency security
Snyk blocks high and critical vulnerabilities, and re-scans weekly.
Approved deployment
Releases roll out automatically to Terraform-defined environments, through approval gates.
The safeguarding gate is unusual. If a change to scoring or matching would weaken a protection that has already been approved, the build fails - however good the change looks elsewhere.
Where we are, and what's next
We'd rather show you exactly where Pulse stands than claim a badge we haven't earned. Here's what is in place today, and what is on our roadmap.
In place today
- Microsoft Entra ID for navigator access, governed by security roles
- Passwordless, identity-based access to Azure data services
- Least-privilege messaging identities
- Secrets held in Azure Key Vault, never in code
- Encrypted connections to the database
- Cloudflare Turnstile, verified server-side
- Embed allow-lists and Content Security Policy
- Snyk dependency scanning on every change and weekly
- Safeguarding regression gate in the build pipeline
- Automated deployments with approval gates
- Infrastructure as code in Terraform for every environment
- Centralised monitoring and alerting with Application Insights and Log Analytics
- Idempotent hand-offs, so duplicates never create a second referral
- Automated follow-up of unanswered referrals in Dynamics 365
On our roadmap
- Business continuity and disaster recovery, with tested restores and published RPO and RTO, before go-live
- Outage and recovery testing, with Application Insights alerting, before go-live
- Role-based access across the admin portal
- Independent penetration testing before go-live
- Cyber Essentials certification
Let's talk about your pathway
Whether you're exploring a pilot, preparing a tender response, or reviewing assurance evidence for commissioners, we're happy to walk through Pulse in detail.