Custom software for life sciences and clinical research

What's different about software in this field

• Every change has to be traceable

  Each change needs an author, a time and the value before and after. We write that history in the same database transaction as the change, so it can't be skipped, and business records are deactivated rather than deleted.

• Access depends on the study and the site

  Internal staff, study coordinators, clinical sites and partners each see a different slice of the data. Roles are scoped to a study or a site, checked on the server in one place, and every rule has a unit test.

• The software follows physical objects

  Samples move between sites, couriers and labs. The system has to model custody: who holds what, who confirmed it, and what happens when something changes after a confirmation.

• Personal data stays where it is needed

  Notifications and documents carry sample codes and study identifiers, not patient data. Data minimisation is a design decision made early, not a filter added later.

• Your quality team will validate it

  Architecture documentation, recorded design decisions and automated tests give a validation effort something concrete to work from, instead of a codebase to reverse-engineer.

What we build

• Sample and shipment tracking

  Registration by form, spreadsheet import or API; status history; shipment manifests; confirmation by the sending site.

• Study, site and partner portals

  Invitation-only access, roles scoped by study and site, and notifications for each step that matters to each party.

• Internal lab and operations tools

  Spreadsheet and inbox workflows replaced with structured data, explicit states and a record of who did what.

• Integrations and APIs

  Authenticated APIs for internal systems, instruments and LIMS, enforcing exactly the same rules as the user interface.

• Audit trails and documents

  A searchable audit trail, versioned PDF documents generated from frozen data snapshots, and exports your team can rely on.

Recent work

From the blog

• 
  Technical deep diveOct 28, 2026

  Building Clinical Sample Tracking Software: Chain of Custody, Audit Trails and Two-Party Shipments

• 
  Technical deep diveOct 28, 2026

  The Transactional Outbox in Practice: Reliable Emails and Side Effects from Next.js and PostgreSQL

Frequently asked questions

Is your software 21 CFR Part 11 or GxP compliant?

Compliance belongs to a system as it is used and validated within your quality system, so no software vendor can certify it alone. We build the technical controls those frameworks expect, such as secure, time-stamped audit trails, individual user accounts, role-based access and no silent deletion, and we document the system so your team can validate it.

Do you replace a LIMS?

Usually not. A LIMS runs the lab. We build what sits around it or where it doesn't fit: site portals, sample logistics, study-specific workflows and the integrations between them. If an off-the-shelf product covers your need, we will tell you.

Can the data stay in the EU?

Yes. Hosting runs in your own accounts and EU hosting is available. When we process personal data on your behalf, we sign a GDPR data processing agreement (Article 28).

Who owns the code and the documentation?

You do, from day one. Repositories and hosting live in your accounts, and we hand over documentation your own developers can work from, as we did on our clinical sample tracking project.

Do you work with clinical sites outside France?

Yes. The studio is based in Besançon and works in English and French. The software itself is built for users in any country, with dates and times stored in UTC.

Services involved