When work is no longer tied to one desk
Traditional programs are installed on one particular computer. Anyone working from home needs a remote connection. Anyone standing at a customer site has no access at all. Every update has to be installed on each device separately, and there is always one workstation still running an older version.
A web application runs centrally on a server. Your people simply open the browser and get to work, whether they are sitting at a Windows PC, a Mac or a tablet. New functions are there for everyone straight away, because there is only one installation.
The same applies to your customers. A portal where they can view their orders, download documents or place new orders removes a large part of the enquiries from your team. That takes a real load off, especially when the same information is given out several times a day.
Web applications we build for you
Customer portals
Your customers look up orders, invoices, delivery notes and appointments themselves. That saves enquiries by phone and email.
Internal business applications
Tools for scheduling, time recording, materials management or quality assurance, tailored to the way you work.
Booking and planning systems
Plan resources, rooms, vehicles or appointments centrally, with permissions per role and automatic notifications.
Document and form workflows
Record requests, approvals and inspection reports digitally, pass them on and file them so they stand up to an audit.
Dashboards and reports
Key figures from several systems in one place, up to date and without anyone having to collect the numbers by hand.
Ordering portals for business customers
Individual prices, framework agreements and approval levels, the way B2B business actually works.
The technology behind the interface
For the interface we mostly use React with TypeScript, because it keeps even large applications clearly structured. On the server side we work with Python and FastAPI, Node.js or PHP, depending on the project. As a database we usually use PostgreSQL. Deployment runs via Docker, so that the test and production environments are identical.
Front end
Server side
Data
Operations
How we go about it
Clarify the goal
Who is going to use the application, and which task should be easier afterwards.
Sketch the structure
We show early on what the screens look like and how you move through the application.
Build in stages
You test each stage at a real address and can make adjustments before the next round.
Permissions and roles
We define who may see and change what, and go through it together with you.
Go live and support
Move to the production server, training for your people, then ongoing maintenance if you want it.
What you get out of it
Security and data protection
Encrypted connection
All access runs over HTTPS with current certificates, including inside your own network.
Roles and permissions
Everyone sees only what they need for their work. Sensitive areas can be given extra protection.
Login with a second factor
On request with Microsoft Entra ID or an app on the phone. That is particularly useful when people log in from outside.
Servers located in Germany
On request we run the application in our own data centre, including a data processing agreement.
Common questions about web applications
Not necessarily. You can have us host the application, run it on an existing server in your own building or place it with a cloud provider. We advise you on the basis of user numbers, data volume and your data protection requirements, so you know what makes the most sense in your case.
For normal use a standard business line is perfectly sufficient. If your people regularly work in places without reception, we build parts of the application so that data is stored temporarily and transferred later. That does have to be planned in from the start.
Yes, that is one of the most common cases. We fetch the data you need from your existing system through an interface, without changing anything there. Depending on the requirement this happens in real time or at regular intervals.
We design web applications so that they adapt to the screen size. For tasks that are often done on the move, we design a reduced view with large controls. A separate app is usually not needed for that.
We set up regular backups and check that they can actually be restored. For applications that the business depends on, we also recommend a second server that takes over when needed. How far you take this depends on your requirements and your budget.
Yes. You receive the source code and the documentation. If you have your own developers, they can carry on from there. Many customers still leave further development with us because it is quicker that way, but you are not tied to us.
Let’s talk about your web application
Customer portal, internal tool or ordering platform: tell us who is going to work with it and which task it has to make easier. We will sort out the rest together.