Filestash — bring-your-own infrastructure map

---
version: alpha
name: Filestash — bring-your-own infrastructure map
colors:
  primary: '#375160'
  surface: '#F2F3F5'
  text: '#313538'
typography:
  primaryRole:
    fontFamily: Inter, sans-serif
    fontSize: 25.5px
    fontWeight: 700
  supporting:
    fontFamily: Inter, sans-serif
    fontSize: 20.4px
    fontWeight: 700
omitted:
- section: spacing
  reason: Measured geometry and responsive composition are documented below; no global
    spacing scale is inferred.
- section: rounded
  reason: Observed silhouettes and measured radii are described in Shapes rather than
    inventing a brand scale.
- section: components
  reason: This reference documents observed composition in prose, not an inferred
    component API.
---

## Overview

A standalone integration section combining a centered protocol word grid with a large storage-and-auth architecture diagram on a cool gray background.

Captured from https://www.filestash.app/ at 2026-10-15T06:08:57.741787+00:00. This image isolates `#bring-your-own`.

## Colors

primary: `#375160`; surface: `#F2F3F5`; text: `#313538`. Values summarize measured surfaces and visually reviewed foregrounds; illustration and photograph colors are not a complete brand palette. Retain the observed light/dark contrast rather than applying the accent to every element.

## Typography

The primary token is a sampled heading; supporting typography is sampled independently. Generated font-loader aliases are normalized to portable family names.

- h3 “Bring your own environment:”: 25.5px, weight 700, line height normal, tracking normal.
- a “S3”: 18.7px, weight 700, line height normal, tracking 0.85px.
- a “SFTP”: 18.7px, weight 700, line height normal, tracking 0.85px.
- a “FTP”: 18.7px, weight 700, line height normal, tracking 0.85px.
- a “FTPS”: 18.7px, weight 700, line height normal, tracking 0.85px.

## Layout

Begin with a short centered heading and a wrapping grid of protocol names. Beneath it place the architecture illustration with a user at the top, the Filestash engine in the middle and storage and authentication groups on either side. Measured padding is 50px top and 90px bottom.

Desktop image: 1440 × 772px at a 1440px viewport. Mobile evidence: 390 × 480px at a 390px viewport. The selected element measured 1440.00 × 771.59px desktop and 390.00 × 479.00px mobile. Integer crops use the measured document coordinates; page-edge subpixel rounding is limited to one pixel.

At 390px the architecture illustration is hidden entirely and protocol names reflow into a compact multi-line block. Heading size remains 25.5px; linked protocol samples are 18.7px bold. Do not shrink the desktop diagram into unreadable mobile artwork.

## Elevation & Depth

The diagram uses muted fills and connecting arrows rather than shadows; the background is flat #F2F3F5. Numeric blur/spread values were not measured; any recreation must tune them against the image.

## Shapes

Rounded diagram group containers contrast with a rectangular engine block. The text grid has no individual chip backgrounds.

## Components

A standalone integration section combining a centered protocol word grid with a large storage-and-auth architecture diagram on a cool gray background. Preserve the hierarchy and grouping described above rather than mixing this composition with unrelated page modules. This capture records one visible state; hover, focus, validation, menus and successful transactions are untested unless explicitly described. No credentials were entered and no form was submitted. Source-owned customer statements, prices and certifications remain source claims, not independently verified facts.

## Do's and Don'ts

- Do preserve the responsive grouping, reading order and measured type hierarchy.
- Do use original content and only substantiated claims when adapting this layout.
- Do keep labels readable and provide accessible focus and reduced-motion behavior in a new implementation; these are recommendations, not verified source behavior.
- Don't treat a static animation frame as proof of timings, easing or all interaction states.
- Don't reproduce source overflow or use decorative padding at the expense of readable mobile content.