The stack we build on, and why we picked it
We are not loyal to any framework. We are loyal to shipping things that still work in two years, which usually means fewer clever choices than you would expect.
Boring where it counts
The database, the auth layer and the payment path get proven technology. Novelty belongs in the parts you can rewrite cheaply.
Chosen for your team
A stack your people cannot maintain is a liability, however good it is. We ask who inherits this before we pick anything.
Documented on the way out
Every handover includes a README that gets a new developer running locally, and notes on why the architecture is the way it is.
Eight areas, and what we actually use in each
Mobile
Cross-platform speed where it helps, native depth where it counts.
- Flutter
- Dart
- Kotlin
- Swift
- Jetpack Compose
- Android
- Expo
- Xcode
Web Frontend
Server-rendered, component-driven, measured against real devices.
- Next.js
- React
- TypeScript
- Tailwind CSS
- Vue.js
- Angular
Backend & APIs
Typed, tested services with contracts your frontend can trust.
- Node.js
- Laravel
- PHP
- Python
- GraphQL
- WordPress
Databases
Modelled properly the first time, migrated safely after that.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Firebase
- Supabase
Cloud & DevOps
Reproducible deploys, real monitoring, no mystery servers.
- AAWS
- Docker
- Kubernetes
- Vercel
- Cloudflare
- GitHub Actions
- Sentry
Monetisation & Growth
Revenue plumbing that survives store review.
- AdMob
- Google Ads
- Meta Ads
- TikTok Ads
- Stripe
- Razorpay
- Google Play
- App Store
Design & Motion
Systems and tokens, not one-off screens.
- Figma
- Framer
- Lottie
- ACAdobe CC
AI & Automation
Narrow problems, evaluated properly, costed before launch.
- Claude API
- Python
- Ppgvector
- LLangChain
- WWhisper
Not sure which stack fits?
Tell us the product, the team you have and the budget. We will recommend a stack and explain the trade-off we are making.