FeaturesModulesPricingAbout

Modular control for your device fleet.

The agent ships with only the modules you selected. Everything you didn't pick is literally absent: low attack surface, low memory, low CPU.

01 · agent → 02 · mTLS → 03 · platform agent device runtime mTLS platform control plane
fig.00 · system overview scale 1:1 · rev 2026.05
01 · modular agent

Only the modules
you select.

The agent is a single binary that ships with only the modules you selected. Everything you didn't pick is not just disabled, it's absent entirely: lower attack surface, lower memory, lower CPU.

Four modules ship today as examples, system, docker, kubernetes, and systemd, each reporting live state, accepting configuration, handling RPCs, and streaming over WebSockets. The platform always dials the agent over mTLS; the agent never opens a connection first.

systemdockerkubernetessystemd
  • Live metrics: CPU, memory, processes
  • Remote procedure calls: restart, deploy, run
  • Terminal & log streaming over WebSocket
  • Configuration sync with JSON schema
host device 200 × 80 sysc-agent mTLS :8443 module ABI system docker kubernetes systemd cpu · mem · proc containers pods · nodes serviceshost: linux/amd64
fig.01 · agent.svg scale 1:1
mutual TLS · bidirectional auth01 ClientHello + cert 02 ServerHello + cert 03 verified ✓ Agent X.509 · client Platform X.509 · server TLS 1.2+ · AEAD · forward secrecy encrypted channel · authenticated both sides
fig.02 · handshake.svg scale 1:1
02 · mTLS connection

Every byte is
authenticated.

Every device in the fleet runs a different mix of modules, but each one proves its identity the same way. mTLS is the secure identity layer between platform and agent, independent of what a device happens to be running. Each agent carries a CA-signed certificate with the device name as its CN.

The platform checks every agent cert against the shared CA chain, not against a hostname. A SAN mismatch is tolerated; identity comes from the chain, not the name on the wire. No shared secrets, no API keys in transit.

protocol · TLS 1.2+
cipher · AEAD
cert auth · X.509 · mutual
transport · HTTP/1.1 + WebSocket
03 · platform

One control plane.
Everything visible.

The platform is the operator's cockpit: one dashboard for every mix of modules you've deployed. Each agent in the fleet can carry a different set of modules, and the platform renders exactly what each one has, from live state down to logs.

Module control surface

State, config, RPCs, terminal, and logs: the per-module control surface the platform generates for whatever modules an agent carries.

Fleet dashboard

Overview, devices, notifications, users, and AI tabs give you one view of every device, whatever modules it runs.

Notifications

Severity-routed events from every module. Mark, mute, escalate.

AI assistant

An LLM assistant that can read module state via MCP tools and answer questions about your fleet.

platform · control plane platform control plane AI assistant ollama · mcp device state live dashboard notifications info · warn · error integrations mcp · api Ø 400
fig.03 · platform.svg scale 1:1
04 · try it live

See the platform
running for real.

The demo is a fully deployed sysc platform with a live fleet of agents, each running the same modules we ship today. It's not open signup; request access and we'll provision an account the same day.

Once you're in, you get the same UI operators use in production. Not screenshots, not a sandbox video.

  • Browse live devices and drill into module state
  • Open a remote shell on any agent from the browser
  • Call RPCs, change config, watch logs stream
  • Ask the AI assistant about your fleet
fleet · device management search devices... status ▾ sort ▾ device status modules last seen actions prod-server-01 linux/amd64 online system, docker now detail staging-node-02 linux/arm64 online system, k8s 12s ago detail edge-device-07 linux/amd64 offline system 3h ago detail showing 1-4 of 12 ‹ ›fleet · 12 devices
fig.04 · demo.sysc.dev scale 1:1
section 05 · deploy

Deploy the blueprint.

Spin up sysc on your first device. Add modules as your fleet grows.