—Services

Services, prices and the engineers behind them.

The stacks our engineers work in, what working with us costs, and what we build with it. Most of our work is ongoing work on systems that are already in production.

Stacks

What we have engineers for.

Looking for someone for your project? These are the stacks our engineers work in — as team extension inside your repository, or on a retainer for your system.

Backend · PHP
PHPLaravelSymfonyMySQLPostgreSQLREST API

Our main stack: application backends, APIs and integrations in PHP and Laravel — including systems several framework versions behind.

Backend · Node.js
Node.jsJavaScriptREST API

Services and APIs in Node.js, when your system already runs on it or the problem belongs there.

Frontend · React
ReactTypeScriptJavaScript

Web interfaces in React: dashboards, internal tools and public sites that talk to your backend.

Mobile · iOS & Android
iOSAndroidReact Native

Apps for iPhone and iPad first, and for Android too — with a backend from the same team.

.NET · on request
.NET

For .NET systems we work with a freelance engineer we bring in for the project.

Formats and prices

Five ways to work with us, each with a price.

We suggest starting with the System-Check: afterwards both sides know what a retainer has to cover.

System-Check
€1,290fixed price
Three working days · credited

Three working days in your code, database and deployment, then a written report and a call: what the system really does, where the risks sit, what an upgrade path costs. Credited in full against a retainer that starts within 60 days.

Team extension
from€8,400/ month
per full-time engineer

Our engineers work in your repository, your review and your release process. You lead, we supply capacity — without you having to hire.

Project
Fixed price
once the scope is in writing

A defined piece of work with a written scope, milestones and a handover. The price is fixed before the work starts.

Consulting
€520/ day
with a written result

Review of an architecture, a codebase or a vendor proposal, with a written result.

Reading as
7 capabilities
Entry A
Building something new

Concept to first release. The technology is chosen for the problem, and the first version stays small on purpose.

01

Websites & Web Applications

Public sites and the applications behind them — from a single marketing site to a multi-role platform.

PHPLaravelSymfonyReactTypeScriptPostgreSQL
Server-rendered by default — a marketing site that depends on client-side JavaScript to show its own text is a liability. For a single-location local business this is productised as Digital Basics.
  • Multilingual marketing sites — with a CMS when the content changes often
  • Authenticated applications: roles, permissions, audit trails
  • Dashboards and internal tools built on real data models
02

Mobile Applications

Apps for iOS and Android, talking to an API we can also build and run.

iOSAndroidReact NativeREST API
The app and the backend come from the same team, so the API and the app are planned together instead of one side waiting for the other.
  • Apps for iPhone and iPad first, and for Android too
  • Offline handling, background sync, push notifications
  • Store submission and release management
03

Backend & APIs

Services, integrations and data models that other systems depend on.

PHPLaravelNode.jsMySQLPostgreSQLREST API
The data has to outlive the application on top of it, so the data model comes first. One API surface, so mobile and web cannot drift apart.
  • REST APIs for web, mobile and third-party clients
  • Payment, logistics, ERP and CRM integrations
  • Queues, scheduled jobs and long-running processing
04

E-commerce & Business Systems

Selling, billing, stock and fulfilment as one connected system rather than five disconnected tools.

PHPLaravelMySQLStripeAWS
Orders are financial records, so they are append-only and auditable. Nothing about an order is edited in place.
  • Custom storefronts and checkout flows
  • Order, inventory and fulfilment logic
  • Invoicing, tax and accounting hand-off
Entry B
Working on what exists

A running system with history. The existing stack is usually the right one to continue with.

05

Legacy Systems

Applications that are already in production, already earning, and nobody wants to touch.

PHPSymfonyLaravelMySQLJavaScript
We continue in the stack that is already there. A rewrite is a business decision, not a technical preference, and it is rarely the cheap option.
  • Reading and documenting an inherited codebase
  • Getting an undocumented system into local and CI environments
  • Framework and language version upgrades in steps
  • Extending without a rewrite; rewriting only where it pays
06

Maintenance & Modernisation

Staying with a system after launch: updates, monitoring, and the small changes the business keeps needing.

GitGitHub ActionsDockerSentryAWS
Monitoring before optimisation. We measure real traffic before changing anything for performance.
  • Dependency and security updates on a schedule
  • Monitoring, logging and error budgets
  • Performance work on real traffic, not synthetic benchmarks
  • A named engineer who knows your system
07

AI integration

Putting AI assistants and language models into products that already exist — on your data, inside your workflow.

LaravelJavaScriptLLM APIsREST API
The provider stays replaceable: access runs through a layer of our own, so changing model is not a rebuild of the product. Cost per request is measured before anything goes live.
  • Chat assistants grounded in the company's own content and data
  • Third-party AI services behind a layer that isolates the provider
  • Cost and usage control per request
  • An explicit line between what the model decides and what a person does
07Technology as a decision
PHPLaravelSymfonyNode.jsJavaScriptTypeScriptReactReact NativeMySQLPostgreSQLAWSDocker
The right technology is the one your system can still be maintained with in five years.On choosing a stack

We work across several stacks rather than selling one. Where a system already exists, continuing in its stack is usually cheaper than being right about a better one. Where nothing exists yet, we choose per requirement — data shape, integrations, team, hosting, and how long the thing has to live.

08Where you are on the line
  1. Day 0

    It ships

    A first release small enough to put in front of real users, and structured so the second release does not require a rewrite.

    LaravelReactPostgreSQL
  2. Day 100

    It changes

    The data model that looked right at launch meets how the business actually works. Integrations arrive. Someone asks for a report nobody planned.

    REST APIDocker
  3. Day 1000

    It is inherited

    The people who wrote it have moved on. The framework is three majors behind. The system is still running the business.

    PHPSymfonyMySQL
    This is where most projects reach us
Languages
German · English · Spanish
Working with
Businesses in Germany and across the EU
Hosting
EU-based, or your own infrastructure
09Next

See how this looks in production.

Client work, anonymised platform experience, and our own conceptual product studies.