APIs and integrations
Making systems that were born apart talk to each other: management system and site, shop and warehouse, CRM and invoicing. We build the missing API too, when the system to connect exposes none.
Integrations, security and infrastructure for web applications
Two programs that do not talk, and a person bridging them by copying data across by hand. An application online that nobody has checked in a year. A supplier who left with a few credentials handed over and no documentation. Those are the three reasons people end up here, all three are fixable, and none of them improves by waiting.
What we build
The foundations: integrations, security, infrastructure, maintenance.
Security and reliability
A review of what is exposed to the outside: authentication, permissions, input validation, headers, ageing dependencies. It produces a list of things to fix, ordered by what it costs not to.
Infrastructure and maintenance
Hosting, automated releases, backups, monitoring. Anyone inheriting a project with no documentation gets, first of all, a map of where everything lives and who has access to what.
Web3 and smart contracts
Solidity contracts, developed and verified on testnet. We propose it when a blockchain genuinely solves a trust problem between parties who do not know each other, and advise against it in every other case.
Who it makes sense for
Who it makes sense for
- Companies where somebody spends the day moving data between two programs that ought to talk.
- Anyone with an application in production that nobody has checked in months, with no idea if it is still safe.
- Anyone who inherited a project from another supplier, with a few credentials and no documentation.
- Anyone who needs somebody to answer when something breaks, and today has nobody.
Frequently asked questions
Frequently asked questions
Do you work on projects you did not build?
Yes, and it is a good share of the work. It always starts with a read of the code and the infrastructure, to know what is there before promising anything. If the project is in a state where rebuilding beats repairing, we say so with the numbers in hand.
What does maintenance cover?
Security updates, monitoring, fixing failures, and an agreed block of hours for changes. What it does not cover is written down as plainly as what it does, because that is where misunderstandings come from.
How much does a security review cost?
It depends on how large the exposed surface is. For a single web application with its private area we are talking days rather than weeks, and it produces a document listing the issues by severity with an estimate of what fixing them costs. Fixing them is separate work, which you can have done by whoever you like.
Do we actually need a blockchain?
Almost always no, and we will tell you. It is needed when two parties who do not trust each other must share a state with no intermediary. If there is an intermediary both already trust, a database is cheaper, faster and repairable.
Where do you host projects?
Vercel for web applications and Supabase for data, unless requirements say otherwise. The accounts are in your name: we work inside them, we do not sit between you and them. If you must stay on your own infrastructure, or inside Europe, we set it up that way.
Shall we talk about it?
Tell us about the process that does not work. We reply within 24 hours, with a first 30-minute call and no commitment.
Let's talk about your projectThe other solutions