Technologies

Choose a stack your team can hire for in five years

We build with mainstream, well-documented technology and say no to anything your next developer would struggle to maintain. This is the list.

A terminal window beside a git commit history
The stack

6 groups, 38 technologies

Grouped by where they sit in a product. A technology outside this list is not off the table; it means we will tell you honestly whether we are the right team for it.

Front-end technologies

Front-end

ReactNext.jsTypeScriptVue.jsAngularTailwind CSSHTML5 / CSS3
Mobile technologies

Mobile

FlutterReact NativeSwift (iOS)Kotlin (Android)Expo
Back-end technologies

Back-end

Node.jsPython (Django, FastAPI)PHP (Laravel)Java (Spring Boot).NET
Data technologies

Data

PostgreSQLMySQLMongoDBRedisSupabaseFirebase
Cloud & DevOps technologies

Cloud & DevOps

AWSAzureGoogle CloudDockerKubernetesGitHub ActionsCloudflarecPanel / LiteSpeed
Integrations & AI technologies

Integrations & AI

StripeTwilioResend / SendGridSalesforceHubSpotQuickBooksClaude & OpenAI APIs
How we choose

Three rules decide every stack

Hiring developers for a mainstream stack
01

Hire-ability beats novelty

If you cannot hire three developers for it in your city or time zone within a month, we do not build your core product on it.

Matching the hosting a company already runs
02

Match the hosting you already pay for

A PHP application on the cPanel account you own is often the right answer. We size infrastructure to the product, not to a conference talk.

One codebase serving both app stores
03

One codebase per platform pair

Flutter or React Native for iOS and Android together; native Swift and Kotlin only when hardware access or performance demands it.

Have a stack in mind already?

Tell us what it is and why. We will say in writing whether we would build on it, and what we would change.