Software development technologies
We choose the stack and build the software for engineering and product teams launching, taking over or modernizing a system. We own the architecture decision and the code that implements it.
- 120+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 5.0Unified rating across 61 client reviews on Clutch
- ISTQBISTQB-certified QA engineers
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
Connect the stack choice to delivery
A software development technology stack combines languages, frameworks and platforms for different parts of a system. Use this directory to find the relevant decision, then the services pages to agree the scope and who owns delivery.
02Where to start
Start with the decision your system needs
Choose the decision you need to make. Each route pairs a technology category with the unicrew service that owns the work.
You are choosing between React, Angular and Vue for the client side
Start hereFront-end Development
What you would be buyingWeb Application Development Services
You are selecting a server runtime for a new system
Start hereBack-end Development
What you would be buyingCustom software development services
You are deciding whether Kubernetes fits your deployment needs
Start hereDevOps
What you would be buyingDevOps Consulting Services
You are choosing between a blockchain and a database
Start hereWeb 3.0 & Blockchain
What you would be buyingCustom software development services
You are deciding which business logic belongs on a platform and which needs custom software
Start hereCMS & Platforms
What you would be buyingWeb Application Development Services
You are choosing between a hosted AI model, running open weights and training on your own data
Start hereAI / ML
What you would be buyingAI and Machine Learning Development
03The full stack
Browse technologies by their role in your system
Industry requirements shape the stack. Start with the constraints for fintech, healthcare and logistics and transportation, then compare the technology categories below.
.NET Development
Angular Development
Laravel Development
Node JS Development
PHP Development
React Development
Vue.js Development
Yii2 Development
C
C#
C++
Django
Golang
Java Development
Python Development
Ruby
Rust
Bootstrap
CSS
HTML
HTML5
JQuery
JS
Next.js
TypeScript
Flutter
Kotlin
Objective C
Swift
Anthropic
ChatGPT API
DeepSeek
Gemini
LLaMA
PyTorch
Qwen
TensorFlow
AWS
Azure Cloud Migration
Google Cloud
Azure DevOps
Cloudflare
Docker
Git
Kubernetes
Apache Hadoop
Apache Spark
Databricks
Microsoft SQL Server
MongoDB
MySQL
PostgreSQL
Snowflake
BrowserStack
Selenium
TestCafe
Adobe
Figma
Material UI
Storybook
HubSpot
Magento
Moodle
Salesforce
Shopify
WooCommerce
WordPress
Ethereum
SolidityNo technology here matches that
We may still work with it, and the areas above are where the decision usually sits. Clear the search to see all of them, or ask an engineer directly.
04How we choose
Technology stack selection, from review to handover
We turn your requirements into a written recommendation and validate it with working code.
- Architecture reviewWe review your goals, existing systems and compliance requirements, with the skills and local hiring market your maintenance plan depends on.
- A written stack decision recordThe recommendation, rejected alternatives, costs and risks, written in plain language for your team to keep.
- One thin slice, shippedWe build one real feature end to end on the proposed stack to test the choice in running software.
- Handover written during deliveryWe build CI/CD, tests and monitoring alongside the code, and write the documentation needed for your engineers or ours to take the next release.
05What you keep
Keep control of the code and operating environment
Your team keeps the assets needed to maintain and release the system. The repositories, accounts and records below remain under your control.
- Source code and repositoriesThe code and delivery pipelines live in your repositories.
- Cloud accounts in your nameInfrastructure code sits in your cloud accounts; tooling uses your licences and billing.
- Written decision recordsArchitecture decisions, rejected alternatives and reasons stay in writing your team and board can use.
- A documented handoverRunbooks and documentation are written during delivery, ready for your engineers to maintain the system.
06Client voices
How clients describe delivery and ownership
After launching the site we saw a rapid increase of test accounts ordered by potential customers. Now the site provides a steady source of sales leads.
Single point of contact. Very clear in communications and finding solutions as a team. Flexible when requirements changed. They deliver in a highly professional way while being in a volatile and insecure situation.
They’ve been helping us grow our platform together since the beginning, from a couple hundred companies to around 2,000. Artelogic has been front and center in this process.
07Credentials
Certified, audited, and proven
Review the credentials relevant to your procurement requirements alongside the people and scope proposed for your engagement.
Company certifications
ISO 27001:2022Information security management system, independently audited and renewed through a multi-stage audit with Quay Audit UK.
ISO 9001:2015Quality management system covering the delivery process, certified in the same audit.
ISTQBISTQB-certified QA engineers, working to the testing scope agreed for the engagement.
Laravel PartnerOfficially certified Laravel partner company.
Team credentials
PMIPMP-certified delivery and project leadership, and PMP among the business analysts' certifications.
Zend PHPZend Certified Engineers on the PHP and Laravel teams.
Microsoft MCSAMicrosoft Certified Solutions Associate, Web Applications.
IIBA ECBACertified business analysis for discovery and scoping.
08Case studies
Software stacks behind delivered systems
We own and run Snaplore. Its clients report up to 60% less time spent on documentation, a ceiling measured on our product rather than an average. The AWS saving is client-reported against the previous setup. Booked It's booking and spend gains are case results averaged across businesses using the platform.
See all case studies
Built by unicrewAI-powered knowledge managementSnaplore is unicrew's own product, built and operated in-house. It uses AI to transform how organizations document, structure, and share information, making meetings, training, and project discussions instantly accessible and actionable.Up to 60%Less time on documentation- SaaSAWS costs down 30%+ for a US B2B SaaS platformunicrew became the programming team for a B2B SaaS platform that had run for over a decade, streamlined how it used AWS and Heroku, and sped up rollouts.30%+Lower AWS costs
HospitalityAdaptable booking platform for entertainment venuesunicrew developed a platform for Booked It that enhanced the customer experience for nightclub, entertainment center, and festival goers.600+Businesses using the platform
09Questions
Questions about choosing and maintaining a stack
Choosing a stack also means deciding how to take over, maintain and pay for the work.
The directory groups our software development technologies into twelve areas, from web and mobile to AI, cloud and data systems. Open a category to compare technologies used for the same part of your system; individual pages explain the language, framework or platform.
Some technologies appear in more than one category because they serve more than one role.
We start with your goals and existing systems, including compliance requirements, maintenance skills and local hiring. The written recommendation records the alternatives, cost and risk.
We validate the proposed stack with a real feature built end to end. A stack your engineers already maintain is part of the decision.
Yes. We begin with a scoped code and infrastructure review, then prioritize the work needed to stabilize the system.
The review covers dependencies and CVEs, test coverage, and the build and deploy pipeline. We document the system during delivery so your engineers can maintain it and take over releases.
Yes. We maintain and modernize older PHP code, Java EE, legacy .NET, Yii2 and on-premise SQL Server systems.
We scope maintenance and incremental modernization around the versions and dependencies in use. A strangler-pattern migration replaces parts behind a stable API, with releases planned around the system being changed.
Most engagements start within two to four weeks.
- Time and materials: billed hourly, quoted per project.
- Fixed price: outcome based, quoted per project.
- Team extension: billed monthly per team member.
Our team includes ISTQB-certified QA engineers and holders of Zend PHP and Microsoft MCSA credentials.
unicrew holds ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK. These are company certifications; technical credentials belong to the individual holder. unicrew is also a certified Laravel partner company.
Choose the delivery engagement
A system built around your workflows, scoped and delivered as custom software.
AI models, retrieval and agents developed into production software, with evaluation in CI.
A managed development team, with unicrew coordinating delivery and engineers working on your system.
ISTQB-certified QA engineers, regression suites and test automation alongside delivery.
An architecture review and written stack recommendation, with the alternatives and trade-offs.
Published systems, their technology stacks and the outcomes of the work.
Discuss the stack for your system
Tell us what the system needs to do, what already exists and who will maintain it. An engineer reviews your requirements and explains the stack recommendation, the trade-offs and the delivery scope.