TECHNOLOGY & INNOVATION
Technology, and the reasoning behind it
The stack listed below is chosen for how well it is maintained, how much of the work is already understood, and what a client team can take on afterwards. Novelty is a poor reason on its own, and it is rarely the deciding one.
Maintenance beats novelty.
Technology principles
-
Modern Technology Stack
We use the latest frameworks and tools to deliver high-performance solutions.
-
Continuous Innovation
We explore new technologies to solve real business challenges.
-
Secure & Scalable Solutions
We build solutions that are secure, reliable and ready for growth.
-
Future-Ready Approach
We stay ahead of emerging trends like AI, cloud, automation and more.
OUR TECHNOLOGY
Our Technology Stack
Nothing here is a preference. Each entry is used because it is well supported, widely documented, and survives a change of team without the project stalling.
Frontend
- React
- Next.js
- Vue.js
- HTML5
- CSS3
- JavaScript
- Tailwind CSS
- Bootstrap
Backend
- Node.js
- PHP
- Laravel
- Python
- .NET
Database
- MySQL
- PostgreSQL
- MongoDB
- Redis
Mobile
- Flutter
- React Native
- Kotlin
- Swift
- Android
- iOS
Cloud
- AWS
- Microsoft Azure
- Google Cloud
- DigitalOcean
AI & Data
- AI & ML
- ChatGPT
- Business Process Automation
DevOps
- Docker
- Kubernetes
- CI/CD
EMERGING TECHNOLOGIES
What we are watching, not adopting
Several items below are on this page because we have said no to them. Putting a technology into production work requires it to be cheaper than the alternative in the way that matters here, which is rarely the case for something new.
-
Artificial Intelligence
Applied to real business processes, decision support and customer service.
-
Machine Learning
Models trained on the data a business already owns.
-
AI Automation
Repetitive document, data and triage work handled automatically.
-
Cloud Computing
Elastic infrastructure sized to real demand.
-
Internet of Things
Connected devices, sensors and operational data.
-
Blockchain Solutions
Tamper-evident records and transparent transactions where the use case fits.
-
AR/VR Experiences
Immersive training, visualisation and product experiences.
-
Generative AI
Content, code and interface assistance inside governed workflows.
Evaluated before it is offered
Our Innovation Initiatives
-
AI-Powered Solutions
Exploring practical ways to use AI to automate processes and improve digital experiences. -
Smart Automation
Reducing repetitive work and helping businesses improve operational efficiency. -
Data-Driven Insights
Helping businesses use information more effectively for better decisions. -
Custom Software Products
Building software around specific business requirements and real-world problems. -
Research & Development
Continuously exploring ideas, technologies and approaches that can create future opportunities.
WHAT THIS ADDS UP TO
What the stack is actually for
Judged by the maintenance cost
A technology choice is only worth discussing in terms of what it changes for the business: how long a change takes to ship, whether a non-specialist can maintain it, and what it costs when something has to be replaced in three years.
HOW WE INNOVATE
Our Innovation Process
A structured approach helps us turn promising ideas into practical solutions, and to reject the ones that are not.
- Research & Discover We explore trends, market needs and relevant new technologies.
- Ideate & Plan We define the strategy and create a practical roadmap.
- Prototype We build and test a proof of concept.
- Develop We develop scalable and secure solutions.
- Test & Optimise We evaluate performance, security and quality.
- Launch & Scale We deploy the solution and support future growth.
NEXT STEP
Ask what we would actually use
If you have a technology you want to use, ask us about it directly. You will get an honest answer about whether it suits the problem, including when the answer is that you should use something else.
Questions people ask us about this
Because we have to support them. Every technology on the list is one the team can maintain at three in the morning, and that constraint is stricter than it sounds. The technology and innovation page gives the reasoning for each one.
Occasionally, and slowly. We add something when clients genuinely need it and remove something when it stops being supportable. The list is shorter than a typical agency's, and it is shorter on purpose.
Where it earns its place, and with the reasoning documented so somebody can check what the system did. That means automating the repetitive part of a process rather than the judgement. The AI and automation page sets out where we draw the line, and our position on publishing unreviewed machine output is explained in the content drafting article.
With AWS, Azure or Google Cloud, depending on the requirement and the client's existing arrangements. The reasoning and the alternatives are covered on cloud and server management, including the case for staying where you are.
No. A platform that cannot be moved is a dependency, and we would rather a client could change supplier than have to. That principle runs through the why SmartEdge page and it is why the code is in the client's name from the first commit.
It is patched on a schedule, and where a version is no longer supported the migration is planned and budgeted rather than left until something breaks. The security hardening service covers the server side of the same discipline.
We use them where they are genuinely better, and it matters where the licence is per user and the tool holds the client's data. Where an open platform does the same job, we recommend it, because the recurring cost is yours and the exit is easier.
On whether the system can be understood and owned, not on its age. If the logic is comprehensible and the platform is still supported, repair is nearly always right. If neither is true, rebuilding is cheaper in the long run and we will show the working. The rebuild versus redesign article works through the decision.