Provision Sync Clients
Create a client record, generate a one-time activation token, and deliver a download-ready config.json without exposing bearer credentials.
Breeze Control Plane
Private sync and governed service access, operated from one console.
Breeze is a focused control plane for provisioning sync clients, distributing activation-ready configuration, and approving provider-to-consumer service traffic with explicit grants and invocation visibility.
Zero-touch
Create clients, issue config, and hand off deployment in one flow.
Default deny
Providers register first. Consumers gain access only through explicit grants.
Operator visible
Approval states, relay metrics, and invocation history stay in one admin surface.
Capabilities
Designed around the workflows already in the product.
This is not generic cloud messaging. Breeze already knows how to provision clients, deliver configuration, enforce access, and keep operator-facing records.
Distribute Client Builds
Surface current client release artifacts by platform so operators can hand off binaries and configuration as a single deployment package.
Govern Service Access
Approve providers, create grants by consumer and service id, and keep provider catalogs under explicit administrative review.
One admin surface, multiple operational loops.
Breeze’s web layer already spans login, dashboard workflows, ignore rules, client creation, release distribution, provider approval, grants, and invocation history. The redesign turns that into a coherent SaaS-grade control plane without changing the underlying mechanics.
Quiet, secure, and infrastructure-first.
The brand direction emphasizes controlled flow, trusted operations, and connectivity between provider, relay, and consumer roles. It is closer to a modern infrastructure SaaS than a consumer storage product.
Services
Provider approval, grants, and invocation history in one story.
Approve Providers
New providers register first, remain pending until reviewed, and only become generally usable after explicit approval.
Grant With Precision
Access is scoped by consumer, provider, and service id, matching the control model already documented in the product.
Inspect Traffic
Relay metrics and invocation history reinforce that service use is an auditable operator workflow, not an opaque side channel.