About Orivana

What Orivana is (and is not)

Orivana is an independently operated publication at https://orivana.xyz, published by Ben Liu. We write original operator guides, topic playbooks, and curated stacks with lab notes — backups, upgrades, auth, and failure modes. This is a personal technical column first — a full project directory stays soft-launched until we choose to reopen it.

We are not a mirror that republishes other websites' articles, and we do not paste upstream README files as our own editorial. Navigation aids (names, licenses, short blurbs) are not our article archive; the pages we expect people to read are the guides and lab-noted reviews.

Who we are

Ben Liu (Independent publisher & homelab operator) runs this site for a global English audience. We are not affiliated with the maintainers of third-party projects we discuss. Corrections and privacy requests: support@orivana.xyz or the contact form. Methodology: how we review; standards: editorial policy.

Review benches run on a mini-PC Proxmox lab (Debian guests, Docker Compose) plus a spare VPS for public TLS drills. Notes record Compose pins, restore drills, and exposure mistakes — not marketing blurbs.

• Primary: mini-PC class host under Proxmox VE with Debian LXC/VM guests
• Workloads: Docker Compose stacks (Caddy/Traefik edge, Vaultwarden, Immich samples, Ollama experiments)
• Secondary: small VPS for ACME/TLS and remote-access drills only
• Backups: local snapshots + encrypted offsite object storage; quarterly restore drills

What readers can find today

• Original operator guides — install-second writing with concrete ops steps
• Category topic playbooks for shortlisting stacks
• Curated stack collections for common jobs
• Project catalog pages exist for stacks/lab notes but stay out of sitemap and public nav until we reopen Catalog mode

Original work vs navigation aids

Guides, comparisons, collections, topic playbooks, featured summaries, FAQs, and lab notes are written for Orivana from operator practice. Short project blurbs and filters help you find names — they are navigation aids, not our article archive. We do not claim ownership of third-party software. Always verify licenses and security practices on each project's official site and repository before you deploy.

How we publish

1. Research — shortlist by category constraints, upstream docs, and operational fit.
2. Bench notes — record environments, failure modes, and restore habits on featured tools and guides (see lab notes on featured pages).
3. Draft — write in operator language: backups, auth, upgrades, when to walk away.
4. Correct — accept reader tips at support@orivana.xyz and update pages when material facts change.

Accountability

We respond to factual corrections and privacy requests at support@orivana.xyz, typically within 2–3 business days. We do not sell editorial rankings. When advertising is enabled, units are labeled "Advertisement".

Publisher

Brand

Orivana

Website

https://orivana.xyz

Publisher

Ben Liu

Role

Independent publisher & homelab operator

Public contact

support@orivana.xyz

Privacy contact

support@orivana.xyz

Operating model

Independently operated personal publication. No corporate parent is claimed on this page. For partnerships or press, use the contact page.

Advertising

Orivana may display ads served by Google AdSense and other partners to keep the site free. Advertisements are marked as "Advertisement". Ad partners may use cookies or similar technologies as described in our Privacy Policy and Cookie Policy.

Contact

Questions, corrections, or partnership requests: /contact or support@orivana.xyz. Privacy: support@orivana.xyz.