A small catalog we can actually deliver
RYVARA sells one thing today: an unmanaged Ubuntu server you can order, reach over SSH and operate from a control panel. Everything on this page is either something the product does, or something it does not.
Built the other way round
Most hosting catalogs start wide and fill in the delivery later. RYVARA started from the opposite question: what can a customer buy, receive and operate end to end without anyone stepping in behind the scenes to make it work? The answer, honestly measured, was one server — so the catalog is one server. Every configuration published here has a provisioning path that has actually been run, and every control in the workspace reports what the provider really did rather than what was requested.
Four rules, each one checkable
Stated as things you could catch us breaking rather than as adjectives, because a value nobody can test is decoration.
An absence is named
Where a figure is missing, the page says which kind of missing it is — not installed, never reported, or unreachable. A zero standing in for “nobody looked” is treated as a defect.
Done means observed
A control that reports success has had that success confirmed against the provider or the server. Requesting something and reporting it as finished is the failure this rule prevents.
Sold means provisionable
A region or a plan appears in the configurator only after a real machine has been built through it. The catalog cannot advertise infrastructure that has never been delivered.
The limits are published
No automated backups, one region, unmanaged. These are on the page before checkout rather than in a support reply afterwards.
Frequently asked, answered specifically
The questions a first-time buyer actually asks, answered from what the product does today rather than from what it might do later.
One Starter server in Mumbai running Ubuntu 24.04 LTS, unmanaged, billed monthly. The full specification is on the pricing page before you pay, and the server validates that same configuration again when the order is created.
No. RYVARA takes no automated backups and none are included. Anything you need kept, you must copy off the server yourself. Where the provider offers snapshots, the workspace calls them snapshots rather than backups.
RYVARA operates the platform around your server — ordering, provisioning, power, access, firewall, recovery and monitoring ingestion. Operating-system updates, the software you install and its data are yours.
Only where one has actually been built. A region appears in the configurator once a real machine has been provisioned and verified in it; today that is Mumbai. Regions are opened one at a time rather than listed in advance.
Through the workspace, raised against the specific server rather than a shared inbox, so the ticket carries that server's activity with it. Platform incidents are published on the status page.
The order stays visible with the failure recorded against it rather than disappearing, and no server is reported as ready until the provider confirms it. Nothing is charged for infrastructure that was never delivered.