Unpublished research shouldn't train someone else's model.
Run it on your machine.
Private LLM hosting on a dedicated machine in EU-Central, for universities and research institutions handling student records, pre-publication data, or grant-funded work with data residency terms that rule out a shared third-party cloud.
Not legal advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your obligations under a specific grant agreement, national student-records law, or your institution's own research data policy. Check with your research office, general counsel, or data protection officer before deciding what can run where.
Where a shared cloud API stops being the right answer
A university runs several kinds of sensitive data at once: student enrollment and grade records, unpublished manuscripts and datasets ahead of peer review, and grant-funded projects that come with their own residency clauses. A single institution-wide policy rarely fits all three.
"Our grant says data can't leave the EU, or can't touch a US cloud"
The hardware is physically in EU-Central and operated by PRINT IT! SE, a Societas Europaea registered in Prague. No US parent, no US region, no US-incorporated entity in the chain. That's a fact about where the machine sits, which grant administrators can check directly against the grant's own wording.
"A postdoc's dataset shouldn't sit on a shared API before publication"
On a GPUwerk instance, the model runs on hardware assigned to your lab or department alone. GPUwerk operates the machine but, under the data processing agreement, does not access your content except at your request for support or where a legal obligation requires it. Pre-publication results stay where you put them.
"Students and staff already use consumer AI tools with sensitive material"
Advisors summarizing student work, registrars drafting correspondence, or grad students pasting draft chapters into a public AI tool is common and usually informal. A sanctioned alternative on your own instance, same chat interface, keeps that workflow on institution-controlled hardware. See the private ChatGPT setup →
What's actually in the contract
For your data protection officer, research office, or IT lead to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your institution or research group |
| Who operates it? | PRINT IT! SE, a Societas Europaea registered in Prague, Czech Republic. No US parent entity. |
| Who can reach the instance? | Through the instance itself, only holders of your SSH keys; password login is disabled fleet-wide. GPUwerk keeps infrastructure administrator access to the underlying machine, as on any hosted service, and under the DPA does not use it on your content except at your request for support or where a legal obligation requires it. |
| Does GPUwerk read research or student data? | No. We host the hardware and, under the DPA, do not access, read, copy, index or analyse workload content. |
| Sub-processors for the workload? | None, listed at /legal/sub-processors |
| DPA (GDPR Art. 28)? | Published at /legal/dpa, no charge |
| Data on termination? | Container and workspace volume deleted from the node, then the node is sanitised before reassignment. Filesystem deletion, not a cryptographic erase; export what you need before terminating, since it isn't reversible. |
Questions we get from universities and research teams
Can we use this for student data under our national student-records law?
GPUwerk can tell you where the hardware sits and who can reach it: EU-Central, a dedicated single-tenant machine, no US entity in the chain, and an Article 28 DPA. Most EU member states have their own student-records rules layered on top of GDPR; whether a given workflow satisfies those is for your institution's data protection officer to assess, not something an infrastructure vendor can certify.
Our grant terms say data can't touch a US cloud provider. Does GPUwerk qualify?
The hardware is physically in EU-Central and operated by PRINT IT! SE, a Societas Europaea registered in Prague, with no US parent or US-incorporated entity in the chain. That is a factual answer to where the machine sits; whether it satisfies a specific grant's data terms is for your research office or grants administrator to confirm against the grant's actual wording.
Does GPUwerk train on our research data?
No. GPUwerk runs infrastructure, not models. Unpublished research and datasets processed on your instance are handled by software you install, behind SSH keys only you hold. Under the data processing agreement, GPUwerk does not access that content except at your request for support or where a legal obligation requires it.
Do you sign a DPA for institutional use?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge, and there are no sub-processors for instance workloads.
Related pages
Give your department a machine it actually controls.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance