Appearance

WAYSCloud Fonts ​

WAYSCloud Fonts is a privacy-first European web font service for openly licensed fonts.

It provides a CSS API compatible with the Google Fonts /css2 surface where it matters for normal day-to-day use, making migration practical for many sites with only a hostname change.

WAYSCloud Fonts is designed for teams that want a more transparent font delivery path, fewer third-party frontend dependencies, and a managed alternative to external font CDNs.

Why it exists ​

European transition is often discussed in terms of compute, storage, databases, and AI.

But the web also depends on smaller frontend-layer dependencies: fonts, libraries, stylesheet calls, DNS lookups, and other external requests that users never see directly, but that still become part of the real infrastructure behind a site.

WAYSCloud Fonts exists to make one part of that layer simpler and more transparent.

It is built for teams that want:

  • European font delivery
  • no third-party font CDN dependency
  • no edge logging of visitor IP, User-Agent, or Referer
  • clear provenance and license visibility
  • a migration path that feels practical, not theoretical

What it is ​

WAYSCloud Fonts is a managed font delivery service for openly licensed web fonts.

It is built for developers, websites, apps, and CMS users who want a more predictable and privacy-conscious way to serve fonts on the modern web.

The service is intentionally curated. It is not designed as a generic font mirror, but as a structured delivery platform for open-source web fonts with European hosting, visible provenance, and explicit licensing per family.

How it works ​

WAYSCloud Fonts provides a CSS API compatible with the Google Fonts /css2 surface. You link to a stylesheet URL, and the browser receives @font-face rules and loads the requested font files from WAYSCloud-managed European infrastructure.

One-line integration ​

Add this to your HTML <head>:

html
<link
  href="https://fonts.wayscloud.eu/css2?family=Inter:wght@400;700&display=swap"
  rel="stylesheet"
/>

Then use the font in your CSS:

css
body {
  font-family: "Inter", system-ui, sans-serif;
}

Multiple families ​

You can request more than one family in the same stylesheet URL:

html
<link
  href="https://fonts.wayscloud.eu/css2?family=Inter:wght@400;700&family=Source+Serif+4:wght@400;700&display=swap"
  rel="stylesheet"
/>

Migration from Google Fonts ​

For many projects, migration is simply a hostname change.

Before ​

html
<link
  href="https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap"
  rel="stylesheet"
/>

After ​

html
<link
  href="https://fonts.wayscloud.eu/css2?family=Inter:wght@400;700&display=swap"
  rel="stylesheet"
/>

The goal is not to make migration theoretical. It is to make it practical.

Supported request surface ​

WAYSCloud Fonts supports the Google Fonts CSS2-style request surface where it matters for practical migration.

Supported parameters ​

  • family=Inter:wght@400;700
  • family=Inter:ital,wght@0,400;1,400
  • display=swap
  • subset=latin,latin-ext when upstream subsets are available

Not supported in v1 ​

  • text=...
  • effect=...

If a request includes unsupported parameters, the response may omit them or reject the request.

What you get ​

  • WOFF2-only delivery for modern browsers and smaller transfers
  • font-display: swap baked into responses
  • European delivery path
  • No edge logging of visitor IP, User-Agent, or Referer
  • Curated catalog
  • Stable active URLs once a release is published

Frontend dependencies matter ​

Fonts are often treated as a minor implementation detail. In practice, they are still infrastructure.

They influence browser requests, caching behavior, dependency boundaries, and the overall predictability of how a site is delivered. For teams that want fewer unnecessary third-party calls and clearer control over what loads in the browser, that matters.

WAYSCloud Fonts is built around that idea: not just as a catalog, but as a practical way to reduce unnecessary frontend dependencies and make one part of the web stack easier to reason about.

Clear licensing and provenance ​

A core part of WAYSCloud Fonts is clarity.

The platform focuses on open-source font families with explicit per-family license information, source provenance, and structured technical metadata. Instead of treating fonts as anonymous assets, the product is designed to make it easier to understand what is being served, under which license, and from which upstream source.

Self-hosting ​

If you prefer to self-host font binaries, that remains a valid choice.

Each font family on WAYSCloud Fonts includes license context, and each family links back to upstream sources where relevant. You can bundle font files with your own build output and declare @font-face locally.

This means WAYSCloud Fonts is not positioned as the only valid way to use these fonts. It is the managed option for teams that want a simpler and more transparent delivery path.

Current scope ​

WAYSCloud Fonts is intentionally curated.

Not every Google Fonts family is available. Inclusion depends on curation, provenance, and redistribution fit for the service model.

That means the catalog is designed to grow deliberately rather than mirror everything indiscriminately.

Inspect tool ​

WAYSCloud Fonts also includes an inspection tool for public websites:

The tool performs a best-effort inspection of public HTML and CSS references to identify likely font usage and suggest compatible WAYSCloud Fonts replacements where possible.

This is intended as a practical migration aid, not a perfect rendering audit.

Privacy and transparency ​

WAYSCloud Fonts is built with a privacy-first approach.

The service is designed to avoid third-party trackers, advertising technology, and hidden cross-service dependencies in the font delivery path.

For product-specific privacy details, see: