Destaris
Browse the docs

Local brain, cloud spine

Where work runs, where state lives, and what never leaves your machine.

"Local brain, cloud spine" is the load-bearing idea behind Destaris: the work runs on your machine, and the cloud's only job is to persist and coordinate — never to execute.

The local brain

Your computer is where workflows actually run. Triggers fire locally, steps execute locally, and AI steps run as your own already-authenticated CLI. That means:

  • Your code and the data your workflows touch stay on your machine.
  • Nothing is custodied — not your AI keys, not your provider accounts.
  • Runs aren't metered, because Destaris isn't paying for the compute.

The cloud spine

The cloud's role is the spine, not the muscle. When it's involved, it stores run history and a shared cache, and helps coordinate work — so you get a dashboard of what ran and the ability to pick up where you left off. The spine persists and coordinates; it never runs your work and never holds your credentials.

Only run metadata and capped payloads sync for history and the dashboard — not the contents of everything a workflow processes.

What's optional, and for whom

The free desktop app is the local brain plus a dashboard for your own runs. For power users running at scale, an optional cloud layer adds coordination across several machines, a shared cache between them, and analytics across every run. None of that changes the core rule: execution is always local.

Why this shape

Running agents in someone else's cloud is expensive and forces a vendor to custody users' AI credentials and resell tokens — which breaks trust. Keeping the brain local and the cloud as a thin spine avoids all of that, and it's what makes the "no execution tax" pricing honest.