SiteCert · Blog
What's Under the Hood of the New SiteCert Platform
SiteCert 4 runs on SitePlant, a new microservice platform we built from the ground up on .NET 8 and the ABP framework. This post is for anyone who wants to know how it works.

SiteCert 4 runs on SitePlant, a new microservice platform we built from the ground up on .NET 8 and the ABP framework. This post is for anyone who wants to know how it works.
When people see a relaunch, they notice the design first. The bigger change in SiteCert 4 is underneath. Rather than one large application where every feature depends on every other, SitePlant splits SiteCert into small, independent services that each do one job well.
One job per service
SiteCert 4 is made up of six core services. Each one can be updated, deployed and scaled on its own, so an improvement to reporting never puts asset registration at risk.
- Identity and Auth — sign-in, user accounts and permissions
- Register — asset management
- Servicing — service management and maintenance
- Cert Report — certificates and reporting, drawing on data from Register, Servicing and Queue
- Queue — bulk asset processing, so large jobs don't slow anyone else down
- Administration — system configuration
How it all fits together
Every request from the web or mobile app passes through one gateway, which routes it to the right service. The services share a common foundation for data, messaging, caching and monitoring.
Many customers, each kept separate
SiteCert 4 is a multi-tenant SaaS platform. Every customer uses the same system, but each customer's data is isolated through the ABP framework's tenant controls.
Reporting shows the care this takes. Cert Report reads from the Register, Servicing and Queue databases using PostgreSQL's Foreign Data Wrapper (postgres_fdw), which lets one database query tables held in another. Every one of those cross-service queries applies an explicit tenant filter, so each customer only ever sees its own data.
Quick, even under load
- Event-driven messaging with RabbitMQ. Services pass messages to each other instead of waiting on each other, so a large bulk import doesn't hold up someone running a report.
- Caching with Redis. Frequently used data is held in memory for faster responses.
- Independent scaling. A busy service can be given more capacity without scaling everything else.
We see problems before you do
Every service reports performance metrics to Prometheus, and our team monitors them on Grafana dashboards. If something starts to slow down, we know about it early.
Security checked on every change
- A dedicated identity service handles sign-in and authorisation for the whole platform.
- Every code change runs through an automated pipeline: build, test and container validation.
- Every change is scanned for known vulnerabilities in third-party packages. If a high or critical issue is found, the build fails and nothing is released.
- Database changes are managed through EF Core migrations, with automated checks that the data model hasn't drifted.
Ready to run anywhere
Every service ships in its own Docker container, orchestrated with .NET Aspire and ready for Kubernetes. Our infrastructure is defined as code using Terraform, Bicep/ARM templates and CloudFormation, so the platform can be built the same way every time, on Azure, AWS or elsewhere.
On the front end, the SiteCert web app is a fast Angular single-page application, with mobile support for teams out on site.
The tech stack at a glance
- Framework — .NET 8, ASP.NET Core, ABP Framework
- Languages — C#, TypeScript (Angular)
- Data — PostgreSQL 17, EF Core
- Messaging and cache — RabbitMQ, Redis
- Containers and orchestration — Docker, Docker Compose, .NET Aspire, Kubernetes
- Monitoring — Prometheus, Grafana
- Infrastructure as code — Terraform, Bicep/ARM templates, CloudFormation
- CI/CD — GitHub Actions, Docker Registry
Want to see it for yourself?
The best way to understand the new platform is to use it. Email sales@sitecert.net to book a demo of SiteCert 4.
