Technologies
Modern, mainstream technology your team can hire for and maintain.
We build on a small set of widely used technologies, so the software is fast to build, easy to staff, and straightforward to maintain. Here is what each one is for, when we choose it, and when we reach for something else.
- InterfaceReact · Next.js
- MobileReact Native
- ServicesNode.js · TypeScript
- DataPostgreSQL · Python pipelines
- AIOpenAI · Anthropic · chosen per task
- CloudAWS · Azure · Google Cloud
React and Next.js
The interface layer for the web applications and sites we build.
Read ServicesNode.js
The services layer: APIs, integrations, and the logic behind the screens.
Read DataPython
The data and AI layer: pipelines, analysis, and model integration.
Read MobileReact Native
iOS and Android apps from one codebase, on the same backend as the web.
Read AIOpenAI and LLM application development
Language models inside business software, with the controls around them.
Read CloudAWS
AWS applications on managed services, with the operations built in.
ReadHow we choose
The principles behind our stack.
Mainstream over novel
Widely used, well-supported technology, so the software is easy to hire for, maintain, and extend for years.
Fit to the job
Each layer is chosen for what the application must do, and where a client standard names another technology, we build to that standard.
Managed over self-run
Managed databases, queues, and hosting replace servers someone has to patch, which means fewer failures and less to operate.
Typed and tested
TypeScript and typed Python, with automated tests on the logic, keep the code readable for the next engineer and safe to change.
A note on choice
The stack serves the business, not the other way around.
Where a client standard names another technology, we build to the standard. Where a vendor product already does the job, we say so. Each page here describes how we work with the technology and why.
Questions
Questions about our technology.
What business and technology leaders ask us first.
Can you work with our existing technology?
Yes. For an existing product we work in its stack and conventions. Our default stack applies to new builds, and any recommendation to change technology comes with the reasons, before anything is decided.
Why these technologies?
They are among the most widely used for business applications, with large hiring pools, long-term support, and mature tooling. That keeps the software maintainable by your team or any future one.
Do you use AI tools in development?
Yes. Senior engineers use the latest AI tooling on every task, from drafting code to writing tests, and review everything before it ships. The tooling speeds up the work; the engineers stay accountable for it.
Which cloud platforms do you build on?
AWS, Azure, or Google Cloud, whichever you already use or best fits the application, with infrastructure defined in code, tested backups, and monitoring from the first release.
Tell us what you are trying to build.
A workflow, a product, or a system your team has outgrown.We’ll come back with what we would build first, and which tools we would use.