Skip to content

Diatonic-AI/opensauce

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

OpenSauce

Install Sauce. Public download + setup paths for the Sauce Framework by Sauce Technologies. Edge users · enterprise managed-cloud environments. Six operating systems. The full Sauce agent suite.

Sauce Technologies is an operating-systems partner for businesses whose growth is being throttled by invisible cost, fragmented knowledge, repeated work, and owner dependency. Sauce ships as a governed, canonical, multi-layer system — not as an AI vendor selling novelty. OpenSauce is the public install surface; the rest of the stack stays inside the framework boundary.

Compliance posture, day one: SOC 2 Type II · ISO 27001 / 27017 / 27018 / 27701 · GDPR · NIST 800-53 Mod. Conditional on declared data class: HIPAA · PCI DSS 4.0 · CCPA / CPRA · SOX. Crypto baseline: TLS 1.3, AES-256-GCM via KMS, ECDSA P-256 / Ed25519, Argon2id, Tink primitives — no custom crypto.

Latest release License: MIT


How Sauce is shaped

┌─────────────────────────────────────────────────────────────┐
│  Sauce Framework Control Plane                              │
│  (PRIVATE — Sauce Technologies–managed; you don't run it)   │
│   • fleet management • version reconciliation               │
│   • license compliance • telemetry + log ingest             │
│   • provisions enterprise cloud environments                │
└─────────────────────────────────────────────────────────────┘
                       │ provisions + manages
                       ▼
┌─────────────────────────────────────────────────────────────┐
│  Enterprise Cloud Environments                              │
│  (managed by Sauce Technologies, in your chosen cloud,      │
│   SOC 2 Type II + ISO 27001)                                │
│   • per-enterprise tenancy • OIDC federation                │
│   • data residency • compliance audit logging               │
└─────────────────────────────────────────────────────────────┘
                       │ hosts
                       ▼
┌─────────────────────────────────────────────────────────────┐
│  Business Workspaces (local-first, scale to cloud)          │
│   • multi-user shared filesystem workbench                  │
│   • run on one machine, promote to cloud when needed        │
└─────────────────────────────────────────────────────────────┘
                       │ serves
                       ▼
┌─────────────────────────────────────────────────────────────┐
│  Edge User Installs (per-user, no backend)                  │
│   • 24-binary user-facing surface                           │
│   • telemetry / logs / cookies auto-share defaults ON       │
│   • per-user opt-out for any data category                  │
└─────────────────────────────────────────────────────────────┘

You install the edge layer from this repo. Enterprises request a managed cloud environment — you don't stand up the control plane yourself; Sauce Technologies does.


The 12 layers — and which ones you touch

Sauce is organized as a 12-layer vertical stack (canonical model in the framework repo's docs/architecture/layer-stack.md). OpenSauce ships only L11 (delivery / packaging) and L12 (user surfaces). The deeper layers — storage, semantics, model runtime, agent contracts, mesh control, governance — live behind the binary boundary in the framework repo.

What you want Layers you touch Where to start
"I just want to use it." L11 + L12 docs/user-install.md
"I want to extend it (skills, plugins, MCP)." + L8 (Agency) SDK crates: sauce-skill-sdk, sauce-plugin-sdk, sauce-mcp-sdk (framework repo)
"I run this for an org." + L9 (Control), L10 (Governance) docs/enterprise-install.md
"I want to understand the whole thing." L1 → L12 Framework repo docs/architecture/layer-stack.md

The four-tier control-plane diagram above is deployment topology. The 12 layers are what kind of concern lives where. They are orthogonal axes — see the framework repo's docs/architecture/README.md § "The five axes of Sauce."


Two install paths

👤 Edge user (single machine)

Install the user-facing Sauce binaries — the full agent suite at L11+L12 — on your laptop / dev box / personal Linux server. No sudo by default. 👉 docs/user-install.md

curl -fsSL https://raw.githubusercontent.com/Diatonic-AI/opensauce/main/install/install.sh | sh

⚠️ Default data sharing is ON — telemetry, logs, cookies, inference traces, and pipeline outputs auto-share to the Sauce Framework control plane. See docs/user-install.md § Data sharing and telemetry for what's sent and how to opt out per category.

🏢 Enterprise (managed cloud environment)

Your organization gets a SOC2/ISO27001-compliant cloud environment provisioned + managed by Sauce Technologies. Your business workspaces run local-first and scale to the cloud env when usage justifies. 👉 docs/enterprise-install.md

Request via: enterprise@saucetech.io


Direct downloads

Latest release: v0.1.0

Sauce ships across six operating systems: Debian / Ubuntu, RHEL / Fedora, SUSE, Alpine, macOS, and Windows.

OS Format Size Direct link
Debian / Ubuntu (amd64) .deb 5.8 MB sauce-framework_0.1.0-1_amd64.deb
Windows x64 .msi 21 MB sauce-framework-0.1.0-x64.msi
RHEL / Fedora (amd64) .rpm v0.2.0
Alpine (amd64) .apk v0.2.0
macOS (universal) .pkg v0.2.0
SUSE (amd64) .rpm v0.2.0

Homebrew, winget, and Chocolatey ship in v0.2.0. See CHANGELOG.md for the roadmap.


After install

sauce --version
sauce init --scope user --profile dev

Walk through the first-run flow at docs/getting-started.md.

Want to extend Sauce with your own skills, plugins, or MCP servers? docs/hobbyist-quickstart.md — adds L7 (local model) and L8 (agency) on top of your install.

Stuck? docs/troubleshooting.md.

What each of the 24 binaries does: docs/binaries.md.


Repo layout

opensauce/
├── README.md                  # this file
├── LICENSE-MIT
├── CHANGELOG.md               # release notes per version
├── install/
│   ├── install.sh             # POSIX install (Linux + macOS)
│   └── install.ps1            # Windows install
└── docs/
    ├── user-install.md        # edge-user / single-machine install + telemetry terms
    ├── enterprise-install.md  # how to request a managed cloud environment
    ├── getting-started.md     # post-install first-run walkthrough
    ├── binaries.md            # what each of the 24 bundled binaries does
    └── troubleshooting.md     # install + runtime issue catalogue

How does this relate to Sauce Framework?

Repo Visibility Contains
Sauce Framework Private The full Sauce agent suite — Rust source, framework architecture, control-plane manifests, plugin / skill / MCP authoring SDKs, the .sauce/ protocol spec, internal CI
OpenSauce (this repo) Public Install scripts, signed release artifacts, edge-user + enterprise setup docs, troubleshooting

The Sauce Framework control plane runs on Sauce Technologies–managed infrastructure. Source contributions happen via the licensed channel at https://saucetech.io/contribute.

You can fork this repo to customize install scripts for your environment. Bug reports and install-script PRs are welcome via CONTRIBUTING.md.


License

The install scripts and docs in this repo are MIT — see LICENSE-MIT.

The Sauce binaries themselves ship under their own license (bundled inside the .deb/.msi as LICENSE).

About

Public install layer for the Sauce Framework — install scripts, signed release artifacts (.deb/.msi/etc.), user + enterprise setup docs.

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Packages

 
 
 

Contributors