A platform's worth of engineering data.
Don't hand it to someone else's model.
Private LLM hosting on a dedicated machine in EU-Central, for automotive OEMs and suppliers working with engineering documentation, supplier contracts, or R&D data that shouldn't sit on shared AI infrastructure.
Not a certification of compliance with any OEM information-security standard (TISAX, ISO/SAE 21434, or similar), and not legal advice. GPUwerk has not pursued sector-specific certification of this platform, and this page is not evidence of it. It describes GPUwerk's infrastructure and contractual commitments only. Whether a given use of engineering or supplier data is permitted under your platform-sharing agreements, NDAs, and applicable regulation is a determination for your own security, procurement, and legal teams.
Two kinds of exposure, one shared answer
Engineering documentation carries development-program IP that took years and a supply chain to produce; supplier contracts carry commercial terms that competitors and Tier 1s alike would like to see. Both raise the same infrastructure question before anything else: where does the model actually run.
"A design review deck describes an unreleased platform"
Component specs, tolerance stack-ups, and test protocols for a program that hasn't launched are exactly the kind of document a competitor's engineering team would pay to see early. On a GPUwerk instance, the machine is assigned to your organisation alone, in EU-Central. 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.
"Supplier contracts carry pricing and volume terms across the whole chain"
A Tier 1 or Tier 2 reviewing pricing, tooling amortisation, or capacity commitments across dozens of contracts has every reason to want an LLM's help summarising them, and every reason not to want that data touching a shared vendor's training pipeline. A dedicated single-tenant machine means no other tenant's workload, and no vendor model training, is anywhere near that dataset.
"Engineers already paste error codes and drawing excerpts into consumer AI tools"
Debugging a CAN bus fault or asking for a second opinion on a tolerance calculation in a public AI tool is common, and rarely reviewed for what program-specific detail rode along with it. A sanctioned alternative on your own instance, same chat interface, keeps that workflow off third-party infrastructure. See the private ChatGPT setup →
What's actually in the contract
For your IT security, procurement, or program lead to review directly. This is a description of infrastructure, not a certification record.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your organisation |
| 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. |
| Is the platform TISAX or ISO/SAE 21434 certified? | No, and we don't claim it is. Any certification of this infrastructure as part of a TISAX-assessed or 21434-compliant environment would be your organisation's own scope of work, using documentation we can provide on request. |
| Does GPUwerk read engineering or contract 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 automotive engineering teams
Can we run engineering drawings and CAD-adjacent documentation through an LLM here?
On a dedicated GPUwerk instance, yes, in the sense that the machine is assigned to your organisation alone, in EU-Central, and GPUwerk does not access, read, copy, index or analyse workload content except at your request for support or where a legal obligation requires it. Whether a given document is cleared to leave your own DMS or PLM environment at all is a separate question for your engineering and IT security teams.
Does GPUwerk train on our supplier contracts or design data?
No. GPUwerk operates infrastructure, not models. Whatever you run on your instance is your software and your data, and under our data processing agreement GPUwerk does not access that content except at your request for support or where legally required.
Is this suitable for data covered by a supplier NDA or a platform-sharing agreement?
We can describe the infrastructure: dedicated single-tenant machine, EU-Central, an Article 28 DPA, no sub-processors on the workload. Whether that satisfies a specific NDA's data-handling clause or an OEM's supplier information-security requirements is a determination for your legal and procurement teams, not something GPUwerk can certify.
Do you sign a DPA?
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
Put the program data on hardware your own team 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