This page is only available in English. Diese Seite gibt es nur auf Englisch.
Software development
Admin panels and back-office apps on EU infrastructure, with code you control.
Updated November 2026
You’ll talk to the engineer who will build your project.
We work exclusively with businesses and self-employed professionals. All offers exclude VAT.
At Datafalke, admin panel development covers the internal tools your staff use to manage business data: admin panels, back-office apps and admin dashboards. We connect them to the databases and systems you already use, with roles for each team. Hosting runs in your own account, with EU-based providers, and the code is in your repository from day one.
Datafalke is based in Bottrop, Germany. Every project is led by software engineer Mohammad Alboush, who heads our team. Projects run in English or German. We work remotely across Germany and the EU, and in person in the Ruhr area.
If your process still runs on spreadsheets or Access, start with custom business software. If your customers are the users, see customer portals.
Software development overviewAll servicesA process check or discovery sprint first, with a data model. If an existing platform fits better, we’ll tell you.
Views to search and edit the records your team manages, connected to your databases and systems.
Each role sees and changes only what it needs, and the server checks permissions on every request.
The tool runs in your own cloud account, and we plan it around EU-based providers. We disclose every service that processes your data.
Repository in your account from day one; at sign-off, architecture docs, an operations manual and a software bill of materials (SBOM).
If you’d like, software care: updates, monitoring and two hours of work a month. Your own team can also take over.
Recurring tasks where staff look up, change or approve records that live in your databases and systems. The examples below show typical internal tools, not client projects.
Manage accounts and subscriptions, and help customers without giving support staff access to the database.
Check order status and handle returns or credits in one place.
Requests for discounts or system access go to the right person, and each decision is recorded.
Key figures and open tasks from several systems on one screen, for the people who act on them.
Master data such as products and prices, edited with validation instead of in spreadsheets or directly in the database.
A low-code platform is often the faster way to standard screens over your data; if that’s all you need, we’ll recommend one. A custom build pays off when your rules go beyond what a platform offers or when per-user fees would keep growing. It also gives you code that doesn’t depend on a platform vendor.
Good for standard screens over your data. Your apps run on the vendor’s servers, and on many platforms, fees grow with every user.
Good if data must stay on your own infrastructure but the screens are standard. Unless the vendor manages it, updates and operations are your job.
Good for your own rules, many or external users and a long service life. More work up front, then no license fee per user for your own code.
Researchers at the University of Duisburg-Essen studied ten low-code platforms. They found that the platforms save effort mainly on routine work in projects of low to moderate complexity. That depends on every requirement fitting the platform’s predefined framework. According to the authors, what you build on one platform usually can’t be used on another (Bock and Frank, 2021 (external site)).
If data location is your main concern, a self-hosted platform may be enough. As of November 2026, Retool offers self-hosting on its Enterprise plan. Appsmith, Budibase and ToolJet publish the core of their platforms as open source, which you can run on your own servers.
Our comparison Low-code vs. custom development covers license costs over five years and how to plan your exit. If off-the-shelf software might cover the task, read Build vs. buy software.
A secure admin panel checks permissions on the server for every request and gives each role only what its job needs. It asks for more than a password at sign-in and logs security events. Broken access control ranks first in the OWASP Top 10:2025, which describes the most critical security risks to web applications.
The requirements below come from the OWASP Top 10:2025 (external site), the OWASP Application Security Verification Standard (ASVS 5.0 (external site)) and OWASP’s cheat sheets on authorization (external site) and logging (external site). ASVS sorts its requirements into three levels of increasing depth.
Hiding a menu item doesn’t protect a function. ASVS 5.0 requires authorization at a trusted service layer, because code in the browser can be manipulated.
A support agent can look up an account but can’t change billing data. OWASP calls this least privilege.
ASVS Level 2, the level the standard says most applications should aim for, requires more than a password at sign-in.
OWASP advises leaving sign-in to a well-tested system. Single sign-on with your company accounts is one way to do that.
Starting at Level 1, ASVS requires that default accounts such as “admin” or “root” don’t exist or are disabled.
Starting at Level 2, ASVS requires logging successful and failed logins as well as denied access attempts.
OWASP’s logging guidance also lists user administration, such as changes to privileges; actions by administrators; and data exports among the events to log where possible.
Together, we agree on which events your tool records, who can read those records and which of these requirements apply. They become part of the written acceptance criteria for sign-off.
In your own cloud account. We plan your tool around EU-based providers and disclose every service that processes your data. In a 2026 Bitkom survey of companies in Germany, 97% said the location of data centers plays a role when they choose a cloud provider.
Source: Bitkom (external site), · 603 companies in Germany with 20 or more employees
Among the companies for which location matters, 51% ruled out data centers in the US.
We set up the account with you and work in it with delegated access. If your company already has a cloud provider, the tool can run there. Our colophon shows how we host this website.
By video, or in person at your office if you’re in the Ruhr area of Germany. The call is free, and you talk directly to the engineer who will build your tool.
A process check if the tool takes over an existing process, a discovery sprint for something new, such as the admin panel for your product. Both are paid entry offers, each with its own deliverable.
We work in short cycles and show you where things stand every week. The code is in your repository from the start.
You review the tool against the criteria we agreed on in writing, including who may see and change what. At sign-off, you receive the documentation and the software bill of materials.
After that, we can keep looking after the tool if you’d like. Your team or another provider can also take over.
We built, ran or documented these examples for our articles. The Excel and Access examples use test data rather than client data.
All examples come from our own project or from test data. None of them comes from client work.
You can carry on without us if you need to. Code, hosting account and domain are under your control from day one, and every sign-off includes documentation another team can work from.
Repository, cloud account, domain and credentials are in your name. We work with delegated access.
Architecture docs (arc42, C4), decision records, an operations manual and a software bill of materials (SBOM) come with every sign-off.
If we part ways, we hand over all documentation to your team or new provider. Your contract sets out how the handover works.
We use widely adopted open-source frameworks, not homegrown tools only we understand.
Mohammad Alboush is a software engineer and the owner of Datafalke. He’s your direct line to the team, from the intro call to sign-off. He replies to requests within one business day (Monday to Friday).
You start with a process check or a discovery sprint, both paid entry offers, each with its own deliverable; we tell you their price before you place an order. After that, we quote a fixed price for building your tool. The factors that drive that price are listed below the packages.
Businesses running processes in spreadsheets or Access
Price in your quote
Excl. VAT, business clients only
Founders and companies with a product idea
Price in your quote
Excl. VAT, business clients only
Software care S covers updates, monitoring and two hours of work a month, for at least three months. Software care L is by agreement. Changes outside the fixed price start only once you approve them.
We work exclusively with businesses and self-employed professionals. All offers exclude VAT.
Usually, yes. In the process check or discovery sprint, we work out how the tool connects to your data. That can be directly to a database, through an API or through regular exports. We confirm the approach before you get a fixed price.
Yes. If we build your SaaS product, an admin area is part of the SaaS MVP; see how we build SaaS products. For an existing product, we connect the admin panel to its database or API, so your support team can help customers without direct database access.
Yes, as a new build. What you build on one low-code platform usually can’t be used on another. So we rebuild the screens and logic as your own code and migrate the data. Before you decide, the process check or discovery sprint shows how much work that will take.
No. Your code and accounts are under your control from the start, and we use widely adopted open-source frameworks instead of homegrown tools. The exclusive usage rights to the code we write for you pass to you on full payment. Open-source components keep their own licenses. So you can switch to another team at any time. More on this in our how-to on avoiding developer lock-in.
Then your team or another provider carries on, because your code, hosting and domain run on your own accounts from day one. Every sign-off includes architecture documentation, an operations manual and a software bill of materials. If we part ways, we hand over all documents; your contract sets out how the handover works.
You’ll know the price of development before it begins, because we build at a fixed price after the analysis. Changes are made only through a written change request that states the price, and you see the budget status in every weekly demo. Your quote sets out the payment terms.
Talk to your works council (Betriebsrat) early, especially if the tool records what individual employees do. Ask your employment lawyer whether the tool needs the council’s approval before rollout. The agreed list of what the tool records and who can read it helps in that conversation.
Yes. Projects run in English or German, and your documentation and the tool itself can be in either language. Datafalke is based in Bottrop, Germany; we work remotely across Germany and the EU, and in person in the Ruhr area.
Comparison · SaaS & software
What low-code licenses cost over five years, where platforms hit limits, how to plan your exit and when custom development pays off. With a checklist.
Comparison · SaaS & software
Off-the-shelf or custom? Five-year costs, flexibility, lock-in and data control for small and mid-sized companies, with a decision tree and worked examples.
Cost guide · SaaS & software
What custom software development costs: euro price ranges for web apps, customer portals and SaaS, hourly rates, maintenance and the main cost drivers.
How-to · Business software
How to tell Excel has reached its limits as a database, which option fits and how to switch: inventory, data model, data migration and parallel running.