365Networking
Snowdaddy Solutions

Web infrastructure of Snowdaddy Solutions

Separate engines, one house.

365 Networking is the web side of Snowdaddy Solutions. One public edge serves every 365 site from its own account; behind it stand the creator platform 365Entertainment, our own image engine ImageForge, the assistant Dove, and the engines of the 365 family. Every one of them is shown here with what it is today: live, built, or designed.

What runs is said to run. What is built is said to be built.

What runs today The map
The 365 rings around the Networking hub. Every icon on this site is drawn by ImageForge.

Running today

Four engines answer right now

These are the parts of 365 Networking that serve people today. Everything else in the family is built or designed, and says so on its own site.

  • The public edge

    One server that every 365 site and snowdaddy.net reach the public through: a certificate for every name, an account and a web root for every site, static files only, and every release verified against a pinned key before it installs.

    Live

  • 365Entertainment

    The creator platform: its public site, the creator Studio and the staff dashboard. Every consent is pinned to its exact words, and identity details are sealed a second time on top of encrypted storage.

    In production

  • ImageForge

    Our own image engine. It draws the icons and images of 365Entertainment on the server, with no image files, no font files and no outside services, and it drew every icon and share card of the 365 sites.

    Live

  • Dove

    The assistant inside the 365Entertainment Studio, answering from an open-weight model on a GPU server we operate, over its own encrypted link. It is off until the creator starts it, and it sends nothing on its own.

    In production

The map

Every engine, with its status

The upper half runs today. The lower half was built or designed for earlier servers that are no longer in service; each of those sites describes its engine as built, and nothing more.

  1. 365Hosting Standard live

    The hosting standard every 365 site is served to, and the customer software as it was built.

  2. 365Vault Built

    Files cut into parts, each part sealed with its own key and stored in a different database engine.

  3. 365Payments Built

    The Monero flow: one address per payment, ten confirmations, a signed webhook.

  4. 365Business Built

    Jobs, dispatch, a time clock, asset maintenance and a payroll export for small field businesses.

  5. 365Books Not running

    A sports-statistics project, behind responsible limits and legal review before anything is public.

  6. 365Proxy Design

    The front layer: visitors reach a public front, never the origin.

  7. 365Phoenix Dove live

    The intelligence: Dove in production, HAWK built and tested, the rest of the roster written.

Map of 365 Networking: running today, the public edge serves the 365 sites and 365Entertainment, ImageForge draws their images, and 365Entertainment reaches Dove over its own encrypted link; built or designed and not running: the hosting software, 365Vault, 365Payments, 365Business, 365Books and 365Proxy RUNNING TODAY The public edge a certificate per name, a room per site The 365 sites static, own accounts 365Entertainment creator platform ImageForge draws every image Dove own encrypted link BUILT OR DESIGNED, NOT RUNNING Hosting software BUILT 365Vault BUILT 365Payments BUILT 365Business BUILT 365Books NOT RUNNING 365Proxy DESIGN
Solid gold: running today. Dashed: built or designed, not running.

How a 365 site is served

Built here, signed here, checked there

Every 365 site is plain static files. Nothing on these pages runs a script, loads a font from elsewhere, or asks the browser to talk to anyone but the site itself.

Built
On our production workstation, from sources that are checked for encoding, working links, the content security rules and a list of words a factual site never needs.
Signed
Each site ships as a release signed with our release key.
Verified
The edge accepts a release only if its signature matches the pinned key and every file matches its hash; otherwise nothing is installed.
Swapped
The site's own account writes the new version beside the live one and swaps it in atomically; every earlier version is kept.
Served
From the site's own web root, over HTTPS only, with a policy that lets the page use nothing but its own files.
How a 365 site is served: sources are built and checked on the production workstation and signed; the edge verifies the signature against a pinned key and every file hash, the site's own account swaps the new version in, and visitors receive it over HTTPS PRODUCTION WORKSTATION Sources, built and checked words, links, encoding, CSP rules Signed release one per site, our release key THE EDGE Verified pinned key, every file's hash The site's own room own account, public/ served, earlier versions kept HTTPS Visitors
Nothing installs that was not signed here and verified there.

Principles

The rules every 365 site keeps

  1. Facts only

    Every sentence on a 365 site is true on the day it is published, and anything that is not running says so.

  2. Nothing from anyone else

    No outside fonts, scripts, analytics or trackers: the browser is told to accept code and images only from the site itself.

  3. Every site in its own room

    Each site has its own account and its own web root; one site's files are never another's.

  4. A person decides

    Dove suggests and the creator decides; nothing is sent in anyone's name on its own.

  5. Signed before it ships

    A release that does not match our pinned key, file for file, is refused.

  6. Our own engines

    ImageForge draws the images, and the pages are plain HTML from our own build script, with no framework and no outside service.

365 Networking

Separate engines, one house