Hosting for JupyterHub in Germany
WZ-IT designs and operates JupyterHub as a shared notebook platform with authentication, isolated environments, resource controls and reproducible images.
About the technology
Design notebook access and compute environments together
JupyterHub manages users and starts their notebook servers through a selected spawner. Security and scaling depend heavily on isolation, images, storage and compute.
We assess user groups, libraries, data, CPU or GPU requirements and the target environment and develop a suitable architecture.
JupyterHub as a shared data-science platform
Run code
Provide Jupyter notebooks and supported development environments per user.Enable team collaboration
Provide shared images, projects and data areas with clear access boundaries.Connect identities
Integrate authentication through suitable authenticators and existing identity providers.Reproduce environments
Provide libraries and runtimes through versioned images or defined packages.Limit resources
Allocate CPU, memory, GPU and storage according to user group and workload.Observe usage
Technically monitor platform state, utilisation, errors and capacity limits.Migration and takeover
Assess existing data and configuration, migrate them in a test run and move to managed operations through a controlled cutover.Identity and secure access
Secure SSO, roles, administrative paths and external access for the application and existing infrastructure.Backup and recovery
Back up all stateful components consistently and document the recovery path for the agreed scope.Updates, monitoring and operations
Monitor and update the application and its technical dependencies and operate them under the agreed service level.
Operations beyond installation
Operate JupyterHub as a secure multi-user compute platform
Each user can execute code, so images, spawners, storage, resource limits and data access define security and scale.
Hub and user environments
Operate JupyterHub, proxy and spawner reproducibly.Compute and images
Define CPU, RAM, GPU, libraries and limits.Persistent workspaces
Protect home, project and shared data.Isolation and operations
Control identity, network, monitoring and backups.
Area
Responsibility for platform, code and data
WZ-IT operates the platform and isolation; user code, packages and business results remain customer-owned.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| JupyterHub platform | WZ-IT | Hub, proxy, spawner, base images, monitoring and updates. |
| Compute and limits | WZ-IT | Technical CPU, RAM, GPU and storage quotas. |
| Images and libraries | Shared | We build reproducibly; teams define required packages. |
| Data access | Shared | We connect storage while the customer approves datasets. |
| Notebook code | Customer | Code, processing and validation remain with user teams. |
| Pipelines and GPU workflows | Optional WZ-IT service | Automation and special images are scoped separately. |
Hosting & operations
How much does JupyterHub hosting cost?
We combine the right compute size with ongoing operations, backups, monitoring and a service level appropriate for the criticality of JupyterHub. High availability and recovery targets are designed separately where needed.
Hosting for JupyterHub in Germany: GDPR-compliant operations
- One managed standard application included
- .de domain included or your own domain or subdomain via CNAME
- German data centres with ISO 27001 and BSI C5, no US clouds
- 99.9 % standard availability per month
- Regular updates, CVE monitoring and prioritised patches for critical vulnerabilities
- Central logs with immutable retention
- Daily backup with 7-day retention
- 5 TB outbound traffic per workload and month
- 24/7 proactive monitoring
- Five service levels, 24/7 P1 response with Production or Critical
- Personal technical contact
Instance sizes and monthly prices
- XS · 2 vCPU, 2 GB RAM, 40 GB NVMe SSD
- €99.90 in total
- S · 2 vCPU, 4 GB RAM, 80 GB NVMe SSD
- €129.90 in total
- M · 4 vCPU, 8 GB RAM, 80 GB NVMe SSD
- €159.80 in total
- L · 8 vCPU, 16 GB RAM, 80 GB NVMe SSD
- €219.80 in total
- XL · 16 vCPU, 32 GB RAM, 80 GB NVMe SSD
- €329.80 in total
- Additional storage per 50 GB
- +€4.99
Straightforward provisioning within a few business days
- Bank transfer
All prices are net and exclude statutory VAT. The offers are addressed to businesses. All on-premises options
Other options
Try it free for 7 daysRequest a test instance
We set up a test instance for you, usually on the next business day. No payment details required. After seven days it is deleted unless you continue.
Request a test instance →Bring Your Own InfrastructureInstallation on Your Infrastructure
Installation on your own infrastructure · On-premise or in your cloud · Control over data location and access · Custom configuration · Complete documentation · Initial setup & configuration · Optional support and maintenance contract
Request a proposal →On-premises optionRun JupyterHub on hardware at your organisation
As an alternative to managed hosting in the data centre, WZ-IT provides the hardware, configures JupyterHub, and handles hardening, monitoring, updates, backup and technical support. Access can be limited to the internal network or enabled through VPN and existing identities.
View WZ-IT App Node →Sizing and deployment
Size JupyterHub by active users and compute profiles
Concurrent servers, libraries, datasets, notebook load and GPUs determine the platform.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| Small analysis or teaching team | Spawner and image assessment | Profiles, limits and storage are defined. |
| Many concurrent servers | Cluster architecture | Scheduling, isolation and storage are sized. |
| GPU notebooks | GPU pool assessment | Drivers, images and quotas are planned. |
| Research or production data | Security and recovery design | Access, audit and recovery are agreed. |
- User profiles, isolation, images, storage and CPU/GPU demand are reviewed before a proposal.
Sizing and deployment
JupyterHub deployment models
Compute and storage are placed close to data with suitable isolation.
Dedicated WZ-IT platform
European CPU or GPU environment after assessment.Your cloud
Integration with existing Kubernetes and storage.On-premises
Local operation near sensitive data or GPUs.Hybrid
Central identity with separate compute or data.
Target architecture
Isolate user code and make environments reproducible
Identity, spawner, images, compute and data access receive explicit boundaries.
Researchers, developers and analysts
Browser-based notebook environments.
TLS and central access
SSO, groups, quotas and restricted administration.
Users and compute profiles
Roles, images, limits and data areas.
JupyterHub
Hub, proxy, spawner and user servers.
Compute and scheduler
Containers, VMs or Kubernetes with CPU and GPU.
Persistent storage
Homes, projects, datasets and backups.
Versioned images
Python, R, Julia and agreed libraries.
Arbitrary code execution requires stronger isolation than a standard web application.
Role in the overall system
Related services for JupyterHub
This page covers installation and the agreed platform operations for JupyterHub. Custom code, the access layer and special confidentiality requirements remain clearly separated responsibilities that can be added when needed.
Support custom code and integrations
Keep custom extensions, interfaces and dependencies controlled, updated and supportable.
View service Secure accessConnect users, sites and systems
Add identity-based access and private network paths as a separate operational layer.
View service Operate confidentiallyAssess Section 203 requirements separately
For professional secrecy holders, define contractual, access and infrastructure requirements in a dedicated operating model.
View serviceThree relevant adjacent paths instead of a long list of further products.
View the overall systemFrequently asked questions about hosting for JupyterHub
Answers about users, images, GPUs, data and operations.
- Hosting for JupyterHub with WZ-IT starts at €99.90 net per month. It includes a dedicated size XS instance (2 vCPU, 2 GB RAM, 40 GB NVMe SSD), updates, daily backups with 7 days of retention, 24/7 monitoring, 5 TB of outbound traffic and a first response to critical incidents by the end of the next business day. Larger instances and higher service levels cost extra; the configurator shows the total price.
- The entry level is a dedicated size XS instance with 2 vCPU, 2 GB RAM, 40 GB NVMe SSD for €99.90; it suits lightweight applications as well as test and development environments. Size S with 2 vCPU, 4 GB RAM, 80 GB NVMe SSD costs €129.90. We check which size JupyterHub needs in production before provisioning. Size M (4 vCPU, 8 GB RAM, 80 GB NVMe SSD) costs an extra €29.90 excl. VAT, L (8 vCPU, 16 GB RAM, 80 GB NVMe SSD) an extra €89.90 excl. VAT and XL (16 vCPU, 32 GB RAM, 80 GB NVMe SSD) an extra €199.90 excl. VAT, each per month. Additional storage costs €4.99 excl. VAT per 50 GB and month.
- No. WZ-IT does not limit the number of users. How many users can work smoothly at the same time depends on usage and the chosen instance size XS to XL.
- Hosting for JupyterHub can be cancelled monthly, with no minimum term and 30 days' notice to the end of the month.
- Germany and Switzerland are available at the same prices, in both cases without US clouds. The data centres are ISO 27001 certified; in Germany we additionally operate with a German provider whose data centres are BSI C5 attested. The Section 203 Managed Cloud for professional-secrecy holders is available in Germany only.
- We typically provide a production instance within a few business days after signing. For a trial, we set up a test instance, usually on the next business day; it runs free of charge for 7 days and without payment details.
- Yes. One .de domain is included with every hosting plan. Alternatively, connect your own domain or subdomain with a CNAME record.
- Spawner, isolation, profiles, storage and GPUs materially change architecture and price.
- It is configurable, but versioned base images improve security and reproducibility.
- Yes. Pools, quotas, drivers and images are planned for the workloads.
- Yes, especially when data or GPU systems must remain local.
- Persistent home and project areas are backed up within the agreed scope.
Knowledge
More about JupyterHub
Tutorials & guides
- Self-Hosted ChatGPT: vLLM with Qwen3.5-122B on Two RTX PRO 6000 Blackwell GPUsYour own ChatGPT, running entirely in-house: a familiar chat interface, a large language model on your own hardware behind it, without a single prompt going...
- Self-Hosted Langfuse: LLM Observability and AI Logging for the EU AI ActAnyone bringing AI into production business processes quickly faces an uncomfortable question: what is actually happening in there? Which prompt went to which model, why...
Matching solutions for your project
- KeycloakOpen-source identity and access management
- PostgreSQLAdvanced open-source object-relational database system
- vLLMHigh-performance inference and serving engine for large language models with high concurrency.
- MLflowOpen-source platform for experiments, evaluation, model management and the lifecycle of production AI systems.
- GitLabPlatform for source code management and DevOps
- ForgejoSelf-hostable software forge for Git, collaboration, CI/CD and packages
Reviews & projects
Client feedback and projects worldwide
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT
Read client reviews
- Secure your Proxmox & backup setup
- Modernize your infrastructure - sovereign
- Plan a sovereign open-source stack
- Integrate a local AI solution
- Modernize your legacy software
- Cut cloud cost - up to −81%
- Build a high-availability Proxmox cluster
- Virtualize with Managed Proxmox
- Design an open-source AI architecture
- Get collaboration fully managed
- Ship your prototype to production
- Connect sites and clusters securely
Hosting & operations
Enquire about hosting and operations for JupyterHub
Briefly describe the current state and objective for JupyterHub. We assess infrastructure, integration, and ongoing operations.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.