Technology Landscape

Technology Landscape is an interactive web application for visualising and governing your organisation's technology portfolio.

Key Features

• Technology Catalogue — a curated catalogue of 100+ technologies and tools (Docker, Kafka, Kubernetes, Azure DevOps, …) organised across domains such as Infrastructure Runtime, Software Delivery, Security & Identity, and Observability.
• Technology Radar — a radar view where each tool is assigned a lifecycle status: Identify → Select → Build → Permitted → Mandatory → Review → Sunset → Decommissioned.
• Capability Mapping — every tool is mapped to the technical capabilities it fulfils (compute, data & storage, routing, CI/CD, observability, …), giving a clear picture of coverage and overlap.
• Workspaces — create separate workspaces for different teams or contexts to manage their own technology choices independently.
• GitHub Sync — save and load your landscape configuration via a GitHub repository so your team can collaborate on a single source of truth with full version history.

Architecture

The application is fully stateless on the server side. No data is stored in the tool itself — everything runs entirely in the browser. Data is either kept locally in your browser or synchronised to a GitHub repository of your choice.

Technical Setup

• Frontend only — the entire application is a static single-page app built with vanilla HTML, CSS and JavaScript. No frameworks, no build step, no server-side rendering.
• Hosting — served via Cloudflare Pages, providing global CDN distribution, automatic HTTPS and zero-config deployments from Git.
• Data persistence — all user data (tool selections, statuses, workspace configurations) is stored in the browser's localStorage. Nothing is sent to or stored on any server.
• GitHub Sync — an optional feature that uses the GitHub REST API directly from the browser to read/write a JSON file in a repository of your choice. Authentication is handled via a standard OAuth 2.0 flow — the only server-side component is a lightweight Cloudflare Worker that securely exchanges the OAuth code for an access token (keeping the client secret out of the browser).
• No PATs — we deliberately avoid Personal Access Tokens. The OAuth App approach follows GitHub's recommended pattern: scoped permissions, no long-lived secrets in the browser, and easy revocation via GitHub settings.
• Portable — because there is no backend state, the app can be self-hosted on any static file server (Nginx, S3, Azure Static Web Apps, …) with minimal effort. The only requirement for GitHub Sync is a small OAuth token-exchange endpoint.