The self-hosted PII gateway
The same OBVELO gateway, on a server you run. Text is masked on your machine; what it masks never reaches us. The images are built for your company, signed, and pulled from our registry in the European Economic Area.
Price and plans
Self-service purchase and the trial are coming soon. Until they open, a self-hosted installation is set up with you on request.
What the server needs
- Linux with Docker and Docker Compose v2, and
cosignto verify the image signatures (or an offline bundle checked withopenssl). - At least 2 CPUs and 4 GB of RAM; 8 GB with the name model.
- At least 10 GB of free disk for the images, the licence and the logs.
The installer checks each of these before it changes anything, and says which one is missing.
1. The trial
14 days, on the Standard plan's limits, for one server, once per company. It needs your company's EU VAT number confirmed in VIES (the Billing tab of your panel) — or, for a Polish company without one, its NIP confirmed in the official Polish register (the Self-hosted tab) — and an address at your company's own domain: the panel sends a link to that address, and opening it while signed in starts the trial. Addresses at free-mail providers cannot start one — contact us instead. A trial has no grace period: on its last day the gateway stops masking.
2. Buy
In the Self-hosted tab of your panel choose the plan, monthly or yearly, and the number of servers, then pay the balance in the Billing tab as for any plan. The licence is issued once the balance is paid. Adding or removing a server later takes effect at once and is settled pro rata for the days left in the period.
3. Install
- Download the licence file from the Self-hosted tab. You receive the installer kit and a pull token for the image registry from us.
- On each server run
obvelo install --licence FILE --server Nwith that server's own number. The installer refuses a number above the servers the licence covers. - The installer verifies every image signature, starts the gateway, makes the first gateway key (shown once) and prints the licence's state.
obvelo update rolls back by itself when the new version is unhealthy; obvelo diagnose writes a support bundle without content.
4. The licence and its end
The licence file is verified on your server with our public key. The gateway's admin page, its health report and its responses say when the licence ends, well in advance, and what happens then. A monthly licence keeps working for 7 days of grace after its period, a yearly one for 21 days. After that the gateway refuses every masking request: nothing is masked or forwarded, and it cannot be switched off. A renewed licence is uploaded on the admin page, or fetched by automatic renewal.
What reaches us
Our hosted service stores nothing from request content; a gateway the customer operates keeps a 30-day content log for the customer, on the customer's disk, which we never receive. Automatic renewal is off unless you switch it on (obvelo renewal on); then the gateway contacts our licence server only, and sends the licence and installation identifiers and three usage numbers for the month — never content. Your company is the controller of what it masks on its own server.