Deploy inside customer infrastructure
Run your automation on the customer's side without changing your product model. Your runtime. Their hardware. Your contracts still apply.
Programmable Workflow Runtime
Turn automation into products you can sell.
Opscotch lets teams package, license, and run automation inside customer environments — with enforceable usage, portable execution, and cryptographic integrity built in.
What Opscotch does
Enforce plans, quotas, and entitlements
Commercial rules are enforced in execution — not in config files customers can edit. Plans, seat counts, and per-feature gates are part of the runtime.
Distribute signed automation packages
Every package has verifiable integrity. Customers can audit what they're running, and you can prove what they agreed to run.
Built for businesses like yours
Automation product vendors
You're packaging an internal automation as a product. You need it to ship like software, with licensing, support tiers, and update channels — not like a one-off script.
Managed service providers
You run automation on customer infrastructure and bill by results. You need every customer's runs to be isolated, auditable, and billable — without rebuilding the same controls per tenant.
Security & compliance vendors
Your automation runs in environments you don't fully control. You need it to be tamper-evident, signed, and capable of refusing unauthorized use — even on a compromised host.
Platform & infrastructure teams
You operate the runtime for multiple internal teams. You need workflows to be deployable like services — with versioning, rollbacks, and per-team entitlements.
How it works
Package your workflow
Write your automation in your language of choice. Opscotch packages it as a signed, versioned artifact with a manifest describing inputs, outputs, and the runtime guarantees.
Define commercial terms
Plans, quotas, feature gates, and entitlements are encoded as part of the package — not bolted on afterwards. They travel with the artifact and are enforced at the runtime boundary.
Distribute and run
Ship the package to customer environments — your cloud, theirs, edge devices, or fully disconnected. The runtime enforces your terms everywhere the package runs.
Observe and audit
Every execution emits structured events. Customers can verify what ran and what was enforced. You can answer support questions without guessing what version ran where.
The result
→ You ship automation like a product. Your customers run it like software. Your commercial terms hold — even when the runtime runs on hardware you don't own.
What we stand for
Built for commercial automation
Most workflow tools assume internal use. Opscotch is built around the assumption that the workflow runs in someone else's environment, and that you need to control what it does there.
Runs inside customer infrastructure
Not in your SaaS, not in a browser tab. Inside the customer's network, server, or device — wherever the work needs to happen. You don't ship your data center; you ship a runtime.
Automation packaged as a product
Workflows become artifacts with manifests, signatures, and version history. You ship updates like a product team — not by emailing a new script.
Commercial rules enforced at runtime
Plans, quotas, and entitlements live inside the runtime. They're not enforced by your customer being well-behaved; they're enforced by the artifact refusing to do otherwise.
Deterministic and verifiable execution
Same package, same input, same output — and a customer can verify that. Every run emits the events you need to support it, audit it, and bill it.
Trust by design
Runtime boundary enforcement
The runtime is the contract. Workflows cannot exceed the boundaries you set, regardless of how the host is configured.
Signed workflow artifacts
Every package is cryptographically signed. Tampering with an artifact invalidates its signature, and the runtime refuses to run unsigned or modified packages.
Runtime-enforced licensing
Plans, quotas, and entitlements are part of the runtime, not part of the customer's config. They're enforced whether or not the customer agrees.
Observable and auditable execution
Every run emits structured events for both you and your customer. Answer support questions, run audits, and prove compliance without reverse-engineering logs.
Commercial patterns you can build and ship
Real workflows teams are running on Opscotch today.
Continuous audits, productized
Run security and compliance checks as a service for your customers — billed by tenant, scoped by entitlement, audit-ready by default.
Detection Integrity Assurance
Tamper-evident detection runs that customers can verify didn't drift between deployments — and you can prove ran as configured.
Cross-System Trust Validation
Distributed checks across customer systems that maintain consistent trust posture without a central coordination point.
Cloud Platform Conformance
Continuous policy enforcement that runs in your customer's cloud — versioned, signed, and visible to both sides.
Absence & Silence Detection
Detection products that can prove a system stayed quiet — not just that something noisy fired. Powerful for compliance use cases.
Temporal Degradation Detection
Catch slow-failing systems — where the signal gradually degrades over time — that traditional alerting misses entirely.
Edge Field Operations
Automation that runs on edge devices and disconnected sites — and stays verifiable even when network access is intermittent.
Ask an Opscotch engineer
Describe the problem you're trying to solve. We'll tell you if Opscotch is a good fit — and if it isn't, we'll say so.
Ask an engineer →Supported platforms
Linux · Windows · macOS · Docker · Kubernetes
Launch a workflow product with commercial control
Talk to an engineer about what you're building. We'll help you figure out whether Opscotch fits — and if it does, get you running in a couple of weeks.