Hyur — boutique-hotel website system

• The complete Hyur source: a single-page boutique-stay website you configure from one TypeScript file.
• Buyer documentation: install, customize, media and rights records, deploy, and troubleshooting.
• Two fictional example configurations with abstract placeholder media you replace with the property's own.
• Bundled typefaces under the SIL Open Font License, with their license texts.
• A release manifest and a deployment verification script that checks a live deployment against the release.
• The Vlavera Professional License v2 in the repository.
• Read access to the private Hyur repository on GitHub, where every future release of Hyur is published.

Installed and deployed to Vercel from a clean package in two clean-room runs by a context-free AI agent during release-candidate testing.

Framework

Next.js 16.3.4, App Router, statically prerendered pages

UI

React 19.2.7

Language

TypeScript 5.9.3

Styling

CSS Modules — no Tailwind, no UI library

Fonts

Bundled locally with next/font/local

Tests

Vitest 3.2.6

Requirements

Node.js 24.x, npm 11 or newer, Git, and a GitHub account

Configuration only:

• Property identity, wordmark, tagline, and every line of copy.
• Three brand colours, validated for WCAG AA text contrast at build time.
• Display and body typefaces from the bundled set, and an optional logo.
• One to twelve rooms with guests, beds, features, and images.
• Surroundings, gallery, enquiry destination, contact details, policies, and social links.
• Title, description, canonical domain, and indexing.

These require editing the code:

• Section order, a new section, or a new page.
• A colour or typeface outside the supported set.
• Interface wording such as the skip link or guest counts.

• Unlimited projects.
• One license covers every website you build with Hyur, for yourself or for your clients. There is no project limit.
• You hand the finished project to its client, who may keep, host, maintain, and modify it indefinitely.
• Before you hand over the code, give your client this license and get their agreement to its restrictions. They get that one site: they can't build another project from it or pass it on as a theme.
• You may not sell, share or redistribute Hyur as a theme, template or starter, whether you've changed it or not.
• Keep the source in a private repository, never a public one. Putting the finished website online is fine; publishing its code is not.
• Don't add anyone to the Hyur repository or share your access to it. Your employees and contractors get the code from you privately, for example from your own private repository.
• You may modify the source, deploy it, keep it in a private repository, and charge your clients for your work.
• Your employees and contractors may work on your projects without separate seats.
• No public Vlavera attribution is required on the website.

This is a summary. The full license is what applies. Read the Hyur license

The full Vlavera Professional License v2 is in the repository and is linked at checkout, together with the purchase terms.

14 calendar days of email support from the order date, for installation and the two tested Vercel deployment paths documented in the package. There is no response-time promise, and customization work, other hosts, third-party integrations, and general development consulting are outside it.

Your purchase includes access to the Hyur repository and every future release published to it, including major versions and redesigns. Vlavera publishes releases when it chooses; there is no schedule. If the repository is ever retired, you get 30 days' notice by email and keep every release already published.

Refunds follow the refund policy.

Deployment is tested and documented on Vercel, on a plan that permits commercial use: deploying with the Vercel CLI, and deploying prebuilt build output. Vercel's Git-integration path and other hosting environments are untested in V1.

• One page with a fixed section order, and no separate room pages.
• Brand changes beyond three colours, the bundled typefaces, and a logo require editing CSS.
• Interface strings are English; there is no multilingual support.
• No CMS, booking engine, availability, prices, or payments.
• The examples ship with abstract placeholder media: supply the property's own photography before launch.
• Text placed over photographs is not checked for contrast automatically.