REGION · LEIDEN
Website design in Leiden.
Leiden is about half an hour by train from our Rotterdam studio. University spin-offs, life sciences and health-tech clients. Short lines and regular on-site time.
Leiden is about half an hour by train from our Rotterdam studio. University spin-offs, life sciences and health-tech clients. Short lines and regular on-site time.
NedDev builds websites, SaaS platforms and AI systems for companies in Leiden, from our studio in Rotterdam. Leiden is about half an hour from our Rotterdam base by train, so we are on site quickly. With the Leiden Bio Science Park and Leiden University, the city has a strong life sciences and healthtech sector, plus many knowledge-intensive spin-offs. For those clients we build platforms that handle data carefully. Short lines, regular face-to-face. Projects start with a fixed price after intake.
Web development in Leiden means building websites, platforms and software for a city that runs on knowledge, life sciences and healthcare technology. The Leiden Bio Science Park is one of the largest life sciences clusters in Europe, and Leiden University produces a steady stream of spin-offs. Those organizations often work with sensitive research and patient data, which sets requirements for the software around it.
NedDev works as a Rotterdam studio for clients in Leiden, and Leiden is a nearby city for us, roughly half an hour by train from Rotterdam. That makes it easy to be on site quickly for a conversation around the table, a design session or a go-live.
For organizations in Leiden we typically build:
Leiden is a knowledge city with a pronounced profile. The Bio Science Park attracts life sciences companies, biotech and healthtech, and Leiden University feeds that with research and spin-offs. Anyone building software here is almost always building for an environment where data is sensitive and care is non-negotiable. That fits our way of working: in production we always have logging, error handling and clear agreements about access.
For life sciences and healthtech clients we build platforms on our built for multiple clients SaaS architecture, so data from different projects or clients stays strictly separated. If an AI component is added, such as making research documents searchable, we build that through AI development with source attribution, so every answer can be traced back to its source.
How do you handle sensitive research or patient data? We build privacy and separated access in from the first line of code, with full logging so it is traceable who saw what. For sensitive data we advise, where needed, on storage and models that stay within the EU.
The City of Leiden positions itself emphatically as a city of knowledge, see leiden.nl. How we handle sensitive case files and strict permissions is shown by ClaimHandler, where every action is traceable and users only see what they are allowed to see.
Leiden is about half an hour by train from our Rotterdam studio, close enough for easy on-site contact. That travel time means working on location is not the exception but the norm when it helps. We can easily sit at the table for a kick-off, a design session or a go-live, and we can also drop by in between if a topic calls for it. That proximity makes the collaboration personal and nimble.
We build our websites and interfaces on Next.js, for fast and easily findable pages that also run smoothly on mobile. The backend runs on Laravel. That fixed stack keeps maintenance and further development manageable, even years after delivery, which matters for long-running research projects.
This is how we approach a Leiden project:
Around the Bio Science Park new spin-offs keep emerging that register their first company at the Chamber of Commerce. For such young companies a well-defined first platform is the smartest start, and the short distance makes intensive guidance easy.
Our own base for multi-tenant SaaS: a Laravel + Filament starter, audit trail and tenant management. We build client platforms on it.
Used internally EDITORIAL · LONG-FORM ↗What we write down as we learn it. Case studies, technical write-ups, design decisions. No content marketing, just real knowledge.
42 articles RESEARCH · AI EXPERIMENTS ↗Side projects and R&D. Voice-agent prototypes, RAG pipelines, AI knowledge-graph experiments. Some become products. The rest teach us something.
455 examples in the LabYes, that fits well with how we work. The Leiden Bio Science Park is one of the largest life sciences clusters in Europe, and the organizations there almost always work with sensitive research or patient data. We build software where privacy, logging and separated access are sorted from the first line of code, with built for multiple clients architecture so data from different projects or clients never gets mixed up. For sensitive data we advise, where needed, on storage and AI models that stay within the EU. For a platform like ClaimHandler we built full traceability and strict user permissions, so we know those kinds of requirements. You do not have to explain to us why an audit trail or fine-grained access rights are needed.
Yes, Leiden is under half an hour by car from our studio in Rotterdam, so on-site work is more the norm than the exception here. We can easily sit at the table for the kick-off, a design session or the go-live, and we can drop by in between when a topic calls for it. That proximity makes the collaboration personal and nimble, which is especially nice for long-running research or care projects where a lot is coordinated along the way. At the same time we handle the ongoing part digitally, with a fixed weekly demo, so we waste no time on trips that could just as well have been a video call. The short distance gives you the best of both.
Projects at NedDev start with a fixed price after intake. A well-findable website often falls in that starting segment. A SaaS platform or an AI application costs more, because that involves user management, connections and ongoing maintenance. For life sciences and healthtech clients there is the added requirement that data processing is demonstrably handled carefully, which calls for extra attention in the build. We would rather give you an honest range after a short conversation than a number that looks too good up front. Alongside the build there are ongoing costs for hosting and maintenance, and with an AI component also for the usage of the model itself. We make those monthly costs clear in advance, so there are no surprises afterwards.
