Web experience
HTML, CSS and TypeScript organise content and interaction. This website uses Astro and Node.js, with prerendered pages and limited JavaScript in the browser.
TECHNOLOGIES / PURPOSEFUL CHOICES
Technology choices guided by your project requirements
A project’s technical foundation should serve its users, data and operating environment. We evaluate technologies for web applications and integrations with security, performance, maintenance and future development in mind.
What we review before choosing
Security, response time and integration requirements.
Maintenance, documentation and compatible licences.
Practical deployment and operating costs.
01 / Technologies
Different layers have different needs.
These categories show how we discuss technical choices. They are not a list of certifications or a guarantee of support for every technology.
Applications and APIs
Server choices are assessed against business workflows, permissions and integrations. Platforms such as .NET can be considered where they fit the requirements and maintenance environment.
Data and storage
Consistency, access controls and recovery come before database selection. A relational database such as PostgreSQL is assessed when the data model and operational needs justify it.
Delivery and operation
Repeatable builds, version control and controlled installation reduce unclear manual dependencies. Docker is used in this project for the runtime and verification environment.
02 / Technologies
The right questions before the stack.
A technical proposal should explain the responsibilities of a choice as well as its capabilities.
- Who will maintain the application, and what knowledge will they need?
- How is a change tested, and how can it be rolled back?
- How is data protected, and where are secrets stored?
- What are the load limits, costs and licensing obligations?
03 / Technologies
Technology ecosystems for assessment
Choices depend on integrations, the maintenance team and total cost. These are examples for technical assessment, without implying vendor partnerships or certified expertise.
Backend and APIs
C#/.NET and ASP.NET Core, Java/Spring Boot, PHP/Laravel/Symfony, Node.js/NestJS and Python/Django/FastAPI can be assessed per project. Business rules, authentication, permissions and secure communication take priority.
Frontend and user experience
HTML, CSS, JavaScript and TypeScript underpin the web. Astro, Blazor, React, Angular, Vue, Next.js and Nuxt are assessed against interaction, rendering, accessibility and SEO needs.
Mobile and desktop
Kotlin/Java for Android, Swift for iOS, .NET MAUI, Flutter and React Native are options for investigation. On Windows, WPF/WinUI and local services can be assessed for device or printer integration.
Data and infrastructure
PostgreSQL, SQL Server, MySQL/MariaDB and SQLite are assessed against data and operational needs. Docker, Linux/Ubuntu, Nginx and GitLab CI/CD can support delivery and operation. Caches and message queues are chosen only for a defined need and with management rules.
CMS and content management with C# / .NET
Umbraco CMS, Orchard Core and Piranha CMS provide foundations for business websites and content management in the .NET ecosystem. Depending on the platform, we assess C# extensions, multilingual content, editorial roles and headless APIs against project requirements.
Headless CMS with Node.js / TypeScript
Payload CMS and Strapi Community are assessed for managing structured content and delivering it through APIs to websites and applications. We review content models, permissions, previews and frontend integration against the capabilities of the selected edition.
eCommerce, CMS and ERP / CRM tools
For eCommerce we assess WooCommerce, PrestaShop, Magento Open Source and the open-source Medusa core (Node.js/TypeScript). Other CMS options include WordPress, Drupal and Joomla, while ERP/CRM options include Odoo Community, ERPNext and Dolibarr. Selection considers features, integrations and maintenance, with a separate review of versions, dependencies and licences.
FAQ
How is a project’s technology selected?
By considering features, integrations, security, maintenance and lifecycle cost. The technical proposal explains trade-offs and dependencies rather than starting with a framework.