Run W2P Solution on your own servers

When does on-premise fit, and when does managed hosting fit better?

The managed yearly subscription, on Netbase VPS or Netbase Cloud, is the right choice for almost every subscriber: Netbase holds the infrastructure, runs the automatic upgrade pipeline, and there is nothing to operate on your side. On-premise fits a narrower case: an organisation whose internal policy, data-residency requirement or procurement rule requires that the software run on infrastructure it controls directly. If that constraint does not apply to you, the managed subscription is simpler and is kept current automatically; on-premise asks you to take on that responsibility yourself.

What is actually delivered with an on-premise licence?

An on-premise deployment is packaged for each release as signed container images with a Compose bundle, or as a tarball for a non-container install, together with an install guide, system requirements per edition and an upgrade command-line tool. Installation and setup are agreed in the proposal rather than left to the client alone. One production domain and one staging install are included per licence. A signed licence file ties the installation to the client and its term; the installation keeps running and keeps the client's own data fully in the client's control whether or not maintenance is later renewed, but the update channel and the connection the designer and pricing engine rely on for file generation stop once maintenance lapses.

What does the client operate, and what stays with Netbase?

The client runs the servers: provisioning, backups, scaling, monitoring and restore drills are the client's responsibility, not Netbase's, because the instance is not a member of the managed fleet and receives no automatic upgrades. Netbase's side is the release itself: signed packages, a changelog, migration scripts, and an update channel the client's own upgrade tool connects to while maintenance is active. Client-built extensions to the installation are the client's own responsibility unless covered separately by a services contract.

How does an on-premise store still reach the print engine every store depends on?

Every W2P Solution store, managed or on-premise, depends on the same print-production engine for file generation and designer rendering. An on-premise installation reaches that engine through a licensed relay rather than holding a direct credential itself, so the client's server never needs to manage that connection on its own; the relay enforces the same usage limits the licence defines. This is an architectural fact about how the product works, not a feature a client configures.

What is the commercial shape?

An on-premise licence is arranged by proposal: a licence term, structured as one-time or annual by owner choice, together with a maintenance and updates subscription that covers security and feature releases and keeps the update channel and the print-engine relay active. Client-specific deliverables, access and handover are defined in the engagement contract. Pre-existing software, products, APIs and third-party components remain subject to their respective ownership and licence terms. Current plan details for an on-premise licence are given on request through a project brief; this page describes what is delivered, not what it costs.

What happens if maintenance lapses?

The installation keeps running and the client keeps full access to run it and export its own data; what stops is the update channel and the print-engine relay connection, so the installation no longer receives new releases or security patches and cannot generate new print-ready files through the shared engine until maintenance is renewed. Business data stays on the client's own infrastructure throughout, maintenance active or not.