Helios One · buyer workflow

Helios One security overview and questionnaire

Evidence summary · 24 October 2026

This page describes selected controls in the inspected Helios One code and documentation. It is evidence summary, not a security certification, independent audit, or universal promise about every deployment.

Controls in the documented paths

Staff access in the Mini ERP path requires an authenticated WorkOS identity mapped to an active member; tenant checks reject records belonging to another tenant.
Customer tracking uses an expiring or revocable bearer capability. Anyone holding a link can use it until expiry or revocation, so links must be treated as secrets.
Configured email handling validates recipients and headers. MCP writes require an explicit environment flag and confirmation in the cited runtime.
Runtime credentials are kept server-side in the documented deployment procedure. Developer usage logs omit message contents, filenames, IP addresses, browser information, and bearer tokens; optional PostHog telemetry is configured separately.
The optional vault encrypts selected files in the browser before upload and excludes vault files from email, AI, parsing, and server rendering in the cited path.
Public tools and staging pages instruct users to use public, fictional, or sample data. A staging or spec-mock result is not proof of a live ERP connector.

Questionnaire snapshot

Area	Answer	Boundary
Legal entity and service scope	Partial	Helios One Oy and the enabled order-form scope are identified; each customer’s production configuration controls.
Identity and tenant access	Partial	Controls are evidenced in the cited Mini ERP path; production configuration and independent testing are not represented here.
Credentials and writes	Partial	Server-side credentials and MCP write gates are documented; operational access review is not claimed.
Logging and retention	Partial	Selected minimised logs and expiry paths exist; developer logs have no automatic cleanup and no universal retention period is promised.
Incident response, vulnerability management, backup recovery	No claim	The inspected materials do not establish an approved runbook, SLA, RTO/RPO, penetration test, or restore test.
Subprocessors and residency	No claim	See /subprocessors; provider regions and transfer terms are service-specific.
Certifications and compliance	No claim	Helios does not claim SOC 2, ISO 27001, CMMC, ITAR compliance, or another certification.
AI processing	Partial	Anthropic is named for enabled extraction/drawing analysis; vault drawings are excluded in the cited path. Provider terms and model behaviour remain configuration-specific.

ITAR parts go in the ITAR vault. The optional vault is a technical feature and does not mean Helios is ITAR compliant or certified.

For a customer-specific security package, contact support@heliosone.fi and identify the exact plant workflow. Do not send secrets or controlled technical data in ordinary email.