Software engineering
Web applications and APIs built to survive production: schema, service, interface, and the deployment that keeps them online.
Most software fails after launch, not before it. We build the whole path: the database schema, the API on top of it, the interface people actually use, and the deployment that keeps all three running.
How we work
Every project starts from the data model, because that is the decision hardest to reverse later. From there the API is designed against real use cases, not against a wish list, and the interface follows.
Tests are written for the parts that break quietly: authentication, permissions, money, dates and anything asynchronous. Coverage as a number is not a goal; a failing test that catches a real regression is.
What you get
Running software, its source, its migrations, and a document that explains how to deploy it without us.
/What this includes
Custom web applications
Internal tools, customer portals and products, built from the schema up rather than assembled from a template.
API design and development
REST APIs with versioning, validation at the edge, documented schemas and rate limits that hold under load.
Legacy modernisation
Moving an application off an unsupported runtime or a schema nobody dares to change, without a rewrite from zero.
Quality and testing
Automated tests where failure is silent and expensive, plus a CI pipeline that refuses to ship a red build.
/Technologies
- Languages
- TypeScript
- Python
- SQL
- JavaScript
- Dart
- Backend
- NestJS
- FastAPI
- Prisma
- SQLAlchemy
- Alembic
- Celery
- Frontend
- Next.js
- React
- Astro
- Tailwind CSS
- Flutter
- Data and analytics
- Microsoft Fabric
- PySpark
- Power BI
- PostgreSQL
- InfluxDB
- Redis
- Infrastructure
- Docker
- nginx
- Caddy
- Cloudflare
- GitHub Actions
- Linux
/Related work
Newspaper portal, from empty database to daily use
A regional newspaper needed a publishing platform its own editors could run. Client project, live since August 2026 and now operated entirely by their team.
A subscription billing pipeline that survives failure
An uptime monitoring product built around the part most teams get wrong: Stripe subscriptions, webhooks and the states in between. Our own product, built to be shown rather than described.
A marketplace across mobile, web and admin
An agricultural marketplace connecting producers and buyers, with a Flutter application for the field, a React console for operations and a NestJS API behind both. Our own build.
/Questions
Questions we get asked
Can you work with an existing codebase?
Yes, and it usually starts with a read-only audit: what runs, what is tested, what is out of date and what would break first. That audit is useful even if we build nothing afterwards.
Do you do design as well?
We design interfaces for the systems we build, working from a design system rather than one-off screens. For brand identity and illustration we bring in a specialist.
Have a project in mind?
Tell us what you are building and we will tell you honestly whether we are the right fit.
Contact us