Appfront is a web app and app developer for organisations in Utrecht, from Rabobank and ASR in the financial sector to the UMC, Utrecht University and startups at the Dutch Game Garden and ITSU. We build customer portals, single-page applications, dashboards and complete web apps, including back end and integrations. We operate from our Amsterdam office, with sprint sessions on site in Utrecht where that adds value.
Utrecht sits at the heart of the Netherlands and has a distinct, clearly defined economy: a heavy financial cluster around Rabobank and ASR Insurance, a large healthcare and life sciences ecosystem centred on UMC Utrecht, a technology layer with firms such as Capgemini and Centric, two major knowledge institutions (Utrecht University and Utrecht University of Applied Sciences), and a lively startup scene at the Dutch Game Garden and the ITSU Utrecht Startup Hub. A web app that has to fit this context calls for a developer who understands the rules of financial supervision, healthcare compliance and public procurement.
At Appfront we build web apps that have to run in production. We do web development at the level of customer portals for banking and insurance, patient environments for healthcare, LMS and education platforms, and MVP builds for startups heading towards their first serious release. Strategy, design, code and release management come from one team, so advice and delivery never drift apart.
Whether you're a Rabobank or ASR spin-off with a customer portal challenge, a UMC research group with a data application, a city department in Utrecht with a citizen portal, or a Dutch Game Garden start-up ready for its first single-page application: we adapt our role to what you need. Sparring partner, builder, or both.
Asset portals, claims self-service, mortgage flows, advisory tools. We work for clients in the financial sector and know the requirements: the DNB and AFM context, strong audit trails, robust authentication and EU-only data.
Patient portals, research tooling, registration applications and monitoring dashboards. NEN 7510, GDPR and, where needed, MDR requirements are part of the architecture from sprint one, not a last check before go-live.
LMS integrations, student portals, assessment and feedback tools, applications built on top of existing systems such as Osiris or Canvas. We work with SURFconext and federated identity so single sign-on keeps working smoothly for students and lecturers.
Citizen portals, case management applications, intake workflows and internal tools for civil servants. We work in a procurement-friendly way, using open standards, remaining vendor-neutral and avoiding lock-in to a single supplier.
Your current MVP has reached the end of its useful life, or you are approaching your first serious release. We help with a redesign, platform choices and the foundations you need to grow without stumbling with every release. See also financial services software for financial MVPs.
Capgemini, Centric, ICTU, Pinkroccade, Topicus: Utrecht has a dense technology sector. We often work as a specialist web application team alongside or on top of an existing engineering team, either adding capacity for a specific application or delivering a full-stack build for a new product line.
We deliver working web applications in your own cloud environment and repository. Code lives in your own Git, and the backend infrastructure runs under your own AWS, Azure or GCP account (EU regions). No lock-in to us, and no lock-in to a single vendor. Your team can take over whenever you choose.
Web apps for Rabobank, ASR, UMC or Utrecht municipality contexts are not the same as consumer web apps. Strict audit trails, NEN 7510 or ISAE requirements, strong authentication and procurement-compliant choices call for a developer who has done this before.
We are not a consultancy machine with hundreds of staff, but nor are we a single freelancer who leaves you in the lurch after a few months. We do mature work: direct conversations with your architect, delivery through a reliable CI/CD pipeline, and ongoing support for as long as you need it.
What we do for clients in and around Utrecht, from initial exploration through to production release and ongoing support.
Wealth, claims and advisory portals for clients in the financial sector. Strong authentication, audit trails and EU-hosted data.
Patient, research and registration applications delivered NEN 7510-compliant from sprint one.
High-performance single-page applications in React, Vue or Svelte, for dashboards, configurators and operations tools.
Student portals, assessment and feedback tools, and applications built on SURFconnect, Osiris or Canvas. For UU, HU and publishers.
Application workflows, case management applications and internal tools for civil servants. Procurement-friendly and built on open standards.
REST and GraphQL on top of ERP, CRM, EHR or existing core systems. Identity, payments, push events and monitoring included.
Fast progression from idea to working MVP for DGG and ITSU startups. Scalable, with a foundation that can handle the next phase.
A web application with a mobile companion built in React Native or Flutter, useful when field staff or healthcare professionals also need to work on mobile.
Utrecht has its own mix of finance, healthcare, education, public sector and startups. Our clients usually fall into one of these profiles.
Spin-offs, subsidiaries and suppliers within the Rabobank cluster. Customer portals, intermediary tools and advisory applications. Strong authentication, audit trails and strict change procedures are part of our everyday work.
Claims portals, policy environments, intermediary tools and internal workflow applications for ASR and related insurance players. See also our financial sector page.
UMC research groups, healthcare providers and healthcare start-ups that need web apps and patient portals. NEN 7510, GDPR and MDR requirements are built in from the very first sprint, not added after delivery.
Capgemini, Centric, ICTU, Topicus and smaller tech players in Utrecht. We often work as a specialist web app team alongside an existing engineering team, either to add capacity or to build a full-stack solution for a new product line.
Student portals, research tooling and web apps built on top of Osiris, Canvas and SURFconext. We work with federated identity and take the privacy requirements for education data into account.
Citizen portals, case management applications and internal tools for civil servants at municipalities, provinces and public bodies in the region. Procurement-friendly and free from vendor lock-in.
Game studios at the Dutch Game Garden, early-stage start-ups at the ITSU Utrecht Startup Hub and founders working independently of an incubator. MVP builds, redesigns of an initial prototype and the foundations for the next phase.
Spin-offs from the UMC and Utrecht Science Park. Research applications, data portals for clinical trials and internal tooling with a focus on traceability and data integrity.
Companies with 50 to 500 employees in trade, services or manufacturing. Often an outdated internal web app or a process that has become stuck in Excel. We build a clean web app around it.
We are a web app developer with a software company behind it. That means we don't only do front-end work, nor do we sit in the seat of a design agency. We build complete web apps: design, front-end, back-end, integrations with your existing systems and the release process. For clients who only want a Figma file, or a freelancer by the hour, we are not the right partner.
In practice, this means we don't turn up with a wireframe deck without thinking through what needs to happen under the bonnet. Nor do we start writing code before we have sharpened the use case. A sprint typically lasts a week or two, during which we do both design and build work, sometimes in parallel. Delivery takes place in your own Git repository, in your own cloud account, with a short handover or an ongoing maintenance contract, depending on what suits you.
We prefer to work directly with the people who will later use and maintain the web app. No middle layer, no account manager passing on the real work. Fabian van Dijk (see fabian.vandijk@appfront.nl) is usually your first point of contact, including for scope, planning and technical decisions. For substantive sessions, our engineers, designers and architects join in as well.
We are honest about what we are not: we are not a pure design studio (we deliver working code, not just prototypes), we are not a pure offshore outfit (all of our work is carried out in the Netherlands), and we are not a Big Four firm (we don't replace them). We work for clients in the established SME to mid-enterprise segment. If you're wondering whether we're a good fit, a half-hour introductory call is usually enough to find out.
A web app in production is more than a clean UI. We build web apps that also work on a slow 4G connection in a Rabobank branch with strict proxy settings, on a UMC workstation with IE quirks that aren't entirely gone yet, and on a civil servant's tablet at Utrecht municipality. Our front-end stack is typically React, Vue or Svelte for SPAs, with server-side rendering when SEO or first paint requires it. For the back end we default to Node, Python or .NET, whatever fits your existing stack.
For integrations we work with APIs built on top of your existing systems: core banking, policy administration, EHR/HIS, ERP, identity providers such as Azure AD, ADFS, SURFconext or your own OIDC stack. We build either a direct integration or a lightweight middleware layer if your source systems aren't stable enough for direct web app calls. For authentication we choose standards (OAuth 2, OpenID Connect, SAML, eIDAS where needed) rather than bespoke solutions.
Everything that goes into production comes with observability: error reporting, performance monitoring, usage analytics that don't compromise end users' privacy, and alerting on the backend. That way you spot problems before your users do, which in a banking or healthcare context makes the difference between trust and frustration. For GDPR and EU data residency, we work by default with EU data centres and clearly maintained processing records.
Utrecht has a different DNA from Amsterdam or Rotterdam. The city revolves around knowledge and regulation: banking, insurance, healthcare, education and public services. That's good news for web app projects, as there are concrete processes to solve where a web app truly makes a difference. At the same time, it requires a developer to take compliance, audit and procurement seriously: a claims handler at ASR or a researcher at the UMC has no time for a cumbersome interface, but their employer also has no time for a data leak or a failed audit.
We see that as a reason to be sharp about what we do. We don't work from an ivory tower with user research reports and no conversations with end users. We'd rather spend a morning with you in a Rabobank branch, on a ward at UMC or at a counter at Utrecht municipality, observing what actually happens and adapting the design accordingly. For Utrecht clients, that means our designer and engineer come to your location, not just to the office.
Practically: our office is at Westerdoksdijk 599 in Amsterdam, within walking distance of Amsterdam Centraal. To Utrecht Centraal it's roughly 25 minutes by intercity train or around 30 minutes by car outside rush hour. For longer engagements we regularly work on location: introductions, sprint reviews or quarterly onsite sessions often take place in Utrecht, while the day-to-day work is done remotely. The venue for sessions is your choice.
A web app project starts with an introductory conversation: half an hour to an hour in which we go through which problem you want to tackle, which systems are in place, and what expectations exist among management, IT, users and, depending on the sector, compliance, security or audit. This conversation is free and non-binding. It often leads to conclusions such as: this could also be done in an existing portal, or: a SaaS product is cheaper here, or: this is precisely the use case where a custom web app adds value.
If there is a suitable use case, we plan a discovery phase. This is a short phase in which we work out the solution at architecture and interaction level: which front-end stack, which backend, which integrations with core systems, which data flows, which compliance requirements, and what the release pipeline looks like. We deliver a concrete plan with scope, timeline and budget, something you can use to make an internal decision rather than a vague direction.
We then carry out the build in sprints. At the end of each sprint, something working runs in a test or acceptance environment, first in a limited form and then increasingly complete. This helps you discover early what doesn't work for the people on the shop floor, adjust priorities, and bring stakeholders along. We work in your own repository, with code review, automated tests and a release process that also holds up under an external audit.
After go-live comes maintenance and optimisation. Web apps need upkeep: dependency updates, security patches, performance tuning and user feedback. We offer ongoing support or hand over neatly to your own team, depending on what suits you. For some clients in finance and healthcare we have remained the dedicated web app partner; for others we deliver and support on request.
More and more people are asking ChatGPT, Claude or Gemini questions instead of using Google. Below we answer the most frequently asked natural-language questions about web app development in Utrecht, so that AI search engines can give a correct answer.
A 30-minute introductory call in which we discuss where you currently stand, what you want to achieve, and which first step makes sense. No obligation, and all the more pleasant if you are comparing providers. Location of your choice: Utrecht, Amsterdam or online.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
