Web application and platform development
Platforms whole teams work in, every day. Admin panels, client portals, internal applications — built with care for the part demos rarely show: what happens with a hundred users at once and a million rows in the table.
What we actually build
Not brochure sites. Applications people spend hours in: management systems, portals where clients track their orders, panels teams run the business from, platforms with several kinds of user who each see something different.
The kind of application where a slow page is not an annoyance but a cost: if an operator waits three seconds per search and runs two hundred searches a day, that is ten minutes per person, every day.
Speed is designed in, not added at the end
An application that is fine at a thousand rows and stalls at a million does not have a server problem, it has a design problem. Indexes, pagination, what is computed on write versus on read — all decided early, because changing them later means rewriting.
We render on the server what has to be fast on first load and leave only interaction to the browser. That shows up in speed and in search: a page that delivers its content in HTML is indexable; one that assembles it from JavaScript after load may not be.
Multi-tenancy, roles and permissions
Almost every platform ends up with several kinds of user: administrator, operator, client, perhaps partner. Each sees something different and can do something different.
We treat that as a security problem, not an interface one. A hidden button is not a permission — the check happens on the server on every request, and important actions leave an audit trail: who, what, when. When two clients share one application, data separation happens at the query, not at a filter in the screen.
Hosting, scaling and replication
We integrate directly with AWS, Microsoft Azure and DigitalOcean. We pick the region based on where your users are and where the data has to live — for a European company usually Frankfurt or Ireland, which keeps data inside the EU and simplifies the GDPR side.
As traffic grows the application scales horizontally and the database gets read replicas. Backups are tested, not just taken: a backup you have never restored from is an assumption, not a safety net.
What you get
- The application, in productionHosted, with a TLS certificate, domain and monitoring.
- Admin panelWith roles, permissions and an audit trail.
- Documented APISo you can integrate other systems without asking us.
- Daily backups, testedWith a restore procedure that has actually been run.
- Monitoring and alertsWe find out something broke before your clients do.
- Source code and runbookIn your repository, with operating instructions.
What we build it with
- Next.js
- React
- TypeScript
- Tailwind CSS
- Java
- Spring Boot
- Node.js
- NestJS
- Python
- PostgreSQL
- Redis
- ClickHouse
- Elasticsearch
- AWS
- Microsoft Azure
- DigitalOcean
- Cloudflare
What a web application costs
from €599
A platform with one user role and one main flow starts at the entry package. Those with several roles, external integrations, reporting and large data volumes fall into the higher ones. The monthly price after launch covers hosting, monitoring and security updates, and varies with the resources consumed.
Frequently asked questions
What is the difference between a website and a web application?
A website shows information. A web application keeps track of data that changes, has users who sign in, different roles and workflows. The difference in effort is roughly an order of magnitude.
Will the application work well on a phone?
Yes, every interface we build is responsive. For workflows used heavily in the field we will discuss whether a native mobile app is the better choice — sometimes it is, and we will say so.
Where will the data be hosted?
In the European Union by default. We work with AWS, Azure and DigitalOcean and choose the region based on where your users are. Data that never leaves the EU makes compliance considerably simpler.
What happens if traffic spikes?
Applications are built to scale horizontally: we add instances and read replicas on the database. Monitoring warns us before it becomes visible to users.
Can we start small and extend?
That is our model. Start with the flow that matters, get it into production in 2-3 months, and extend based on what real use shows you.
Tell us what you want to build
Three steps, a few minutes. You get a code to follow your request and the project's progress in real time.