Technologies We Use
The stacks we build on — chosen for maintainability, not novelty.
We are deliberately unromantic about technology. The right choice is the one your team can maintain, that hires well in the Saudi market, and that will still be supported in five years. Here is what we work with.
Start a Project →Frontend
React, Next.js, Vue, Nuxt, Astro, TypeScript, Tailwind CSS
Backend
Laravel, Node.js, NestJS, Django, .NET, Go
Mobile
Swift, Kotlin, Flutter, React Native
CMS
WordPress, Drupal, Strapi, Sanity, Payload
Ecommerce
Salla, Zid, Shopify, WooCommerce, Medusa
Data
PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch
AI & ML
OpenAI, Anthropic, Llama, Qwen, DeepSeek, LangChain, pgvector
Cloud & DevOps
AWS, Azure, Google Cloud, Docker, Kubernetes, Terraform, GitHub Actions
How we choose a stack
Three questions decide almost every technology decision we make.
Who maintains this after handover?
If your internal team writes PHP, a Go microservice architecture is a liability regardless of its benchmarks. We optimise for the team that inherits the system.
What does it integrate with?
If the project lives or dies on an ERP connection, we choose the stack with the most mature client library for that ERP and accept trade-offs elsewhere.
What is the five-year support picture?
We avoid frameworks with a single corporate sponsor and no community, and we avoid versions approaching end of life. Boring, well-supported technology is a feature.
- Written stack recommendation with trade-offs before build
- Infrastructure as code so environments are reproducible
- Automated testing and CI/CD from the first sprint
- Dependency and security scanning in the pipeline
- Documentation and handover training as a deliverable
- No proprietary lock-in — you can take the code anywhere
Frequently Asked Questions
Which technology stack is right for my project?+
It depends on your team, timeline and integration needs — not on what is fashionable. We recommend a stack during scoping and explain the trade-offs in writing, including what it costs to maintain in three years.
Can you work with our existing codebase?+
Yes. We regularly take over legacy PHP, WordPress and .NET systems. We start with a code and security audit so you know exactly what you are inheriting before committing to a roadmap.
Do you self-host AI models?+
Yes. Where data cannot leave your infrastructure we deploy open-weight models such as Llama, Qwen or DeepSeek on in-Kingdom servers or your own hardware.
Do you provide DevOps and hosting?+
Yes. We set up CI/CD pipelines, infrastructure as code, monitoring and backups, and can either manage them ongoing or hand them to your internal team with documentation.