Captain’s Toolkit Documentation

Captain's Toolkit is a browser-based marine operations application designed to keep important vessel information organized in one place.

Unlike a hosted SaaS service, Captain's Toolkit is distributed as source code. You deploy the application to your own hosting environment and can modify its interface, branding, workflows, and functionality according to your project requirements and license.

The application follows an offline-first approach. Core vessel data can remain available locally in the browser without requiring a permanent internet connection.

An optional PHP/MySQL backend extends the application with account-based cloud backup and restore functionality.

Captain's Toolkit can be used as a ready application, a starting point for a customized marine tool, an internal application, a client project, or the technical foundation for a larger marine-related product.

Captain's Toolkit brings the main day-to-day vessel management workflows into one responsive application.

The modules are designed to work together while remaining separate enough to be adapted, removed, or extended for a particular vessel, client project, or marine workflow.

Captain's Toolkit is designed so that the main application does not depend on a backend server for normal everyday use.

The frontend runs in the browser and stores core application data locally. This allows vessel information and essential workflows to remain available even when an internet connection is unreliable or unavailable.

The architecture is divided into two main layers: a standalone frontend application and an optional PHP/MySQL backend.

The frontend handles the user interface, vessel-management modules, local data, Progressive Web App behaviour, and offline operation. The backend can be added when account-based cloud backup and restore functionality is required.

Marine environments do not always provide reliable connectivity, so Captain's Toolkit uses an offline-first approach rather than assuming the application will always have access to a server.

Core application data is stored locally in the browser. Users can therefore continue accessing and managing vessel records when connectivity is limited.

Internet access is mainly required for functionality that depends on a remote server, such as optional account-based cloud backups.

Because browser data can be removed if local storage is cleared, regular backups are recommended for important long-term records.

Captain's Toolkit is built as a Progressive Web Application (PWA).

On supported browsers and devices, it can be installed and opened in an app-like standalone interface while still being deployed and maintained as a web application.

The PWA architecture provides offline caching, application icons, standalone display, responsive layouts, and offline fallback behaviour.

Installation behaviour varies by browser and operating system, but the application is designed for both desktop and mobile use.

Captain's Toolkit uses local browser storage as the primary data layer for offline operation.

This allows the core application to work without requiring a remote database or backend server.

Local data belongs to the browser environment in which it was created. It therefore does not automatically appear in another browser or on another device.

Application data can be exported to a local backup file. When the optional backend is configured, backups can also be stored remotely under a user account.

Captain's Toolkit provides two approaches to protecting application data: local backups and optional cloud backups.

Local backups allow application data to be exported and retained independently. They can be used for manual archiving, transferring data, or restoring records later.

When the optional backend is installed and configured, authenticated users can also save backups remotely, view backup history, and restore previously stored application data.

Cloud backup is optional and is not required for the core application to operate.

Because Captain's Toolkit is offline-first, locally stored data belongs to the browser and device where it was created.

The optional backend provides a backup-and-restore workflow that can be used to move application data between devices. For example, a user can create a cloud backup on one device, sign in from another device, and restore that backup.

This should not be confused with continuous real-time synchronization.

The supplied backend provides account-based backup and restoration rather than live record-level synchronization between devices.

Captain's Toolkit uses a straightforward web stack intended to keep the codebase understandable, portable, and adaptable.

The frontend is built with standard web technologies and does not depend on a large JavaScript framework.

The optional backend adds server-side functionality for users who need account-based cloud backups and restoration.

The technical requirements depend on whether Captain's Toolkit is deployed as a frontend-only application or together with the optional backend.

For frontend-only use, the application requires a modern browser and suitable web hosting for production deployment. A MySQL database is not required for core offline operation.

The optional backend requires a PHP-capable hosting environment and a MySQL or MariaDB database.

Captain's Toolkit is a self-hosted source-code product rather than a managed SaaS service.

The frontend can be deployed by itself when offline operation and local backups are sufficient. The optional PHP/MySQL backend can be added when account-based cloud backup and restore functionality is needed.

The application can be deployed on a dedicated domain, a subdomain, or within a subfolder of an existing website.

Detailed server paths, configuration values, database setup, and production deployment instructions are included in the buyer documentation rather than reproduced in full in this public overview.

The PHP/MySQL backend is an optional extension rather than a requirement for running Captain's Toolkit.

It adds server-side account and backup functionality while leaving the offline-first frontend able to operate independently.

The backend is included as editable source code and can be inspected, modified, or extended for project-specific requirements.

It should not be treated as a complete real-time synchronization platform by default.

Captain's Toolkit is supplied as editable source code rather than as a closed hosted application.

Developers can adapt the project to different vessels, workflows, organizations, internal tools, client projects, and commercial applications according to the terms of the purchased license.

Because the source code is included, both the visual identity and application functionality can be changed rather than being limited to predefined SaaS settings.

Captain's Toolkit is sold as a downloadable source-code package.

The package is intended to provide both a usable offline-first marine application and a technical foundation that developers can inspect, customize, rebrand, and extend according to the purchased license.

This Public Documentation is designed to help potential buyers understand Captain's Toolkit before purchasing it.

It explains the main application modules, architecture, offline behaviour, data model, optional backend, technical requirements, deployment options, and customization possibilities without reproducing every implementation detail.

The purchased package includes more detailed technical documentation for installing and configuring your own copy of the application.

Buyer documentation covers areas such as project structure, frontend installation, backend installation, database setup, backend configuration, cloud backup configuration, PWA configuration, production deployment, updates, customization, and troubleshooting.

Implementation-specific configuration values and detailed deployment instructions are intentionally kept in the buyer documentation.

Captain's Toolkit is distributed as a commercial source-code product with Standard and Extended license options.

The source code can be modified and rebranded within the permissions of the selected license. Permitted deployment, client usage, and commercial use depend on the license purchased.

The original source-code package may not be redistributed, published publicly, or resold as a competing source-code product.

Always refer to the license supplied with the product for the complete terms that apply to your purchase.

Quick answers to common questions about Captain's Toolkit, its offline architecture, optional backend, customization, deployment, and source-code model.

Public Documentation provides an overview of the application, but the easiest way to understand Captain's Toolkit is to explore the interface.

Use the live demo to see the Dashboard, Vessel Profile, Voyages, Fuel, Maintenance, Crew, Emergency, Checklists, Exports, and Settings screens before purchasing.

If Captain's Toolkit fits your project, choose the appropriate license to receive the complete source-code package and detailed buyer documentation.