Infrastructure-grade
Built for production. Tested on real workloads. No magic, no managed service dependency, no surprise outages.
Built for teams who ship automation as a product.
Not a workflow builder. A workflow runtime — for the engineers who sell automation to other engineers.
What Opscotch is
Opscotch is a portable runtime for running commercial workflow products. You package your automation logic as signed Opscotch packages; your customers run those packages inside their own infrastructure; Opscotch enforces the plans, quotas, and entitlements you set.
It's designed for teams whose customers need to run automation themselves — air-gapped, behind firewalls, on edge hardware, in regulated environments. SaaS-only deployment models don't work for these customers. Building 'deploy-anywhere' from scratch is a multi-quarter project. Opscotch is the part in the middle.
What it's not
Opscotch isn't a workflow builder, an orchestration framework, or a serverless platform. We don't have a visual editor. We don't have a hosted execution environment. We don't compete with Airflow or Temporal or n8n. We sit underneath them.
If you're building internal automation for your own team, Opscotch is overkill. If you're selling automation as a product — packaged, licensed, distributed to other companies — Opscotch is what you're missing.
What we stand for
Customer-deployable
Runs in environments you don't control. Air-gapped. Offline. Embedded. Designed for these from day one.
Cryptographically honest
Signed packages, verified execution, audit trails. Trust built into the runtime, not bolted on at the billing layer.
Engineering-led
Built by engineers, for engineers. Docs in the repo. Public roadmap. Office hours on Discord. No marketing veneer.
See if Opscotch fits.
30-day extended trial with engineering support. Production-scale from day one.