Scylos
Product · Pillar

ZeroCore, the stateless operating layer.

A minimal, verified runtime that replaces the traditional OS on the device. ZeroCore retains no local state, user profiles, credentials, configuration drift, or patch history, it safely executes authorized work, then disappears.

Session anatomy

Boot from a verified baseline. Run. Reset to nothing.

ZeroCore boots from a signed, measured baseline, runs your authorized workloads in an ephemeral runtime, then wipes all state on exit. Nothing carries forward to the next session.

ZeroCore · session anatomy

Verified baseline

Signed, measured boot

Ephemeral runtime

Authorized work only

Teardown to nothing

State wiped on exit

Retained on the device
0bytes of state
  • No local data
  • No credentials at rest
  • No config drift
  • No patch history
What runs instead

Your real, containerized workloads, executed locally and statelessly.

Run authorized work · keep nothing

What ZeroCore retains

Nothing. By design.

No local state

Nothing persists on the device between sessions.

No user profiles

Users sign in to their own apps, not the device or Scylos. Nothing is stored on the machine.

No credentials at rest

There is no token or secret to steal from the endpoint.

No config drift

Every session starts from the same verified baseline.

No patch history

There is no accumulated OS to patch, watch, or clean up.

Authorized work only

It safely executes what you allow, then disappears.

How a session runs

Power on. Sign in. Work. Reset.

1

Verified boot

The device starts from a signed, measured baseline, no local OS to corrupt and no kernel agent to push a bad update into.

2

Authorized execution

Your real, containerized workloads run locally on the device, statelessly, with only what the policy allows.

3

Teardown to zero

When the session ends, all state is wiped. The endpoint reboots to known-good, ready for the next clean session.

What ZeroCore is not.

It is not a persistent OS, a thin client, or a VDI session. ZeroCore runs your real, containerized workloads locally on the device, statelessly, and keeps nothing. There is no VDI back end to size and no imaging pipeline to maintain.

The economics

The security model is the reason. The math is the bonus.

per endpoint / month, all-in
$7
industry fully-loaded endpoint cost
$60–75

One flat per-device price for ZeroCore plus the Switchboard control plane in your own cloud. No imaging licenses, no VDI back end, no per-incident cleanup.

ZeroCore vs. a persistent OS

What changes when the OS comes off the endpoint.

ZeroCore
Persistent OS
Local state retained between sessions
Credentials at rest on the device
Configuration drift over time
Kernel agent stack (EDR/AV/RMM/MDM)
Recovery from a bad day
Reboot to known-good
Reimage / rebuild
Runs your real containerized workloads
Common questions

ZeroCore, answered.

Is this VDI or a thin client?+

No. ZeroCore runs your real, containerized workloads locally on the device itself, statelessly. There is no remote desktop session and no VDI back end to size or license.

What happens during an outage or a bad update?+

There is no persistent OS to corrupt and no kernel agent to push a bad update into. A ZeroCore endpoint reboots to known-good and keeps running, recovery is a reboot, not a three-week rebuild.

What does it cost?+

$7 per endpoint, per month, all-in, against industry fully-loaded endpoint costs commonly cited at $60–75. That is one flat per-device price for ZeroCore plus Switchboard in your own cloud.

See it on your hardware

See the stateless endpoint on your own hardware.

Flash an idle machine into a live endpoint and run your real workloads. You buy no hardware and sign nothing.