Complete project index

Apps & Control Planes / Built / deployed

Fimi Access

Browser infrastructure workspace built from a pinned Termix base with a custom Fimi brand layer, reproducible patch set, SSH agent integration and gateway access.

STATUSBuilt / deployed
AREAApps & Control Planes
STACK6 documented technologies
INTEGRATIONS5 connected / bounded services
01

OVERVIEW

What I built.

Browser infrastructure workspace built from a pinned Termix base with a custom Fimi brand layer, reproducible patch set, SSH agent integration and gateway access.

02

Maintained the branding and behavior changes as a reviewable patch/overlay instead of an untraceable fork.

03

Integrated SSH-agent based access, gateway routing and Tailscale-reachable target hosts.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Browser -> Cloudflare/Caddy service gate -> Fimi Access application -> SSH agent socket -> target host.

02
Architecture boundary

Upstream engine remains pinned and attributed; user-facing identity and selected behavior are changed by the Fimi patch layer.

03
Architecture boundary

Runtime keys, sessions and secrets remain outside Git.

03

NETWORK / DATA FLOW

What talks to what.

TRACE PATHFocus or tap a stage to trace the flow from source to that point.
04

TECHNOLOGY STACK

The technical surface.

01TypeScript
02Docker
03SSH
04Tailscale
05Caddy
06Termix
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Browser -> Cloudflare/Caddy service gate -> Fimi Access application -> SSH agent socket -> target host.

  2. 02

    Upstream engine remains pinned and attributed; user-facing identity and selected behavior are changed by the Fimi patch layer.

  3. 03

    Runtime keys, sessions and secrets remain outside Git.

06

TESTING & VALIDATION

How I know it works.

TEST 01

Pinned upstream commit verification

TEST 02

Patch/overlay reproducible build

TEST 03

Image build and scan

TEST 04

SSH-agent authentication

TEST 05

Gateway/Tailscale target reachability

TEST 06

Metrics compatibility patch validation

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

COREFimi Access
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01NOTEBrand patch
02NOTEOverlay assets
03NOTEDockerfile
04NOTEBuild script
05NOTESSH agent sidecar
06NOTELicense/attribution preservation
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

—Derived from Termix 2.7.1; upstream authorship is preserved

—Runtime keys/sessions remain outside Git

—Internal protocol/schema names intentionally remain compatible

10

RESULT / CURRENT STATE

What this produced.

A browser-based SSH/infrastructure workspace with a reproducible customization layer and preserved upstream attribution.

Quick navigationEsc