Otter/Pricing

Pricing

Free to self-host.

Self-hosting costs nothing and there is no seat meter, because the runtime does not phone home to count your jobs. You pay for the machine you already have — or, when you would rather not run one, for managed compute.

Self-hosted

FreeUnlimited jobs. Unlimited runs. Bring the host.

The whole runtime: scheduler, releases, retries, state, run history and HTTP capture. Installed with a single command.

  • Cron, webhook and manual triggers
  • Immutable releases with rollback
  • Durable queue, retries and concurrency limits
  • Durable state, logs, run history, HTTP capture
  • CLI with --json, and a documented HTTP API
  • Managed Python environments per job

Enterprise

Let's talkSupport, roadmaps and terms that fit procurement.

For teams putting pipelines they cannot afford to lose into production, who need someone contractually on the hook.

  • Support with defined response targets
  • Guided migration of an existing pipeline estate
  • Deployment review against the operating drills
  • Security and architecture review
  • Prioritised input on the roadmap
  • Commercial terms, invoicing and a DPA

Why no numbers here? Because inventing a price table for software in early alpha would be theatre. Cloud pricing is being shaped with the first tenants and enterprise terms depend on what you need. Self-hosted is free and stays free — that part is decided.

Side by side

What differs between the two.

  Self-hosted Otter Cloud (alpha)
Runtime features Complete Complete — same binary, same contract
Who runs the host You We do
Where state lives SQLite in your data directory On your tenant's host, operated by us
How you deploy otter deploy --host user@host otter deploy --cloud
Network reach Whatever your host can reach Whatever the tenant host can reach — tell us your allow-list needs
Cost model Free software, your infrastructure bill Being set with the first alpha tenants
Best for Anyone with a server, a VM or even a spare Mac Teams without an operations habit for Python jobs

Licensing & terms

Fair questions about the money.

Is Otter open source?

The source is public on GitHub and you can build it from source, install it from a release or via Homebrew. The terms attached to the source are stated in the repository — read LICENSE there before you assume anything about redistribution, because we would rather you checked the file than trusted a marketing page.

Does self-hosting have limits or a licence key?

No key, no job count, no metering daemon. You run it and it runs. The practical limit is the host: --workers defaults to CPU cores capped at 8, and the supported-load envelope is published in the docs.

What happens to my data if I move from self-hosted to Cloud, or back?

Your jobs are files and your state is SQLite. Moving means copying those to the other host and pointing a runtime at them — there is no proprietary format to escape from and no export tool to request.

Can I use Otter at a company that forbids alpha software?

Then wait, or talk to us about enterprise terms. We label this alpha because the runtime contract is published and being validated against real pilots, not because the engineering is casual. If your risk function says no today, that is a reasonable answer.

Do you offer a discount for non-commercial or research use?

Self-hosting is already free, so there is nothing to discount. If you need committed support without a commercial budget, write to us anyway — the answer is sometimes yes.

Start free. Decide about the rest later.

Install the binary, release a job, and see whether the run history is worth more than the crontab it replaced.