FT Internal Tools

Three internal web applications that automate the release, environment and deployment workflows, plus the shared Python and JavaScript libraries they are built from. Source: Friendly-Technologies/ft-internal-tools.

The applications

Application	What it does	Port
CI/CD Manager	QA builds, release new build, finalize sprint (version bump, changelog generation, tag and branch, docs-portal build, release e-mail), Harbor and branch cleanup.	5001
Environment Manager	Dynamic Kubernetes environments through ArgoCD GitOps.	5002
Deployment Manager	Docker Compose deployment artifacts from service contracts: contract sync, environment wizard, generate, deploy over SSH, health and smoke checks.	5003

Application

What it does

Port

CI/CD Manager

QA builds, release new build, finalize sprint (version bump, changelog generation, tag and branch, docs-portal build, release e-mail), Harbor and branch cleanup.

5001

Environment Manager

Dynamic Kubernetes environments through ArgoCD GitOps.

5002

Deployment Manager

Docker Compose deployment artifacts from service contracts: contract sync, environment wizard, generate, deploy over SSH, health and smoke checks.

5003

The release process these tools implement is documented on the portal under Release Process and Sprint End Checklist.

Shared libraries

Independently versioned packages under ft-tools-shared-libs/, installed by the apps as git subdirectory dependencies.

Library Purpose

Library	Purpose
`ft-flask-auth`	Magic-link login and JWT
`ft-harbor-client`	Harbor registry
`ft-jira-client`	Jira issues, references and the fixed-build field
`ft-json-storage`	JSON file storage
`ft-smtp-service`	SMTP
`ft-k8s-client`	Kubernetes API
`ft-argocd-client`	ArgoCD
`ft-github-client`	GitHub through the `gh` CLI and a REST transport
`ft-deployment-engine`	Compose bundle generation
`ft-db`	SQLAlchemy and Alembic setup for the apps' databases
`ft-settings-store`	Settings kept in JSON or Postgres
`ft-ui-core` (JS)	Auth cookies, themes, modals, toasts, `apiFetch`

ft-flask-auth

Magic-link login and JWT

ft-harbor-client

Harbor registry

ft-jira-client

Jira issues, references and the fixed-build field

ft-json-storage

JSON file storage

ft-smtp-service

SMTP

ft-k8s-client

Kubernetes API

ft-argocd-client

ArgoCD

ft-github-client

GitHub through the gh CLI and a REST transport

ft-deployment-engine

Compose bundle generation

ft-db

SQLAlchemy and Alembic setup for the apps' databases

ft-settings-store

Settings kept in JSON or Postgres

ft-ui-core (JS)

Auth cookies, themes, modals, toasts, apiFetch

Design documents

Document	Covers
SDD — Version Control Service	DEV-2755. Generating the Version Control record from the finalize-sprint flow and publishing it for support engineers.
Version Control — design reference	The long-form companion to that SDD: gap analysis against the current code, the snapshot schema, the checklist generator and the delivery schedule.
QA Build from a Jira Issue	Start, retry and submit a QA build from a Jira issue; the warnings, the hold on a branch, and the setup.
SDD — QA build from Jira	The Forge app, the server door, the job and hold stores, and the decisions behind them.
Dependency and Vulnerability Reports	What is inside each service image and which known vulnerabilities affect it; how to request and read the reports.
SDD — Dependency reports	The GitHub workflow, the generator, the Forge app and the Confluence layout behind the reports.

Document

Covers

SDD — Version Control Service

DEV-2755. Generating the Version Control record from the finalize-sprint flow and publishing it for support engineers.

Version Control — design reference

The long-form companion to that SDD: gap analysis against the current code, the snapshot schema, the checklist generator and the delivery schedule.

QA Build from a Jira Issue

Start, retry and submit a QA build from a Jira issue; the warnings, the hold on a branch, and the setup.

SDD — QA build from Jira

The Forge app, the server door, the job and hold stores, and the decisions behind them.

Dependency and Vulnerability Reports

What is inside each service image and which known vulnerabilities affect it; how to request and read the reports.

SDD — Dependency reports

The GitHub workflow, the generator, the Forge app and the Confluence layout behind the reports.

Developer-facing notes that change with the code — file layouts, gotchas, test commands, deployment steps — stay in the repository’s README.md and CLAUDE.md files. This section carries the documents that outlive a single change.