Validation
Review Before Adoption
Dependencies can be evaluated for known vulnerabilities, package integrity, licensing, project health, maintainability, operational risk, and suitability before becoming part of the platform.
The Verified Stack
Built with intention. Powered by proven technology.
Brilliance One is built on a carefully managed technology foundation designed around security, performance, maintainability, interoperability, and long-term control.
We use modern .NET, established open-source software, professionally licensed components, standards-based frontend development, controlled dependency management, and security-focused review rather than adding technology simply because it is popular.
.NET
•
API First
•
Standards Based
•
Security Focused
Technology Philosophy
Use the right technology. Not the most technology.
Every dependency introduces code, maintenance, security considerations, licensing obligations, upgrade requirements, and long-term operational responsibility. Brilliance One treats technology selection as an architectural decision rather than a collection exercise.
Control
Reduce Unnecessary Dependency
Brilliance favors controlled delivery and direct ownership where practical instead of making critical platform behavior dependent on unnecessary third-party libraries, frameworks, or public delivery infrastructure.
Sustainability
Build for Long-Term Maintenance
Technology decisions consider not only what solves today’s problem, but also whether the software can be responsibly maintained, upgraded, secured, documented, and supported over time.
Architecture Standard
Modern .NET at the platform core.
Brilliance One is engineered on modern .NET architecture to support APIs, business logic, security, data access, background processing, integrations, modular services, and high-performance operational workloads.
- Modern .NET architecture
- C# business logic
- ASP.NET Core
- API-first platform design
- SQL Server data services
- Background processing
- Dependency injection
- Modular application services
- Structured security controls
- Integration-ready architecture
Platform Core
Enterprise architecture without unnecessary complexity.
The platform is designed to keep business logic, data access, APIs, frontend experiences, integrations, automation, and security concerns appropriately separated while still operating as one connected system.
That structure allows individual capabilities to evolve without requiring the entire platform to be rebuilt every time one component changes.
Frontend Philosophy
Framework optional. Standards required.
Brilliance One does not require every website or interface to inherit a specific CSS framework. The frontend can be built around standard HTML, CSS, and JavaScript while frameworks or component libraries remain implementation choices rather than platform requirements.
HTML
Semantic markup provides the structural foundation for accessible, understandable, maintainable web experiences.
CSS
Native CSS can provide responsive design, theming, layout, accessibility support, and visual consistency without requiring a framework for every interface.
JavaScript
JavaScript is used where behavior requires it rather than as a prerequisite for content that can be delivered through simpler browser standards.
Component Libraries
Mature components can still be used where they meaningfully improve complex workflows, accessibility, development speed, or user experience.
Framework Choice
When a framework is appropriate, it can be selected for the application rather than becoming a permanent requirement imposed by the CMS or platform.
Less Lock-In
Standards-based output makes it easier to evolve frontend technology without treating one framework as part of the customer’s permanent content architecture.
Technology Choice
The platform manages the business. It should not dictate every frontend decision.
Brilliance One is moving toward a platform-agnostic frontend philosophy where CMS content, CRM data, forms, workflows, and business services can be exposed through APIs and consumed by the experiences that make sense for the customer.
- Standards-based frontend development
- API-driven business services
- Framework-independent content
- Reusable platform data
- Connected forms
- Headless-capable architecture direction
- Custom frontend support
- Progressive enhancement
- Reduced framework coupling
- Long-term portability
Technology Should Be a Choice
Your website should not belong to your website framework.
A CMS should manage content and business data. It should not require customers to rebuild their digital presence simply because one frontend library falls out of favor.
Dependency Management
Every dependency has to earn its place.
Open-source and commercial software can accelerate development significantly, but every external dependency becomes part of the platform’s security, licensing, operational, and maintenance responsibilities.
Evaluate
Review the purpose, architecture, license, project history, maintenance activity, security posture, vendor or community support, and alternatives.
Validate
Evaluate package integrity, known vulnerabilities, compatibility, runtime behavior, operational impact, and fit within the Brilliance architecture.
Maintain
Monitor updates, security advisories, licensing changes, compatibility, support status, and whether the dependency continues to justify its place in the platform.
Open-Source Foundation
Proven software. Reviewed before adoption.
Brilliance One uses established open-source technology where it provides clear value and can be responsibly incorporated into the platform’s security, licensing, maintenance, and architectural requirements.
Verified Open-Source Stack
Open source with operational discipline.
The software below represents open-source technology used within or supporting the Brilliance ecosystem.
Chart.js
Chart.js is a flexible and elegant JavaScript library for creating interactive data visualizations. It supports eight chart types—including bar, line, area, radar, and pie—and allows extensive customization for colors, animations, and tooltips.
- License: MIT
- Source: https://www.chartjs.org/
Facebook Pixel
Meta (Facebook) Pixel is a snippet of JavaScript code that helps track visitor activity on a website. It’s used for analytics, advertising optimization, and remarketing campaigns on Facebook and Instagram.
- Note: Facebook's Pixel does use Facebooks’s CDN, which may collect limited analytics. Using Facebook's Pixel is not usually acceptable in the UK with GDPR.
- License: Proprietary (Meta Platforms, Inc.)
- Source: https://www.facebook.com/business/tools/meta-pixel
FancyBox
FancyBox is a modern lightbox script that helps display images, videos, and other content in a responsive, elegant overlay. It supports touch gestures, galleries, and iframe content.
- License: GPLv3 or Commercial License
- Source: https://fancyapps.com/fancybox/
Google Analytics
Google Analytics provides in-depth insight into how visitors interact with your website, including traffic sources, engagement metrics, and conversion tracking. It’s a crucial tool for optimizing user experience and marketing effectiveness.
- Note: Google Analytics does use Google’s CDN, which may collect limited analytics. Using Google Analytics is not usually acceptable in the UK with GDPR.
- License: Proprietary (Google LLC)
- Source: https://analytics.google.com/
Google Fonts
Google Fonts is an open library of hundreds of web-optimized fonts that can be freely embedded into websites and apps. It allows designers and developers to easily incorporate typography that is both performant and visually appealing.
- Note: Fonts are open source, but served via Google’s CDN, which may collect limited analytics. Using Google Analytics is not usually acceptable in the UK with GDPR.
- License: SIL Open Font License
- Source: https://fonts.google.com/
jQuery
jQuery is a fast, small, and feature-rich JavaScript library that simplifies DOM manipulation, event handling, and Ajax. Its wide browser support and plugin ecosystem made it one of the most influential libraries in web development history.
- License: MIT
- Source: https://jquery.com/
Microsoft Clarity
Microsoft Clarity is a free analytics tool that provides session recordings, heatmaps, and behavioral insights. It helps identify usability issues and improve user experience by showing how visitors actually interact with your site.
- Note: Microsoft Clarity does use Microsoft’s servers, which may collect limited analytics. Using Microsoft Clarity is not usually acceptable in the UK with GDPR.
- License: Proprietary (Microsoft Corporation)
- Source: https://clarity.microsoft.com/
QR Code Styling
QR Code Styling is a lightweight JavaScript library that allows you to generate stylish and branded QR codes with custom shapes, colors, and embedded logos. It’s perfect for integrating modern QR functionality into digital products.
- License: MIT
- Source: https://qr-code-styling.com/
Spectrum Color Picker
Spectrum is a powerful and flexible color picker plugin built on jQuery. It supports multiple color formats (HEX, RGB, HSL), transparency selection, and custom palettes, making it ideal for creative UI tools.
- License: MIT
- Source: https://bgrins.github.io/spectrum/
Microsoft .NET Core
Microsoft .NET Core (now simply .NET) is a free, open-source, cross-platform framework for building modern web, cloud, and desktop applications. It provides exceptional performance, scalability, and security, making it a foundational platform for the Brilliance One ecosystem. The modular runtime and open development model ensure long-term reliability and community-driven innovation.
.NET’s flexibility allows us to integrate multiple data services, background processes, and secure API endpoints — ensuring each component of our system communicates efficiently and predictably.
- License: MIT License (Open Source Initiative approved)
- Source: https://github.com/dotnet/runtime
Tailwind CSS
Tailwind CSS is a utility-first CSS framework for rapidly building custom designs. It eliminates repetitive styling by providing low-level utility classes for spacing, color, typography, and layout—all composable in your markup.
- License: MIT
- Source: https://tailwindcss.com/
Open-Source Principles
Free to use does not mean free of responsibility.
- Review licensing before adoption
- Evaluate known security issues
- Track maintenance activity
- Prefer established projects
- Limit unnecessary packages
- Review update impact
- Maintain attribution where required
- Replace abandoned dependencies when appropriate
- Contribute issues or improvements where useful
- Support healthy software ecosystems
Controlled Delivery
Reduce unnecessary third-party runtime dependency.
Where appropriate, approved frontend assets and dependencies can be delivered through Brilliance-controlled infrastructure rather than depending entirely on public third-party CDNs at runtime.
- Controlled package versions
- Known asset locations
- Reduced external runtime dependencies
- Predictable deployment
- Centralized update management
- Dependency version control
- Reduced unexpected asset drift
- Improved availability control
- Security review before deployment
- Documented software ownership
Private Delivery Layer
Control the dependency you depend on.
Hosting approved assets through controlled infrastructure can reduce exposure to external delivery changes and provide greater consistency over which version of a dependency reaches production.
It does not eliminate software supply-chain risk, but it can provide another layer of operational control.
Professional Software
Build when it differentiates. Buy when expertise matters.
Brilliance One can use professionally licensed software where mature components, dedicated vendor support, specialized functionality, accessibility, integration quality, or long-term maintenance provide greater value than rebuilding the same capability internally.
Professional Software List
Commercial technology used intentionally.
The following professional products provide specialized functionality within the Brilliance ecosystem.
Froala Editor
Froala Editor is a premium WYSIWYG HTML editor designed for seamless integration with web applications. It offers advanced features like inline editing, drag-and-drop image uploads, Markdown support, custom styles, and robust plugin architecture.
- Standard Modules Used (All Available)
- Core Product
- Emoticons
- Lists
- Draggable
- Markdown
- Paragraph Styles
- Microsoft Word Pasting
- License: Commercial (Froala Labs, part of Idera Inc.)
- Source: https://froala.com/wysiwyg-editor/
Telerik / Progress Software
Telerik by Progress provides a professional suite of web and application UI components for .NET and JavaScript frameworks. It includes the Kendo UI library, offering high-performance grids, charts, forms, and more for enterprise-grade applications.
- Modules:
- Kendo Grid
- Lookup Components
- License: Commercial (Progress Software Corporation)
- Source: https://www.telerik.com/
Support
Professional Vendor Support
Commercial software can provide dedicated technical support, documented upgrade paths, vendor expertise, and professionally maintained components for critical functionality.
Experience
Mature Components
Established professional components can accelerate complex interfaces and workflows while reducing the need to reinvent mature functionality internally.
Adoption
Still Subject to Review
A commercial license does not automatically make software appropriate. Professional tools are still evaluated for security, licensing, accessibility, maintainability, vendor stability, integration quality, and architectural fit.
Software Supply Chain
Security includes the software behind the software.
Application security is not limited to the code Brilliance writes directly. Frameworks, packages, libraries, build tools, commercial components, delivery systems, and integration dependencies all become part of the broader software supply chain.
Vulnerability Awareness
Dependencies can be reviewed against available vulnerability information and security advisories as part of ongoing maintenance.
Version Control
Production environments should use known and controlled dependency versions rather than silently inheriting unreviewed changes.
Update Discipline
Security updates still require compatibility testing and controlled deployment instead of assuming every new package version is automatically safe.
License Awareness
Dependencies are evaluated for licensing obligations and their compatibility with the intended use of the Brilliance platform.
Dependency Reduction
Fewer unnecessary dependencies can reduce maintenance work and limit the number of external components that must be monitored over time.
Replacement Strategy
Dependencies that become abandoned, insecure, incompatible, or strategically unsuitable can be replaced as the platform evolves.
Technology Decision Model
Build. Adopt. Or leave it out.
Build
Build internally when the capability is strategically important, differentiates Brilliance One, requires deeper control, or benefits from direct ownership.
Adopt
Adopt established software when it solves a mature problem well and its security, license, maintenance, support, and architecture fit the platform.
Leave It Out
Avoid adding a dependency when browser standards, existing platform capabilities, or simpler code can solve the same problem without unnecessary complexity.
The Verified Stack
Less dependency. More intentional technology.
Brilliance One combines modern .NET architecture, standards-based frontend development, carefully selected open-source software, professional components, controlled dependency management, APIs, and security-focused engineering into one maintainable technology foundation.
Brilliance One • Standards First • API First • Built for Control