Web platforms
We plan the application with you and build it, from the first concept to the finished product. Then we keep developing it and we operate it.
An application your customers use is never just the application. Around it sit the content your team needs to edit, the payments, the hosting and the deployment. Each one is a decision, and each one has to work with the others. So we plan them with you before we build, and we build them as one product.
Much of our web work is on applications that are already live, with customers on them. There the trouble is rarely inside one part. It’s between them: a wording change that needs a deployment, a payment that went through but never reached your books, an upgrade nobody dares to start. So we change one part while the rest keeps running, in your project and through your own release process. When we build new, we build on Next.js, PayloadCMS and PostgreSQL.
- Next.js
- TypeScript
- React
- Node.js
- Bun
- PayloadCMS
- PostgreSQL
- MySQL
- Supabase
- Ruby on Rails
- Vercel
- Docker
- Stripe
- PayPal
- Revolut
- Alipay
What we do.
You’re building a new application.
We start with the plan: what the product has to do, who uses it, and what it needs around it to run as a business. Then we build it, from the first version to launch. Content your team edits, payments and hosting are part of that, and so is the release process. After launch we keep developing it and we operate it.
Your team can’t change a word on the site without a developer.
If every wording change needs a developer, the wording doesn’t get changed. We build on PayloadCMS. The content lives with the application, and the people who own the words edit them themselves.
You need to take payments.
Which provider, which currencies, and what happens when a refund or a failed charge has to reach the rest of your system. We settle those with you before anyone writes code. We’ve integrated Stripe, PayPal, Revolut and Alipay. Most of that work was in the webhooks and in matching payments to your records, not in the checkout page.
You need to be sure users only ever see their own data.
Check permissions in the application, and every new piece of code that reads the data is a new place to get it wrong. We put the rule in the database instead, with Row Level Security, so Postgres enforces it for everything that connects. That’s how the logistics platform below works.
Nobody’s looked after the platform since it launched.
Dependencies go stale, the framework moves on, and every change costs more than the last one. We’ll look after it, if you want us to. Upgrades, security patches and the next feature, under the same contract.
Tell us what you’re building.
Our clients are in the DACH region and across the EU, and we work with all of them remotely.