The technologies we build on
Tools we use often, and the reason we pick each one.
Web
For sites and apps that load fast and can be read by search engines.
Next.js
Renders pages on the server, so content reaches search crawlers and visitors quickly.
TypeScript
Catches many mistakes before release and makes code easier to hand over.
React
A widely known way to build interfaces, so other developers can pick the work up.
Mobile
For apps on iPhone and Android from one codebase.
React Native
Shares most code between iOS and Android, which keeps first versions affordable.
AI
For assistants and features that work on your own information.
Open-weight models on your servers
Keeps sensitive documents inside your own environment when privacy comes first.
Major AI providers
Strong models with little setup when your data terms allow it.
Retrieval over your documents
Answers come from your material and can point to the source.
MCP connectors
Lets an assistant read from tools you already use, through one standard interface.
Cloud
For releases that are repeatable and watched.
Docker
Packages the app so it runs the same on a laptop and on the server.
CI/CD
Tests and deploys every change the same way, so releases are small and reversible.
Monitoring
Tells us about downtime and slow pages before your customers do.
Search
For being found by people and by AI assistants.
schema.org
Labels your business, services and questions in a form software can read.
Search Console
Shows how Google crawls, indexes and ranks your pages, with real data.
Analytics
Shows what visitors do after they arrive, set up with consent in mind.
Questions we get
Do you only work with these tools?
No. These are what we reach for most often, and we pick the tool that fits your project. If you already have a stack, we will work with it where it makes sense.
Will I own the code?
Ownership is agreed in writing for each project, and we aim to hand over the code with notes so another developer can take it on. Settle this in the scope.
Can an AI assistant run without sending data to a third party?
Yes. An open-weight model can run on servers you control, with retrieval over your own documents. It needs hardware and care, and we will explain the trade-offs against using a major provider.
Tell us what you’re building.
- A call about the goalThe budget, the deadline and what success looks like.
- A written scopeWhat we build, in what order, and the quote.
- Work in sprintsA demo at the end of each one.