Skip to content
COREWARDBook 4-Week Pilot

Check what your machines report against what they were signed to do.

One platform, four weeks, no change to control logic. You get a verdict report tied to your own signed builds.

  1. Week 0

    Intake

    We agree on one platform or hardware-in-the-loop (HIL) bench, the telemetry it already emits, and who signs off the report.

    From you: One contact, access to a build pipeline, a sample of field or bench telemetry.

  2. Weeks 1 to 2

    Sign and map

    Keyless Sigstore signing in your CI with SLSA provenance and a CycloneDX SBOM. We write the twin: the states and transitions your machine is allowed to take, and map telemetry topics to twin events.

    From you: A review of the twin with your engineers.

  3. Weeks 3 to 4

    Shadow replay

    The reference twin replays real event streams in shadow mode. Verdicts are logged, not acted on, so nothing in production changes.

    From you: Nothing. The pilot runs beside your systems.

  4. End of week 4

    Audit verdict report

    Every verdict with its build digest and attribution chain, the illegal transitions and gaps found, what the evidence does and does not show, and a plan for production.

    From you: A readout meeting.

Fixed-scope pilot fee, 100% credited toward Year 1 production licensing. The report is evidence, not a certification or legal opinion.

Book a pilot.

Tell us about the machine and the telemetry it emits. We reply within two working days.

Email hello@coreward.dev

Stockholm

Booking form coming soon

Until then, email us and we will set up a call.

Email instead