Who we work with and which tools we use.
An honest overview of our strategic partners, the platforms we build on every day and the criteria we use to choose them. No marketing stickers, no invented partner status — only what we actually use for your custom software.
A partner page, not a logo wall.
Most partner pages are a collection of logos where you can't tell what the actual relationship means. "Cloud Partner" might mean the company earned two certifications last year, or that a sales conversation once took place. With us, you can read which collaborations are strategic, which tools we use every day and which we deliberately do not position as partners.
Our strategic partners — InfoPeople and Data Science Lab — together with us form a data and AI collective of around 75 professionals, which we call the Data Hub internally. Beyond that, we use a broad range of cloud, payment, design and development tools. We do not claim any tier status or badge that we cannot demonstrably hold, because our clients and their due diligence teams rightly check such claims. Below, we do describe which platforms we use every day and why.
This page is intended for clients who want to know, before a project starts, which tooling we would use to build it; for procurement departments running an RFP or supplier acceptance process; and for IT departments who want to start thinking about integrations with their existing landscape. If anything is incorrect or missing, we'd be glad to hear it so this overview stays up to date.
Three types of relationship we distinguish.
Not every collaboration is the same. A strategic partner is fundamentally different from a platform we use every day or a vendor we happen to build an integration with. On this page we distinguish three levels, so you know exactly what kind of relationship it is before you accept dependencies in your project.
Strategic partners
Companies we work with over the long term: we write joint proposals, put teams together and share knowledge. For our clients, this means that through Appfront you get direct access to capacity and specialist expertise beyond our own walls.
InfoPeople, Data Science LabPlatforms and tools we use
The cloud, payment, AI, design and developer platforms we build on every day. We are a customer or user of these platforms, not a reseller. That keeps our choices unbiased and avoids commission-driven advice.
Cloud, CRM, payments, AI, design, dev toolsIntegrations at your request
Specific vendors we integrate with because you already use them. We have no preferred relationship with these parties — we follow your landscape. We make no partner claim here, even though we often have deep technical experience with the system.
ERP, HRM, industry-specific, legacyStrategic partners — the Data Hub.
Together with InfoPeople and Data Science Lab, Appfront forms a data and AI collective that we internally call the Data Hub. Together we are around 75 professionals with complementary specialisms: data engineers and BI specialists via InfoPeople, data strategy and machine learning via Data Science Lab, and application development via Appfront. For clients, this means a single point of contact with access to the full spectrum, without having to juggle three separate suppliers.
Appfront
We design, build and maintain custom software, web applications and mobile apps, often with AI or data components. Within the Data Hub, we are the party that turns data and models into working products: portals, dashboards, automation, integrations. We close the chain between raw data and the user who has to work with it.
- Custom web applications and native apps
- AI-driven dashboards and interfaces
- API integrations and middleware
- Ongoing maintenance and further development
InfoPeople
Specialised in matching data engineers, data scientists and BI specialists with organisations that need capacity. For our clients, this means we can quickly add a data engineer to a team, or provide an interim BI specialist for a specific phase, without needing a separate recruitment process. InfoPeople knows the Dutch data landscape and knows which profiles work in which type of project.
- Data engineers and data scientists
- BI specialists and data analysts
- Secondment, interim and project-based
- Knowledge of the Dutch ecosystem
Data Science Lab
Helps organisations with data strategy, machine learning and translating raw data into usable insights. For clients who don't yet have a clear data roadmap — or an existing AI initiative that is running into constraints — Data Science Lab is the party we involve for strategy and model development. We then make sure those models actually reach production through the applications we build.
- Data strategy and roadmaps
- Machine learning and predictive analytics
- Data maturity assessments
- Data-to-action translation
Platforms and tools we use.
Below are the platforms we build on every day. We are a customer or user of these services — not a reseller, not an affiliate. That keeps our advice neutral: we choose what suits your project, not what earns us a commission. For cloud questions, we also have dedicated pages on AWS consulting, Azure consulting and Google Cloud consulting, where we go into more depth on when each platform is the right choice.
Cloud infrastructure
IaaS · PaaSWe host and run applications on the three major hyperscalers and, where it fits, on smaller European providers. For projects with strict EU residency requirements, we deliberately choose European regions or local alternatives. We don't claim any specific partner tier; however, for each platform we have a consulting page explaining when we recommend which option.
Hosting, CDN and edge
Edge platforms · CDN · WAFFor frontends, edge functions and global delivery, we use Cloudflare and Vercel. We also use Cloudflare for DDoS protection, web application firewall and DNS management; Vercel for projects where Next.js or similar frameworks deliver the most value. For traditional web hosting of content sites, we often work with TransIP or Hetzner, depending on what your IT department already has in place.
Payments
PSP · iDEAL · SEPAFor Dutch clients with iDEAL and SEPA as their main payment methods, Mollie is usually the logical choice, as its Dutch documentation and level of support are high. For clients with international or enterprise requirements — fraud models, tokenisation, recurring direct debits at scale — we generally recommend Adyen or Stripe. We always make a payment choice in consultation with your finance team and based on your volume and risk profile.
CRM and marketing stack
Sales and marketing platformsWe integrate with almost every CRM that is common in the Netherlands. We often see HubSpot at fast-growing B2B companies because it keeps sales and marketing functionality close together. Salesforce comes up once organisations need enterprise reporting, complex role structures or have an existing Salesforce investment. For email and automation, Mailchimp, Brevo and ActiveCampaign come into play. We have no partner status here; we are an integrator.
AI and LLM platforms
Model APIs · ML infrastructureFor AI functionality, we use models from Anthropic, OpenAI and Mistral via their official APIs. Which one we choose depends on the use case and data residency: for projects where European processing is essential, we more often choose Mistral or self-hosted variants. For production, we put guardrails, observability and cost monitoring on top of these APIs. We are a customer of these platforms; we have no reseller deal steering us towards a specific model.
Design and research tools
UI/UX · Prototyping · ResearchOur designers work in Figma for interface design, design systems and prototypes. For user research, we use Maze, Lookback or Lyssna, depending on whether the focus is on moderated interviews or asynchronous testing. For analytics and behaviour tracking after launch, we consider Plausible, Matomo or Google Analytics, and for clients who are conscious of the GDPR we generally recommend a privacy-friendly option.
Development and delivery
Versioning · CI/CD · ObservabilityWe manage our source code in Git, hosted on GitHub or GitLab depending on the client's preference. For builds, tests and deployments, we use GitHub Actions, GitLab CI or platform-native pipelines. We catch errors and performance issues with Sentry, and we monitor application performance with Datadog, New Relic or the native cloud tools. The source code and CI/CD environment are always registered in the client's name, never in Appfront's.
Identity, security and compliance
SSO · IdP · AuditFor authentication and single sign-on, we integrate with your existing identity provider, often Azure AD or Google Workspace. For consumer-facing apps, we use Auth0, Clerk or Cognito, with iDIN or DigiD if your audience requires it. For the security layer, we deploy Cloudflare WAF, rate limiting and bot management. We carry out compliance checks in-house based on our information security policy, with penetration tests by an external specialist party in the final phase of a project.
How we select partners and tools.
We make deliberate choices, not ad hoc ones and not based on marketing promises alone. Our clients often have to deal with procurement, compliance or security questionnaires, and we want to be able to justify every tool we propose. Below are the criteria we apply.
GDPR compliance and EU residency
We prefer suppliers that offer EU data residency or can run in a European region for your use case. For data containing the personal data of EU citizens, we are not satisfied with a mere mention of Standard Contractual Clauses without further measures.
Code ownership and freedom to exit
A platform or supplier must not be the only place where your business logic lives. We choose tools from which you can export your data at any time and whose configuration we can reconstruct if we ever had to switch.
No vendor lock-in at the data layer
At the data layer, we work with open standards wherever possible: PostgreSQL or similar as the primary database, S3-compatible storage for objects, and JSON or Parquet as exchange formats. That way, migrating between cloud providers remains a planned project, not a disaster.
Proven documentation and support channel
We would rather choose a well-documented, slightly less well-known supplier than a much-discussed platform with chaotic API documentation. For clients, this means a lower maintenance burden and less dependence on consultancy.
Transparent pricing model
We avoid suppliers with unpredictable cost models or heavy "talk to sales" elements without a public price list, unless the use case makes that unavoidable. For your operations, predictable OPEX is crucial.
Compatibility with your landscape
A partner or tool must fit in with what you already have. We don't try to rebuild your stack to suit our preferences; we start from where you are. You can read how this works in practice on our page about our process.
Vendor-independent, with no hidden agenda.
A question clients regularly ask us during introductory meetings: "Will we get commission-driven advice?" The short answer is no. We deliberately have no reseller or affiliate relationships with the platforms above. We are a Mollie customer just as you would be, an AWS customer like any startup, a Figma customer like any other studio. As a result, our advice is driven by substance rather than commerce.
This has a practical consequence: if we point you towards a specific platform, it's because it suits your situation, not because we'd get a discount on it. Conversely, if you already use a platform we have less experience with, we'll say so. We don't claim expertise we don't have, and we don't hold partner status that isn't real. For due-diligence and RFP processes, that gives you sharper, verifiable answers than a wall of logos where every badge carries a different weight.
Finally, on every project we hand over the source code, configuration and accounts in your organisation's name. You are free at any time to continue with someone else or to bring maintenance in-house. For us, no lock-in is not a marketing claim but a design choice in how we set up projects.
Frequently asked questions.
Procurement, IT and compliance teams usually ask the same questions before we start. Below are the answers we give most often.
Is Appfront an official cloud partner of AWS, Azure or Google Cloud?
Which permanent partners does Appfront work with strategically?
Will we be locked in to the tools Appfront chooses?
Can I bring my own preferred suppliers?
How do you handle data residency and sub-processors?
Do you also work with other agencies or freelancers?
What if one of your partners or tools disappears?
How does all of this fit into your process?
Question about a specific partner or tool?
Talk to us about which partnership and which stack would suit your project. An introductory meeting is non-binding and takes half an hour. We listen to your situation, think along about alternatives, and give honest advice based on what your question really needs.