We build on the right foundations
We chose our technology stack deliberately — for longevity, ecosystem strength, and the ability to deliver genuine business value. Not because it's trendy.
Umbraco CMS
Umbraco is the leading open-source CMS on .NET. It gives editorial teams genuine control over content without compromising developer flexibility or security.
We chose Umbraco because it scales from simple brochure sites to complex multi-site platforms, supports headless delivery via the Content Delivery API, and has a mature ecosystem of packages and integrations. It's backed by a commercial company with a long-term roadmap.
We're certified Umbraco partners and have been building on the platform since version 7.
Why Umbraco?
- Open source with commercial backing
- Built on .NET — enterprise-grade performance
- Headless and traditional delivery modes
- Intuitive editorial experience
- Mature security model and audit logging
Why Dataverse?
- Relational data with built-in security model
- Power Platform integration out of the box
- REST and OData APIs for custom integrations
- Auditing, versioning, and compliance built in
- Scales from SMB to enterprise
Dynamics 365 & Dataverse
Dataverse is Microsoft's low-code data platform — and the backbone of Dynamics 365, Power Apps, and an increasing number of the integrations we build for clients.
For membership organisations, it manages contacts, subscriptions, CPD records, and event registrations. For field service, it powers scheduling, inspection records, and asset management. For attractions, it connects visitor data to marketing automation and operational reporting.
We build custom Dataverse solutions and integrate them with Umbraco front-ends via Azure integration services.
Microsoft Azure
Every platform we build runs on Azure. App Services for web hosting. Azure Functions for serverless processing. Azure SQL for data. Azure CDN for performance. Azure DevOps for CI/CD pipelines.
We manage infrastructure through code (Bicep/ARM templates), so every environment is reproducible and auditable. Staging, production, and disaster recovery are part of every deployment, not afterthoughts.
Azure services we use
Why .NET MAUI?
- Single codebase for iOS, Android, Windows
- Native device access (GPS, camera, sensors)
- Offline-first with SQLite sync
- Shared skills with .NET backend team
- Enterprise deployment via Intune/MDM
.NET MAUI
.NET MAUI is Microsoft's cross-platform framework for building native mobile applications. A single C# codebase targets iOS, Android, and Windows — which means we don't need separate teams for each platform.
For field service work, MAUI gives us offline data storage, GPS tracking, camera integration, and push notifications. For visitor attractions, it powers audio guides, interactive maps, and ticketing apps.
Because MAUI shares the same .NET ecosystem as our backend services, the entire stack speaks the same language.
How we use AI — and why we tell you about it
We use AI tools — including Claude Code, the Claude API, and GitHub Copilot — to accelerate development, generate initial content drafts, and automate repetitive tasks. This isn't a secret ingredient; it's a deliberate methodology.
We're transparent about AI usage because our clients deserve to know where the efficiency comes from — and because it lets us pass on genuine cost savings. Every AI-assisted output goes through human review before it reaches production.
This site runs on our stack
The Infobox website is built on Umbraco 17, hosted on Azure, and was developed with AI assistance from Claude Code. The content was drafted with AI and reviewed by humans. We use our own tools because we trust them — and because it means we find the rough edges before our clients do.
Want to know more about how we build?
We're happy to talk architecture, tech choices, and AI methodology. No pitch deck required.
Start a conversation