Understanding the Technologies We Recommend
When we recommend a particular technology, framework, or platform for your project, it is based on structured evaluation — not on what is fashionable or what we happen to know. This article explains how we make technology decisions.
How We Evaluate Technology
We assess technologies against multiple criteria:
- Fitness for purpose: Does it genuinely solve your problem well?
- Maturity: Is it proven in production environments, or bleeding-edge and unproven?
- Ecosystem: Is there good tooling, libraries, community support, and documentation?
- Longevity: Is it backed by a major vendor or strong open source community? Will it still be supported in 5 years?
- Security: Does it have a strong security track record?
- Total cost: Licences, hosting, skills availability (your future internal team), and maintenance cost
- Your team: If you have internal developers, can they realistically maintain it?
Technology We Commonly Recommend
- Web front-end: React, Next.js, Vue.js — depending on requirements
- Backend APIs: Node.js (Express/Fastify), .NET Core, Python (FastAPI/Django)
- Databases: PostgreSQL, MySQL, MongoDB, Redis
- CMS: WordPress, Umbraco, Sanity, Contentful — matching your team's capabilities and content needs
- Cloud: AWS, Azure, Google Cloud — often dictated by your existing infrastructure
- Mobile: React Native (cross-platform), Swift/Kotlin (native)
Challenging Our Recommendations
You have every right to challenge or question our technology recommendations. We will always explain our reasoning and consider your preferences. If you have strong views on a specific technology, tell us — we will assess whether it is appropriate and be honest if we have concerns.