How do Verify and Horizon fit together?

Verify is the scoped review. Horizon is the continuous monitoring layer used only when the site needs ongoing coverage after that review.

Does Verify require a full integration project?

Usually no. Most Verify engagements begin from standard exports and a defined review scope rather than a custom systems integration.

Can Horizon run inside our own environment?

Yes. Horizon can be structured around customer-controlled deployment models, including private cloud, on-premise, and controlled environments where data residency and access boundaries matter.

Documentation FAQ

Frequently Asked Questions

Scope, deployment, and data handling across Verify and Horizon.

Security & Deployment Boundaries

Can I run Oxaide without internet?

Yes. Customer-controlled deployments can be structured for restricted environments where raw data and system access stay within the customer perimeter.

Where is customer data handled?

That depends on the product and deployment path. Verify follows a managed review workflow for the agreed scope. Horizon can be deployed in customer-controlled environments when residency and perimeter control are stricter requirements.

Do you train on my data?

No. Customer data is not used to train shared models.

Verify & Audit

What does Verify actually do?

Verify is a scoped technical review that works from the telemetry and asset context you provide. The output is an engineering report that clarifies asset condition, material risks, and recommended next steps.

Does Horizon require Verify first?

Usually yes. Verify establishes the baseline so Horizon starts from the actual condition of the asset rather than a generic assumption set.

Commercials

How is Verify priced?

The standard Verify diagnostic is S$4,800 for one bounded asset block, with a written report in 5 business days. Broader portfolio work or unusual reporting requirements are scoped separately.

How is Horizon commercialised?

Horizon pilots typically start from S$35,000 and are scoped around telemetry path, deployment boundary, integration needs, and reporting model rather than sold as a generic self-serve plan.

Operating posture

Scope first

Defined review scope

Boundary, telemetry window, and mandate question are pinned down before conclusions move.

Encrypted handling

Protected review workflow

Review traffic and operating data are handled with encrypted transfer and controlled access.

Customer boundary

Customer-controlled deployment

Managed, private, and isolated deployment paths are available when the environment requires them.

Direct accountability

Principal sign-off

Technical accountability stays close to the method rather than disappearing into a generic workflow.