Fedora CoreOS based • immutable • monochrome

Quiet infrastructure with a tactile black-glass surface.

Vnyl is specified as a Fedora CoreOS-derived desktop/server environment: immutable at the base, monochrome at the surface, and strict about every public-facing detail.

Core features

Designed as a system, not a skin.

[IM]

Immutable base

Fedora CoreOS, Ignition, Butane, rpm-ostree, and local RPM ownership for Vnyl components.

[UI]

Obsidian glass interface

Black, white, alpha surfaces, 1px refraction edges, and typography instead of pictogram icons.

[VA]

BTRFS-first vault

Snapshot-oriented storage logic with BTRFS as the standard path and ZFS as an optional advanced channel.

[WI]

Wine compatibility layer

Fedora Wine packages as compatibility only. No Windows, proprietary DLLs, or Microsoft runtimes are bundled.

[GL]

Global release target

30-language first-boot flow with RTL-aware layouts, Noto fallback fonts, and input-method validation.

[SE]

Small public attack surface

Static-first PHP: no database, no sessions, no uploads, no tracking endpoint, and no build logic on shared hosting.

Architecture

The public domain is only the front panel.

vnyl.live is a landing surface. Build logic, repositories, image composition, validation reports, local RPM packaging, installer logic, dashboard behavior, and manual rendering belong inside the Fedora CoreOS-based Vnyl repository and ISO workflow.

No shared-host dependency

The website does not build, host, update, mirror, or distribute the operating environment. It only describes the product and provides contact points.

Security posture

Small exposed surface, clear responsibility.

AreaDecisionPractical effect
Site runtimeTwo PHP pages, no database, no sessions.Fewer moving parts exposed to the public internet.
HeadersCSP, HSTS on HTTPS, frame denial, nosniff, permissions policy.Reduces common browser-side abuse classes.
ContactMail links only, no public form.No form spam endpoint or upload handler.
Build logicNot executed on shared hosting.Compromise of the landing page cannot become a build-pipeline compromise.
Abuse policy

Direct reporting channels.

Vnyl is not designed for spam, malware hosting, phishing, unauthorized access, evasion services, or abusive network activity. Reports should include timestamps, source and destination addresses where available, logs, screenshots, and a concise description.

Report abuse

Use the abuse mailbox for urgent reports involving misuse, impersonation, network abuse, or public safety concerns.

abuse@vnyl.live