Skip to main content

Brilliance One Technology

A practical technology stack. Built for long-term support.

Brilliance One is built around .NET, C#, SQL Server, Blazor, API services, and selected libraries that support performance, reliability, and secure business workflows.

Business & government focused•API first•Built to evolve
Software Used at Brilliance One

Core stack

Microsoft-based application architecture.

Software names are based on current technical history and supplied page drafts. Version numbers, active deployment scope, and licensing must be confirmed against the production dependency inventory.

Backend

.NET, C# & ASP.NET Core

Application services, REST APIs, business logic, dependency injection, and server-side functionality; .NET 11 is under active migration/validation.

Frontend

Blazor & web standards

Blazor Server plus HTML, CSS, and JavaScript for interactive and standards-based interfaces.

Data

Microsoft SQL Server

Tenant databases, stored procedures, relational data, and backup/recovery operations.

Selected software & libraries

Purposeful dependencies and developer tools.

The stack has included the following packages and tools; their use in any specific deployment, release, or module should be verified.

Data & workflow

Dapper, Entity Framework Core, Hangfire, Polly, and FluentValidation for database access, background jobs, resiliency, and request validation.

API & documentation

Asp.Versioning, Swashbuckle / OpenAPI, Kiota-generated clients, and ASP.NET Core health checks.

Identity & security

Argon2id library, NSec, Otp.NET, authentication middleware, API-key/JWT authorization, and security-review tooling including Aikido.

Application utilities

Blazored.LocalStorage, JsonSubTypes, and Zernio SDK where their respective application functions require them.

Hosting & infrastructure

Microsoft IIS, Windows Server, dedicated SQL Server, Kamatera infrastructure, win-acme certificate automation, and TLS/HTTP configuration.

Connected services

MailerSend; supported AI-provider SDKs and Google/Microsoft calendar, conferencing, communications, and payments integrations as configured.

Lifecycle & governance

Verified is better than merely popular.

Dependency inventories, software bills of materials, vulnerability scanning, license reviews, secure updates, and testing remain important, particularly for government procurement.

  • Maintain an accurate software bill of materials and supported version inventory
  • Monitor CVEs, end-of-support dates and breaking changes
  • Review open-source licensing and supplier risk
  • Document security and privacy implications of each external service
  • Do not assume use of a library implies certification, support, or endorsement

Next Step

Let's discuss your requirements.

Capabilities, deployment options, contractual requirements, and roadmap items should be confirmed for your specific use case.