Frontend
ReactNext.jsVueNuxtTypeScriptTailwind CSSViteAstroStorybook
Home › Tech stack
Tech stack
Considered defaults, selected per project.
We maintain default technology choices because their failure modes are known to us. If your team already runs something well, we work in your stack rather than arguing for ours — and we will say plainly when a technology choice is a genuine risk.
By layer
What we build with, grouped by layer.
Backend
Node.jsNestJSPythonFastAPIDjangoJavaSpring BootGo.NET 8PHP / Laravel
Mobile
Swift / SwiftUIKotlin / Jetpack ComposeReact NativeFlutterExpoFastlane
Cloud & Platform
AWSMicrosoft AzureGoogle CloudKubernetesDockerTerraformCloudflareVercel
Data
PostgreSQLMySQLMongoDBRedisSnowflakeBigQuerydbtApache AirflowKafkaElasticsearch
DevOps & Observability
GitHub ActionsGitLab CIArgoCDPrometheusGrafanaDatadogSentryPagerDuty
AI & ML
PythonPyTorchscikit-learnLangChainLlamaIndexpgvectorPineconeMLflowHugging Face
How we choose
Three criteria governing every stack decision.
Boring beats clever
The interesting technology should be in your product, not your infrastructure. We pick the option with the largest hiring pool and the longest support horizon unless there is a concrete reason not to.
Your team has to maintain it
If a choice means only we can maintain the system, it is the wrong choice. Stack decisions are made with your hiring reality in mind.
Decisions get written down
Significant architecture choices are recorded as short decision records — what we chose, what we rejected, and why. Six months later, nobody has to guess.
Retaining an existing stack?
Send us the repo structure or an architecture sketch. We will tell you what we would keep, what we would change, and what we would not touch.