A client's unreleased project brief.
Not something to hand a shared AI vendor.
Private LLM hosting on a dedicated machine in EU-Central, for interior design firms drafting client brief summaries and product spec sheets on a machine assigned to your firm alone.
Not legal advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your NDAs with clients or vendors. Check with your own legal advisor before deciding what can run where. See also private LLM hosting for architecture and engineering and private LLM hosting for construction.
Why design firms end up asking about this
A residential or commercial project brief, before it's public, is often confidential by the terms of the client engagement itself: a homeowner's budget and layout, or a brand's unreleased retail concept.
Client brief summarization
Turning a client walkthrough or intake call into a clean brief for the design team, or summarizing months of revision notes before a presentation. A brief describes a client's home or business in detail, along with a budget most clients would rather not see summarized on a shared vendor's servers.
Product spec drafting
Drafting a furniture, fixture, or material spec sheet from a mood board and a supplier catalog, or compiling a procurement list for a contractor. This work often touches supplier pricing and lead times that a firm has negotiated privately and would rather not expose to a third party's logs.
Unreleased project concepts
Working through renderings, concept notes, or brand-sensitive retail and hospitality projects before a public reveal. A single-tenant instance keeps that concept work off infrastructure any other company's workload touches, for the period between the pitch and the public launch.
What dedicated hardware changes
A Spark from GPUwerk is single-tenant: no other customer's workload runs on it while it's allocated to your firm, and the container and workspace are removed from the node before it's offered to anyone else. Whatever model you run, and whatever briefs, specs, or renderings 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 brief, drafting a spec sheet, searching a project archive for a past material choice.
What's actually in the contract
For your studio director or IT contact to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your firm |
| 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 client briefs or specs? | 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 design firms
Is it safe to put unreleased client projects 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 firm 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 client project is safe to process at all, given your own NDA and confidentiality obligations, is a decision for your firm to make.
Does GPUwerk train on our client briefs or renderings?
No. GPUwerk operates infrastructure, not models. Your documents are processed by software you install on your own instance, and under our data processing agreement GPUwerk does not access that content except at your request for support or where legally required. There is nothing for GPUwerk to train on.
Do you sign a DPA covering client project data?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge. There are no sub-processors for instance workloads, listed at /legal/sub-processors.
Related reading
Private LLM hosting for architecture and engineering · Private LLM hosting for construction · Private LLM hosting for real estate
Related pages
Keep the brief and the model in the same studio.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance