§ 00 · Linux Fleet Orchestration
Pilot · onboarding design partners

Orchestrate your Linux fleet at any scale.

Single binary. Cloud or self-hosted. Your data stays on your infrastructure — packages, logs, and credentials never cross into ours.

~/syncronis
# Install agent on any Linux box
$curl -fsSL https://syncronis.net/install | sh
# Same binary, three roles
$syncronis server --config /etc/syncronis/server.json
$syncronis vault  --config /etc/syncronis/vault.json
$syncronis agent  --config /etc/syncronis/agent.json
§ 01 What it is

Three roles. One binary. Zero runtime dependencies.

01

One static binary

A ~13 MB static Go binary serves as control plane, vault, or agent depending on subcommand. No runtime. No Python, no Ruby, no Java. Drop on anything from a Raspberry Pi to a bare-metal rack.

02

Vault on your infrastructure

Packages, logs, and credentials live on a vault you control. The control plane — managed by us or self-hosted by you — never stores tenant data. Air-gap deployable, audit-friendly, sovereign by design.

03

Bash + JSON, no DSL

Familiar Bash for execution. Structured JSON for rollout intent — target matching, machine sets, canary phases, scheduling. Nothing new for the team to learn.

§ 02 Why Syncronis

Three architectural choices that matter.

How it differs from Ansible, Mender, Balena, and other comparable tools.

Data sovereignty as a first principle

vs. typical SaaS →

The vault runs on your infrastructure. Tenant data never crosses into ours. Whether you choose our managed cloud or fully self-host, packages and logs stay on machines you control.

No Kubernetes. No agents to babysit.

vs. cluster orchestration →

One binary, three roles. No cluster, no sidecar mesh. Deploy in minutes, not weeks. Runs equally well on a Raspberry Pi at an edge site or a rack of bare metal in a datacenter.

Opaque scripts, structured rollouts

vs. declarative DSLs →

We don't parse or interpret your scripts — that is your business logic and stays with you. We orchestrate where and when they run, with versioned intent, target specificity, and natural canary phases via machine sets.

§ 03 Access

Currently onboarding design partners.

Syncronis is in pre-launch. We are onboarding a small group of design partners with direct founder support — personalised setup, dedicated email channel, and hands-on troubleshooting during your pilot.

Email contact@syncronis.net with your fleet size, primary use case, and current orchestration setup. You will receive a personal access link within one business day.

See pricing details — first 5 machines free, graduated rates beyond that, cloud or self-hosted.