SentraZero
How it works

Platform

Multi-Runtime

One sandbox. Every language.

Rich Media

Any file type. Auto-detected. One binary.

Cost Savings

Preprocessing without the data-movement tax.

Security

Embedded security with seccomp, signing, and isolation.

Benchmarks

Platform performance, measured.

Solutions

Research Labs

Sovereign data processing for regulated research

Retail Catalog

Match, dedup, and compare product catalogs

ML Pipelines

Batch inference and data prep at the edge

PII Redaction

Scrub sensitive fields before anything leaves

Pipeline Metrics

Real benchmarks from production pipelines

Request accessDocs
Sign inRequest access

Embedded security,
built into the binary.

The seccomp sandbox lives in the binary. Every plugin carries an Ed25519 signature. And your data never touches the control plane. Not once.

Request access How it works
Guarantees
  • Every plugin Ed25519-signed, verified before execution
  • Seccomp default-deny: 215 syscalls on x86_64, 182 on ARM64
  • Zero client data in the control plane, ever
  • Immutable, queryable audit trail on every run

Embedded
seccomp sandbox

215 allowlisted syscalls on x86_64 (182 on ARM64), default-deny, in the agent binary

Every plugin,
the same filter

The seccomp-BPF filter is compiled into the agent binary. No external seccomp profiles, no container runtime dependencies. Every plugin, regardless of language, runs through the same filter with the same allowlist, the same default-deny policy, and the same audit logging.

Allowlisted syscall categories
File I/O (read, write, open, close, lseek, fstat)
Memory management (mmap, munmap, brk, mprotect)
Process control (clone, fork, exit, wait4)
Network (socket, connect, sendto, recvfrom)
Signal handling (sigaction, signalfd, rt_sigreturn)
Timer & time (clock_gettime, gettimeofday, nanosleep)
Synchronization (futex, eventfd, epoll_wait)
Miscellaneous (gettid, getpid, sched_yield, sysinfo)

Any syscall not on the allowlist triggers SIGKILL immediately. The sandbox is initialized before the plugin starts and cannot be escaped or modified from within.

Ed25519
plugin signing

Every plugin signed before distribution, verified before execution

  1. Key generation

    Each workspace generates an Ed25519 keypair. The private key stays with the workspace owner. The public key is registered with the agent at deployment time.

  2. Plugin signing

    Before a plugin is distributed to agents, it is signed with the workspace private key. The signature is appended to the plugin manifest as a base64-encoded Ed25519 signature.

  3. Signature verification

    Every time an agent receives a plugin, it verifies the Ed25519 signature against the registered public key. Verification happens before the plugin is written to disk, before sandbox init, before any execution.

  4. Execution audit

    Every plugin execution, successful or failed, is logged with the signature hash, execution ID, plugin runtime, resource usage, and outcome. The audit trail is immutable and queryable.

Integrity guarantee: If a plugin binary is tampered with after signing, even a single byte, the Ed25519 signature verification fails. The agent refuses to execute. No unsigned plugin has ever executed on SentraZero.

Zero data
movement

Every claim backed by production database queries

This is the claim that separates SentraZero from every competitor. We don't say "your data stays yours" as a design intention. We show you the production tables to back it up.

Production table queries confirm zero client data
vector_store
0
No client vectors stored
step_outputs
0
No client output data
plugin_execution_history
0
No execution payloads

Only outcome metadata (execution ID, status, wall time, plugin name) and audit logs ever reach the control plane. Raw data, intermediate results, and final outputs stay in your storage. That is not a promise. It is a queryable property of the architecture.

Security
layers

Trust built in layers, from cryptographic verification down to hardware isolation.

Ed25519 plugin signing

Every plugin signed with a workspace Ed25519 keypair. Signature verified before every execution. No unsigned code runs.

Seccomp-BPF filter

215 allowlisted syscalls, default-deny policy. Compiled into agent binary. Applied before every plugin execution.

Cgroups isolation

Memory, CPU, wall-clock, and PID limits enforced per plugin. GPU device access controlled via cgroup device allowlist.

Configurable network access

Plugins run in isolated network namespace by default. Outbound access can be restricted or disabled per pipeline.

Immutable audit trail

Every execution logged with signature hash, resource usage, outcome. Audit trail is append-only and queryable.

SentraZero agent

Your data stays
in your storage

Every plugin Ed25519-signed and sandboxed. No client data leaves your storage.

Benchmarks →Multi-Runtime →
Request accessRequest Compliance Package