CFTS Documentation

CFTS Developed Platforms

CFTS develops and operates selected platforms where a focused service provides clearer control, easier support, or better integration with the infrastructure we already operate.

These platforms are not intended to replace established products unnecessarily. They are developed where CFTS has a specific operational requirement that is not well served by a standard product alone.

Current Areas of Development

Capability Purpose
Internet and uplink visibility Present useful connectivity and service-path information without exposing unnecessary internal detail
Monitoring and failover tooling Observe multiple internet paths and assist with identifying or responding to connectivity problems
Client service access Give authorised clients a controlled way to reach assigned VMs, machines, services, or operational functions
File and document delivery Provide controlled file sharing without relying on large email attachments
Infrastructure diagnostics Bring together useful network, host, and service information for troubleshooting and support
Virtual machine control Provide controlled operational actions without requiring clients or support staff to access the underlying virtualisation platform directly
DNS and network tooling Support DNS management, visibility, security integration, and related operational workflows
Documentation platforms Maintain practical client and engineering documentation close to the services it describes
Communications and workflow integration Improve the movement of service information between operational, support, and communications systems
AI-assisted operations Use locally controlled AI where it can assist with documentation, diagnostics, knowledge retrieval, and carefully bounded operational tasks

The exact systems used in each area may change over time as CFTS develops, replaces, or consolidates tooling.

Examples Within the CFTS Service Stack

edge.cfts.co

edge.cfts.co provides the CFTS Client Edge Portal.

It gives authorised clients a simpler access point to assigned VMs, machines, service links, and related functions without requiring direct access to the underlying infrastructure management systems.

file.cfts.co

file.cfts.co provides controlled file delivery for clients and internal teams.

It is intended for cases where ordinary email attachments are unsuitable or where CFTS needs clearer control over access, expiry, revocation, or download handling.

isp-status.cfts.co

isp-status.cfts.co/view provides a client-facing view of CFTS internet and uplink status.

The service presents useful operational visibility while deliberately keeping unnecessary internal network detail out of the public view.

docs.cfts.co

docs.cfts.co is the CFTS documentation and knowledge platform.

The documentation itself is part of the operational model: services should not depend entirely on undocumented knowledge held by individual engineers.

Not Every Tool Is Public

A significant part of the CFTS software layer consists of internal services, scripts, APIs, diagnostics, and automation that support engineers rather than clients directly.

These may help with:

  • service health checks
  • host and network diagnostics
  • controlled infrastructure actions
  • deployment and maintenance
  • backup and recovery workflows
  • DNS operations
  • data collection and reporting
  • support workflows
  • documentation maintenance

Keeping these tools internal can be as important as developing them. A useful engineering function does not automatically need to be exposed as a public service.

Lifecycle and Support

CFTS-developed platforms are treated as operational infrastructure.

Where appropriate, this includes:

  • source and configuration control
  • documented dependencies
  • access control
  • backup or recoverability considerations
  • testing before production changes
  • logging and diagnostics
  • maintenance and version review
  • retirement or replacement when a better solution becomes available

The aim is to avoid creating software that only one person understands or that becomes impossible to maintain once the immediate problem has passed.