OpenVibe.Host

OpenVibe.Host is two things. At openvibe.host it is hosting compared: a sourced comparison of cloud, VPS and dedicated plans, the offers providers post, domain prices and benchmarks people run, plus a console for your own servers. Behind it is the network's deployment plane, the ovhost CLI, which deploys every OpenVibe service.

Hosting plans

The README calls the catalog plan T20 step 3: "openvibe.host is hosting compared". Plans come from providers' official APIs through OpenVibe.Sources (category hosting) and from staff entries that must name their source URL. Each plan shows its monthly price, its price per vCPU and per GB of RAM and disk, the day the price was checked and a link to its source; price changes are kept as a history per plan, and OpenVibe.Watch can tell a visitor when a price changes. The order comes only from the sort a visitor picks, and affiliate links are marked with rel="sponsored nofollow noopener" and disclosed beside the link.

Offers

/catalog/offers lists what providers post on LowEndSpirit's Offers board, read from its public feed through Sources (LowEndTalk's and LowEndBox's feeds refuse the production host, so those sources are off): the headline, who posted it, the date and the price the headline states, with its monthly equivalent. Each links to its post, which has the final word.

Domains

/catalog/domains compares what registrars charge for each ending: the first year, a renewal, a transfer and the total over five years (the first year and four renewals at one registrar), with a mark where the renewal is more than a fifth above the first year. Prices come from registrars' public price lists through Sources, Porkbun's first. Each ending has its own page with every registrar's price and its change history. A name check asks the ending's registry over RDAP, the public lookup that replaced WHOIS: it says whether the name is registered (and through which registrar, since when and until when), prices the same name at popular endings, and links to the search at ten registrars.

Benchmarks

/catalog/benchmarks collects results people run on their own servers with YABS (Yet Another Bench Script). A signed-in member asks for a one-time link naming the provider and plan; YABS posts its result to that link when it finishes. A result keeps the CPU, memory and disk, Geekbench scores with their public link, fio disk speeds, iperf3 network speeds and the city and network YABS looked up, never the server's address, and never who ran it on the public page. Provider and plan pages show the medians.

The console

/console lists a signed-in person's own servers across Linode (Akamai), DigitalOcean, Vultr and Hetzner Cloud. Each account is connected with its own API token, which Host checks with the provider and then seals with AES-256-GCM; it is never shown again and is sent only to that provider's API. Servers can be powered on, off or rebooted from the list, each action is logged for the person, and a server links to a catalog plan of at least the same size for 15% less when there is one. Disconnecting deletes the token, and account export and deletion cover the accounts and the action log.

The deployment plane

The ovhost CLI holds the host inventory, validates environments, installs and rolls back releases, polls /api/ready, runs scheduled PostgreSQL backups and restore drills, and installs nginx vhosts transactionally. It is installed on the production host and deploys every service.

What it does not do

Static site hosting moved to OpenVibe.Space; *.openvibe.host answers with a pointer there. Sandboxed user code (Stage C) is not started.

How it fits the network

It uses OpenVibe.Network for sign-in and tokens, OpenVibe.Events for host.* events, OpenVibe.Sources for prices and offers, and OpenVibe.Search for its plan and provider pages; plan and provider pages have discussion threads on OpenVibe.Community, and provider pages link to reviews on OpenVibe.Reviews.

Status

STATUS.json's stage is "alpha". License: AGPL-3.0.