A client's unreleased catalogue isn't public training data.
Run AI on a machine you control.
Private LLM hosting on a dedicated machine in EU-Central, for print, prepress, and publishing companies working on jobs that haven't shipped yet.
No special affiliation claimed. GPUwerk is a product of PRINT IT! SE, a Prague-registered company. That doesn't give this page any particular authority over print industry practice; it's a standard infrastructure offer described on its own terms.
Why a prepress workflow shouldn't run through a public AI tool
Prepress and print production houses sit in the middle of other companies' launch timelines: packaging redesigns before a retail rollout, annual reports before a filing date, book manuscripts before publication. None of that is meant to exist anywhere outside the job file until the client says so.
"It's just proofreading and layout notes"
Running unreleased copy, cover art, or packaging text through a public AI tool to check consistency or catch errors sends that content to a third party's infrastructure, often under terms of service the client's own confidentiality clause never anticipated.
"Our NDA only covers the finished product"
Most client NDAs cover the work in progress too, including drafts, proofs, and revision notes. A dedicated instance keeps that material inside infrastructure your company controls instead of a shared cloud tenancy you don't have visibility into.
"Production staff already paste into public AI tools"
Designers and editors drafting captions or checking copy in a public tool is a real exposure, not a hypothetical one, especially on embargoed releases. A sanctioned alternative on your own instance, same chat interface, keeps that workflow off third-party infrastructure. See the private ChatGPT setup →
What runs well on a Spark node
Copy editing and proofreading assistance, metadata and alt-text generation for large image sets, translation drafts for multi-market packaging, and summarizing revision notes across a job file are typical workloads. A single dedicated node covers most production schedules, including deadline-driven print runs.
| Question | Answer |
|---|---|
| Where is data physically processed? | EU-Central, on a dedicated single-tenant machine assigned to you |
| Who can access instance content? | Through the instance itself, only holders of your SSH keys; password login is disabled fleet-wide. GPUwerk keeps infrastructure administrator access to the 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. |
| Sub-processors for the workload? | None, listed at /legal/sub-processors |
| DPA (GDPR Art. 28)? | Published at /legal/dpa, no charge |
| Certifications held? | None claimed on this page or elsewhere on the site. If a client's contract requires a specific certification, verify directly with us before relying on this page. |
| On-demand rate | $0.79/hour (spark-1x), $1.79/hour (spark-2x). See /pricing for held/reserved rates. |
Questions we get from print and publishing companies
Can we run unreleased client jobs through this?
Yes. The instance is a dedicated single-tenant machine assigned to your company, so proofing, layout notes, or copy work on an unreleased catalogue, packaging design, or embargoed publication stays off shared public infrastructure.
Is GPUwerk affiliated with our print business?
No. GPUwerk is a product of PRINT IT! SE, a Prague-registered Societas Europaea, but we don't offer any special standing or affiliation-based authority to print or prepress companies. This page describes the same infrastructure and contract terms available to any customer.
Does GPUwerk see the designs or manuscripts we process?
No, not as a matter of course. Under the data processing agreement, GPUwerk does not access instance content except at your request for support or where a legal obligation requires it.
Do you sign a DPA and NDA for client print jobs?
A standard GDPR Article 28 DPA is published at /legal/dpa at no charge. A separate mutual NDA can be discussed directly if your client contracts require one; ask when you book a first engagement.
Related pages
See how other creative and production businesses use private LLM hosting: media and publishing, marketing agencies, and translation and localization agencies. Or start from the private LLM hosting overview.
Related pages
Bring your next production run to a machine you control.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance