Quantum Howl

We start with a pilot, on your server

One closed format to test one of our lines with your data and on your infrastructure. If it works, we continue it as an R&D project.

DiagramYour data, your server: our stack is installed inside and the pilot runs there.

Before the pilot: feasibility study

Every pilot starts with a feasibility study, free and short. We review four things with you: what data you have and what state it is in, what infrastructure exists or would be needed, which specific case you want to solve and which metric will tell you whether it worked. You get a feasibility report with what we found and a clear recommendation: a pilot, another solution or nothing at all.

We review four things with you

  • 1/4

    What data you have and what state it is in

  • 2/4

    What infrastructure there is or would be needed

  • 3/4

    What specific case you want to solve

  • 4/4

    What metric will tell you whether it worked

You getA feasibility report with a clear recommendation

The on-premise pilot

  • Fixed scope, duration and price

    We set them with you when the feasibility study ends, before we start. The price depends on the case, so we quote it on request.

  • An agreed metric

    Before we start, we agree which number the pilot has to move to count as a success.

  • Your data, your server

    We work with your data and on your infrastructure, with our own stack.

The on-premise pilot

What you get

  1. Feasibility report

    Feasibility report

    The starting point, and whether the pilot is worth doing.

  2. A system running on your server

    A system running on your server

    With the documentation to operate it.

  3. Results report

    Results report

    The agreed metric, measured, with what worked and what did not.

  4. Technical documentation of the system

    Technical documentation of the system

    What it does, which data it was trained or configured with, how it is evaluated and which risks have been identified. It is the basis for your legal adviser to assess your obligations under the EU AI Act.

  5. Continuity decision

    Continuity decision

    Continue, adjust or stop, in writing.

Which pilots we take on and when we will say no

We accept

  1. Only from our three lines (on-premise AI, data and agents), built on our stack and leaving something reusable.

  2. We open at least two pilots per quarter; how many more depends on the size of each one.

  3. No pilot with a clinical purpose until we have the CE marking.

We will say no:

  • If your problem can be solved without AI or with a tool that already exists.

  • If there is not enough data, or it cannot legally be used for what you want.

  • If we cannot agree on a metric before we start.

We would rather say no at the start than deliver a pilot that is of no use to you.

After the pilot

If the pilot works and you want to go further, we continue it as a phased R&D project and, if it fits a funding call, we look for funding for it. We never start there.

What we work with

Only what we have tested and written about in the Sprint DGX series.

Tap a layer

NVIDIA DGX Spark

Hardware

Why the model lives in the clinic, not in the cloud.

NVIDIA DGX Spark
Read the chapter

Frequently asked questions

01Do I need to buy hardware?

It depends on the case. In the feasibility study we look at what you have and, before we start, tell you what would be needed and what it would cost.

02Does my data leave my organization during the pilot?

We work on your infrastructure. If any phase needed data to leave it, for example to train on external GPUs, we would propose it beforehand and in writing, with the data pseudonymised, as we describe in chapter 3 of the Sprint DGX series. Read the chapter

03What if the pilot does not work?

You will know from the metric we agreed at the start, and you will see it in writing in the results report. Stopping is also a result.

04How much does it cost?

The feasibility study is free. The pilot depends on the scope, the data and the infrastructure: we give you a fixed price when the study ends, before we start.

05What do I keep when the pilot ends?

The system stays running on your server and you can keep using it with our maintenance. The code remains ours.

06Who does the work?

We do, with no subcontracting: the team that listens to you is the team that builds.

Tell us about your case

What happens next

  1. 1

    We'll reply within 24-48 hours.

  2. 2

    A feasibility study, free and short.

  3. 3

    A feasibility report with a clear recommendation: pilot, another solution or do nothing.

Collaboration type
Technical areas

By submitting this form you accept the processing of your data in accordance with our privacy policy.

For consultancies and integrators

If you work with clients in regulated sectors, such as healthcare, who cannot move their data to the cloud, we can take care of the on-premise part: the model, the deployment on their infrastructure and the evaluation. You keep the client relationship; we handle the technical side.

Write to us using the form