Sales website
Product presentation, guidance and security information. No account login, working checkout, assessment intake or customer software distribution is provided on this public site.
Clear boundaries.
Serious engineering.
FieldKitOS is a portable security-workflow product in development. We describe what the current workbench does, what it doesn't do and which production controls remain to be built.
No accreditation claimed. FieldKitOS is not presented as an accredited government or classified-workload platform, independently certified security product, production scanning backend or managed protection service.
01 / CURRENT STATE
What exists today.
Separate public marketing from the local workbench, and evaluation features from operational service promises.
Portable software
Browser-based planning and records, local SHA-256 manifests, review utilities, public-resource references and a separate offline package. These require validation before paid release.
Subscription service
A private Node/SQLite starter exists in development. Live billing, customer recovery, secure licence issuance and protected package delivery are not connected for public purchases.
Record boundaries
Module records typically remain in page memory or opt-in browser storage until exported. They do not automatically sync between computers, and optional saves require suitable local information-handling care.
02 / PROFESSIONAL EVALUATION
Evaluate against your environment.
Professional use starts with a defined scope, test cases, approved information classification and a clear account of who is responsible for the system.
A checksum is not chain-of-custody proof; a browser warning is not active intrusion prevention; a planning worksheet is not certification.
01
Define the permitted workflow
Specify systems, data types, access permissions and excluded actions.
02
Test data preservation
Check exports, reload behaviour, browser storage, malformed input and offline limits.
03
Require evidence before deployment
Verify release integrity, support commitments and appropriate technical and legal controls.
03 / ENGINEERING ROADMAP
Controls to build and validate.
These are proposed safeguards — not capabilities we claim to operate today.
Trusted releases
Signed package distribution, verified release manifests, hashes, rollback policies and software inventories.
Identity & recovery
Customer accounts, access recovery, MFA and revocable subscriptions linked to verified billing events.
Secure delivery
Protected downloads, customer entitlements and production infrastructure separated from the public marketing site.
Auditability
Event records, security review, documented threat models and reliable administrative controls.
Information handling
Clear retention, storage, encryption, backup, deletion and deployment boundaries for sensitive workloads.
Human-controlled execution
Explicit authorised scope, review and stop controls for any future scanning, AI or endpoint integrations.
FAQ
Direct answers.
Is FieldKitOS approved for government use?
No approval or accreditation is claimed. Suitability depends on your environment, workload, organisational review and applicable procurement requirements.
Does visiting this website expose customer assessment data?
This public sales website has no assessment-input form or cloud case backend. Like most hosts, Cloudflare may process ordinary connection information to deliver the site. The separate workbench has its own local-data and external-service boundaries.
Does the product run scans automatically?
No. The current workbench focuses on planning and review, alongside deliberately bounded user-initiated checks. It does not silently run network scanning or protection enforcement.
Are subscriptions and secure product delivery live?
Not yet. The seller service is a development starter and is not connected to a live checkout or production customer-access system.
REVIEW THE PRODUCT
Explore before you decide.
See the public module walkthrough and current capabilities without accessing the actual console or software distribution.