Member messages and booking logs.
Not something to type into a shared chatbot.
Private LLM hosting on a dedicated machine in EU-Central, for co-working operators drafting member communication or summarizing booking and usage reports on a machine assigned to your space alone.
Not legal or compliance advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your obligations as a co-working operator, and it is not a claim of any specific certification on GPUwerk's behalf. Check with your own advisor before deciding what can run where. See also private LLM hosting for hospitality for the adjacent guest-facing setting, and private LLM hosting for event management for space and booking coordination.
Where an LLM fits into a co-working operation
This is about the member-facing and reporting side of running a space, not access control or the booking system itself.
Member communication drafting
Drafting welcome emails, renewal reminders, or replies to member questions about invoicing and desk allocation from the account history already on file. That history ties a member's name to their company, plan, and billing detail, exactly the kind of record most operators would rather not send to a shared vendor's servers.
Booking and usage report summarization
Turning a month of meeting room bookings, desk occupancy, and day-pass usage into a plain-language summary for an operator deciding whether to add capacity or adjust plan pricing, without someone manually skimming a spreadsheet every week. See the private AI internal comms guide →
Community update drafting
Writing the weekly community newsletter, event announcements, or house-rule reminders in the space's own voice, pulled from the calendar and member list without a community manager retyping the same update by hand each week.
On certifications and compliance frameworks
GPUwerk has not published ISO 27001, SOC 2, or any other formal certification, and this page makes no claim that hosting on GPUwerk satisfies any specific data protection regulation on its own. What GPUwerk provides is a dedicated single-tenant machine, a published GDPR Article 28 DPA with no sub-processors for instance workloads, and a documented answer to who can reach the machine and what happens to data on termination. If your compliance program requires a specific framework, that gives your own advisor a concrete starting point to assess against your requirements, not a substitute for the assessment itself.
What's actually in the contract
For your operations lead or IT contact to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your space |
| 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 see member 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 |
| Certifications? | None published (no ISO 27001 or SOC 2 claimed). Assess against your own compliance requirements. |
| 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 co-working operators
Is it safe to put member data 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 space 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 use of member data meets your own regulatory obligations is for your own advisor to confirm.
Is GPUwerk certified for handling member data?
GPUwerk has not published ISO 27001, SOC 2, or similar certifications. If your compliance program requires a certified provider or a specific control framework, a dedicated single-tenant instance with a published DPA and no sub-processors gives you a documented starting point to assess against your own requirements, not a substitute for that assessment.
Do you sign a DPA covering member 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 member records?
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 hospitality · Private LLM hosting for event management · Private AI for internal comms
Related pages
Keep member 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