Field data from the wellhead to the terminal.
Keep it on hardware only you can reach.
Private LLM hosting on a dedicated machine in EU-Central, for upstream, midstream, and downstream teams drafting drilling reports, safety incident documentation, or field data summaries without routing operational detail through a shared AI vendor.
Not legal or HSE advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your regulatory or safety obligations. Check with your own legal and HSE compliance team before deciding what can run where. This page covers upstream, midstream, and downstream document work; for grid and utility-side operations see private LLM hosting for energy and private LLM hosting for utilities and water.
What this page is and isn't about
This is about text and document AI across the value chain, drilling and completion reports, safety incident writeups, and field data logs, not operational technology security. We don't operate in SCADA environments and have no claim to expertise in industrial control system security. If your question is about protecting live control systems on a rig or a pipeline, that's a conversation for an OT security specialist.
Upstream: drilling report summarization
Turning a daily drilling report or mud log into a clean summary for the next shift, or pulling a pattern out of months of well data. These reports carry well locations, formation data, and operational detail that a competitor or a shared vendor's logs have no business seeing.
Safety incident documentation
Drafting the narrative section of an incident report, near-miss log, or permit-to-work record from field notes. Safety filings are often legally required to be accurate and complete, and regulators expect an operator to account for where drafts and working data were sent while preparing them. See the private AI incident postmortems guide →
Midstream and downstream: field data summarization
Summarizing pipeline inspection logs, terminal throughput records, or refinery maintenance data for a shift handover or a regulatory filing. This data describes physical infrastructure in enough detail that most operators keep it off shared cloud AI products as a matter of course.
What dedicated hardware changes
A Spark from GPUwerk is single-tenant: no other customer's workload runs on it while it's allocated to you, and the container and workspace are removed from the node before it's offered to anyone else. Whatever model you choose to run, and whatever reports or field data you feed it, stays on that instance; we don't access, read, or analyse the content. 128 GB of unified memory covers the bulk of this work, summarizing a report, drafting an incident narrative, searching a document archive for a prior occurrence; a linked 256 GB cluster adds headroom for a large historical document set without changing where the data lives.
What's actually in the contract
For your HSE lead or IT lead to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your operation |
| 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 field or safety 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. |
| Pricing | Spark-1x from $0.79/hour on demand, billed per minute; Spark-2x from $1.79/hour. A customer-requested stop holds the reservation at 75% of the running rate. See /pricing for full detail. |
Questions we get from oil and gas operators
Is it safe to put drilling and field reports into an LLM?
That depends on where the model runs and who can reach it, not the model itself. On a GPUwerk dedicated instance in EU-Central, the machine is assigned to your operation alone and reachable only through your SSH keys; GPUwerk does not access, read, copy, index or analyse what runs on it except at your request for support or where a legal obligation requires it. Whether a specific report is safe to process at all, given your own confidentiality and regulatory obligations, is a decision for your own legal or HSE compliance team.
Do you support operational technology or SCADA environments?
No. GPUwerk hosts document and text AI workloads, drafting and summarizing reports, not control systems. We have no claim to expertise in industrial control system security and do not operate in SCADA environments.
Do you sign a DPA covering field and safety data?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge, and there are no sub-processors for instance workloads.
Does GPUwerk train on our drilling or field data?
No. GPUwerk runs infrastructure, not models. There is nothing for GPUwerk to train on, since we do not access instance content except as described in the DPA.
Related reading
Private LLM hosting for energy and utilities · Private LLM hosting for mining · Private AI for incident postmortems
Related pages
Keep field data and safety records off someone else's servers.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance